Methods for dynamic configurations for artificial intelligence machine learning positioning

Abstract

Systems, methods, and apparatus are described herein for determining applicable artificial intelligence (AI) / machine learning (ML) functionalities. A wireless transmit receive unit (WTRU) may determine AI / ML functionalities implemented by a network entity. In response to the AI / ML functionalities failing to be supported by the WTRU, the WTRU may send a request to activate an applicable AI / ML functionality within a serving cell associated with the WTRU. The WTRU may implement a fallback when there are no applicable AI / ML functionalities.

Description

METHODS FOR DYNAMIC CONFIGURATIONS FOR ARTIFICIAL INTELLIGENCE MACHINE LEARNING POSITIONINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority from Provisional U.S. Patent Application No. 63 / 679,487, filed August 5, 2024, the entire disclosure of which is hereby incorporated by reference herein in its entirety.BACKGROUND

[0002] A wireless transmit / receive unit (WTRU) has Artificial Intelligence Machine Learning AIML model(s) and the WTRU may determine its position using the AIML model(s) at the WTRU. The inference of the WTRU’s AIML model is the WTRU’s location. The geographical coverage of an AIML model is proportional to the size of the AIML model input and AIML model complexity and thus, power consumption. To measure positioning reference signal(s) (PRSs) from neighboring cells, the WTRU requires measurement gaps to be configured. An AIML model may be associated with a cell or area (collection of cells), cell, or potentially a set of PRSs (e.g., if configured, the WTRU uses the AIML model as long as the WTRU is in the associated area).SUMMARY

[0003] Systems, methods, and apparatus are described herein for determining applicable artificial intelligence (Al) I machine learning (ML) functionalities. A wireless transmit receive unit (WTRU) may determine applicable AI / ML functionalities implemented by a network entity. The determination may be based on one or more conditions or assistance information. The one or more conditions may comprise at least one of battery power, location, or availability of measurement gap. The assistance information comprises an associated identifier. In response to the AI / ML functionalities failing to be supported by the WTRU, the WTRU may send a request to activate an applicable AI / ML functionality within a serving cell associated with the WTRU. For example, the WTRU may send a request to activate the applicable AI / ML positioning functionality based on the WTRU not receiving a measurement gap configuration within a time window.

[0004] The assistance information comprises an associated identifier. In some examples, the associated identifier indicates a configuration or condition associated with the WTRU or a network. The associated identifier may indicate a cell identifier, an area identifier, a positioning reference signals (PRS) configuration, and / or a transmit-receive point (TRP) location.

[0005] The WTRU may determine applicable AI / ML positioning functionality supported by the WTRU further based on a number of cells the WTRU can support through AI / ML based positioning. In some examples, the WTRU may receive an activation command for the applicable AI / ML positioning functionality. In some examples, the WTRU may receive a request from a location management function (LMF) to report a capable AI / ML positioning functionality. In some examples, the WTRU may determine to use a fallback positioning method when there is no applicable AI / ML functionality.

[0006] A WTRU may include a processor and memory. The WTRU may be configured to receive a positioning reference signals (PRS) configuration and an associated identifier. The associated identifier may indicate one or more transmit-receive point (TRP) locations. The WTRU may be configured to determine an applicable artificial intelligence (Al) / machine learning (ML) positioning functionality supported by the WTRU based on the PRS configuration and the associated identifier. The WTRU may be configured to send a request to activate the applicable AI / ML positioning functionality.

[0007] In some examples, the WTRU may send an indication of the number of cells the WTRU can support for AI / ML positioning. The associated identifier may indicate one or more of PRS identifiers, PRS resource set identifiers, and / or PRS resource identifiers. In some examples, the WTRU may determine a fallback when there is no applicable AI / ML functionality. In some examples, the WTRU may receive a request from a location management function (LMF) to report a capable AI / ML positioning functionality. In some examples, the WTRU may request to activate the applicable AI / ML positioning functionality based on the WTRU not receiving a measurement gap configuration within a time window. In some examples, the WTRU may determine a location of the WTRU based on the determined AI / ML positioning functionality, and send, to a location management function (LMF), a report comprising the location of the WTRU.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0012] FIG. 2 is a diagram illustrating an example measurement gap periodicity, an example measurement gap length, and an example measurement gap offset.

[0013] FIG. 3 is a diagram illustrating using an example AIML model to estimate a WTRU location.

[0014] FIG. 4 is a tree diagram illustrating an example hierarchical structure of PRS configurations.

[0015] FIG. 5 is a diagram illustrating an example signaling exchange between an LMF and a WTRU.

[0016] FIG. 6 is a tree diagram illustrating an example of a hierarchy of PRS parameters in an AIML functionality.

[0017] FIG. 7 is a system diagram illustrating an example of measurements a WTRU makes for different geographical coverage of an AIML model.

[0018] FIG. 8 is a system diagram illustrating an example of a supportable area depending on the remaining battery power of the WTRU.

[0019] FIG. 9 is a system diagram illustrating another example of a supportable area depending on the remaining battery power of the WTRU.

[0020] FIG. 10 is a diagram illustrating an example of receiving applicable functionalities from a network.

[0021] FIG. 11 is a diagram illustrating an example of a signaling exchange between a WTRU and an LMF.

[0022] FIG. 12 is a diagram illustrating an example of a signaling exchange between a WTRU, a base station, and an LMF.DETAILED DESCRIPTION

[0023] 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-sOFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

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

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

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

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

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

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

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

[0031] 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 multipletypes of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g, a eNB and a gNB).

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

[0033] 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 and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

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

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

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

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

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

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

[0040] 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 more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

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

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

[0043] 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 maybe any suitable device for powering the WTRL1 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] 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 ST As (e.g., every ST A), 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.

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

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

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

[0062] 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 theexample 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0077] The WTRU may be requested to perform AIML based positioning with any of the following specific requests. The specific request may be for configured duration and reporting periodicity. The specific request may be for positioning over specified area (e.g., indicated cells, indicated transmission reception points (TRPs), network (NW) may want the WTRU to have an AIML model that works in an area).

[0078] The WTRU may send a request to the network for configuration (e.g., Downlink Reference Signal (DL-RS) configurations, Uplink Reference Signal (UL-RS) configurations) in Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Uplink Control Information (UCI), Medium Access Control Control Element (MAC-CE), Radio Resource Control (RRC), or Location Positioning Protocol (LPP) message. The request from the WTRU may include configurations of a measurement gap, DL-RS processing window, or window for transmission of UL-RS.

[0079] The WTRU may send an acknowledgement message in PUSCH or PUCCH for the grant received from the network. More than one conditions / criteria may be used in a combination. The WTRU may be configured with more than one condition and associated WTRU behavior and the WTRU may determine which behavior the WTRU shall use based on the applicable condition. The WTRU may measure DL-RS inside or outside of active BWP. The WTRU may transmit UL-RS inside or outside of active BWP. The WTRU may be preconfigured with parameters (e.g,. measurement gaps, DL-RS processing windows, DLRS configurations, UL-RS configurations) via a semi-static message (e.g, LPP, RRC). Any actions the WTRU determines to take may be configured by the network. For example, the WTRU may be configured with a rule and according to the rule, the WTRU may determine to take an associated action.

[0080] In addition to the measurements made on DL-RS, the WTRU may include at least one of the following cell-related measurements. The cell-related measurements may include Synchronization Signal Block (SSB) Reference Signal Received Power (RSRP) from the serving cell with corresponding cell ID. The cell-related measurements may include SSB RSRP from the neighboring cell(s) with corresponding cell ID(s). The cell-related measurements may include RSRP of Channel State Information Reference Signal (CSI-RS) with CSI-RS resource ID. The cell-related measurements may include Reference Signal Received Strength (RSRS) of Demodulation Reference Signal (DM-RS).

[0081] In the embodiments described herein, “Network” may include AMF, LMF, a base station (e.g., gNB) or NG-RAN. “Pre-configuration” and “configuration” may be used interchangeably in the embodiments described herein. “Non-serving gNB” and “neighboring gNB” may be used interchangeably in the embodiments described herein. The terms “base station”, “gNB” and “TRP” may be used interchangeably in the embodiments described herein. “DL-RS” or “DL-RS resource” may be used interchangeably in the embodiments described herein. “DL-RS(s)” or “DL-RS resource(s)” may be used interchangeably in the embodiments described herein. The aforementioned “DL-RS(s)” or “DL-RS resource(s)” may belong to different DL-RS resource sets. “Measurement gap” or “Measurement gap pattern” may be used interchangeably in the embodiments described herein. “Measurement gap pattern” may include parameters such as measurement gap duration or measurement gap repetition period or measurement gap periodicity.

[0082] A Location Management Function (LMF) is a non-limiting example of a node or entity (e.g., network node or entity) that may be used for or to support positioning or sensing. Any other node or entity may be substituted for LMF and still be consistent with the embodiments described herein. The WTRU may receive a preconfigured threshold(s) from the network (e.g., LMF, gNB). The Line of Sight (LOS) indicator may be a hard (e.g., 1 or 0) or a soft indicator (e.g., 0, 0.1 , 0.2..., 1) and it may indicate the likelihood of the presenceof an LOS path between TRP and WTRU or along DL-RS. The LOS indicator may be associated with a TRP or PRS resource ID (e.g., index). The WTRU may receive the LOS indicator from the network per TRP or resource ID. The WTRU may also determine the LOS indicator per TRP or resource ID based on measurements.

[0083] In the examples described herein, “ID” and “index” may be used interchangeably. A WTRU location may be expressed in terms of altitude, latitude, geographic coordinate, or local coordinate, for example. In the examples described herein, a timestamp may be indicated by absolute time, relative time (e.g., in seconds) compared to a reference time, System Frame Number (SFN), slot index, frame index, subframe index and / or symbol index. Examples of “absolute time” may be UTC time, GNSS time, and / or locally defined absolute time (e.g., LTE or NR Time).

[0084] Embodiments are described herein for RS configurations. In one example, the WTRU may receive DL-RS and / or UL-RS (e.g., SRS) configurations for positioning purpose from the network (e.g., LMF). The LMF may forward the PRS configuration and SRS configurations to the base station so that the base station may schedule PRS transmission or SRS reception at the TRP, TP, and / or RP.

[0085] Embodiments are described herein for DL-RS configurations. In one example, a DL-RS configuration may include at least one of the following parameters: number of symbols, transmission power, number of DL-RS resources included in DL-RS resource set, muting pattern for DL-RS (for example, the muting pattern may be expressed via a bitmap), periodicity, type of DL-RS (e.g., periodic, semi-persistent, or aperiodic), slot offset for periodic transmission for DL-RS, vertical shift of DL-RS pattern in the frequency domain, time gap during repetition, repetition factor, RE (resource element) offset, comb pattern, comb size, spatial relation (e.g., with respect to other DL-RSs or UL RS such as SRS for positioning purpose), QCL information (e.g., QCL target, QCL source) for DL-RS, number of TRPs, Absolute Radio-Frequency Channel Number (ARFCN), subcarrier spacing, expected RSTD, uncertainty in expected RSTD, start Physical Resource Block (PRB), bandwidth, BWP ID, number of frequency layers, start / end time for DL-RS transmission, on / off indicator for DL-RS, TRP ID, DL-RS ID, cell ID, global cell ID, and / or applicable time window. The WTRU may apply a DL-RS configuration under a condition that the current time is within the applicable time window. “ID” may be used interchangeably with “index”. Examples of DL-RS may include CSI-RS, PTRS, PRS, TRS, and / or SSB.

[0086] Embodiments are described herein of configurations for UL-RS. In one example, UL-RS or SRS configuration may include at least one of : resource ID; comb offset values, cyclic shift values; start position in the frequency domain; number of UL-RS symbols; shift in the frequency domain for UL-RS; frequencyhopping pattern; type of UL-RS (e.g, aperiodic, semi-persistent or periodic); sequence ID used to generate UL-RS, or other IDs used to generate UL-RS sequence; spatial relation information, indicating which reference signal (e.g., DL RS, UL RS, CSI-RS, SRS, DM-RS) or SSB (e.g., SSB ID, cell ID of the SSB) the UL-RS is related to spatially where the UL-RS and DL RS may be aligned spatially; QCL information (e.g., a QCL relationship between UL-RS and other reference signals or SSB); QCL type (e.g., QCL type A, QCL type B, QCL type C, QCL type D); resource set ID; list of UL-RS resources in the resource set; transmission power related information; pathloss reference information which may include index for SSB, CSI-RS or DL-RS; periodicity of UL-RS transmission; and / or spatial information such as spatial direction information of UL-RS transmission (e.g., beam information, angles of transmission); and / or spatial direction information of DL RS reception (e.g., beam ID used to receive DL RS, angle of arrival). “ID” may be used interchangeably with “index”. Examples of UL-RS may include SRS and / or SRS for positioning purpose.

[0087] Categories of WTRU positioning techniques are described and / or may be implemented, as described herein. The WTRU positioning technique category may include a DL positioning method. The DL positioning method may refer to any positioning method that uses downlink reference signals, such as PRS. The WTRU may receive multiple reference signals from TP(s) and may measures DL RSTD and / or RSRP. Examples of DL positioning methods may include DL-AoD or DL-TDOA positioning. The WTRU positioning technique category may include a UL positioning method. A UL positioning method may refer to any positioning method that uses uplink reference signals, such as SRS for positioning. The WTRU may transmit SRS to multiple RPs and the RPs may measure the UL RTOA and / or RSRP. Examples of UL positioning methods may include UL-TDOA or UL-AoA positioning. The WTRU positioning technique category may include a DL & UL positioning method. A DL & UL positioning method may refer to any positioning method that uses both uplink and / or downlink reference signals for positioning. For example, a WTRU may transmit SRS to multiple TRPs and base station may measure a Rx-Tx time difference, which may be calculated based on the time of arrival of DL RS (e.g., PRS). The base station may measure RSRP for the received SRS. The WTRU may measure a Rx-Tx time difference for PRS transmitted from multiple TRPs. The WTRU may measure RSRP for the received PRS. The Rx-TX difference and possibly RSRP measured at the WTRU and base station may be used to compute round trip time. WTRU Rx - Tx time difference may refer to the difference between arrival time of the reference signal transmitted by the TRP and transmission time of the reference signal transmitted from the WTRU. An example of DL & UL positioning method may include multi-RTT positioning.

[0088] Embodiments are described herein for a measurement gap related to measurements that may be performed. The WTRU may receive configuration(s) for measurement gaps for making measurements on PRSs outside of the active BWP. The WTRU may receive PRSs outside of the active BWP from outside of the serving cell. In one example, the WTRU may transmit a request to the base station (e.g., serving base station), for example, via MAC-CE or UCI to change measurement gap configuration. The WTRU may send (e.g., determine to send) the request based on the measurement status (e.g., quality or value) of one or more PRS resource(s). The WTRU may receive a PRS configuration from, for example, the LMF. The PRS configuration may be received via signalling such as LPP signalling (e.g., LPP messages). The WTRU may, for example initially, send a request to (e.g., to the base station) to configure measurement gap(s). In one example, the WTRU may receive configurations related to a measurement gap from the network. The configuration of measurement gap(s) may comprise configuration of a measurement gap parameter(s) that may include measurement gap length, gap periodicity, and / or gap offset. The WTRU may make the request so that the WTRU may make measurements on PRS from one or more serving base stations and / or nonserving base stations. Parameters related to measurement gap, such as, measurement gap length 206, measurement gap periodicity 202, and / or measurement gap offset 204 are illustrated in FIG. 2. During the measurement gap, whose length is indicated as measurement gap length 206 in FIG. 2, the WTRU may not be expected to transmit or receive data. Outside of the measurement gap, the WTRU may be expected to make measurements on PRS(s).

[0089] A WTRU may be configured with (or receive configuration of) one or more thresholds, one or more time windows, and / or one or more durations which the WTRU may use for determining when to request a measurement gap configuration (e.g., pattern) or a measurement gap configuration (e.g., pattern) update or change. The threshold(s), the time window(s), and / or duration(s) may be received from a base station (e.g., the serving base station) and / or the LMF.

[0090] Timing measurements are described herein. In one example, RSTD may be defined by the difference in time of arrival between PRSs transmitted from a reference TRP and target TRP. The WTRU may be configured with the reference TRP index and target TRP index. The WTRU may be configured with the PRS resource indices to make measurements. The WTRU may determine the time of arrival from TRP based on one or more PRS resources associated with the TRP. In another example, the RSTD may be defined as the difference in time of arrival between the reference PRS transmitted from a TRP and the target PRS transmitted from a TRP. In one example, WTRU Rx - Tx time difference may refer to the difference between arrival time of the reference signal transmitted by the TRP and transmission time of thereference signal transmitted from the WTRU. The RxW-Tx time difference may be associated with PRS resource ID and / or SRSp resource ID.

[0091] Phase measurements are described herein. In one example, RSCP (RS Carrier Phase) may be defined as the carrier phase measurement on the PRS. RSCPD (RSCP Difference) may be defined as difference in carrier phase measurements between two PRS resources.

[0092] Power measurements are described herein. In one example, RSRP per path may be defined as the RSRP per path if the WTRU observes a multipath channel in the measurement. The WTRU may determine RSRP for a DL RS resource. RSRP or RSRPP may be reported using units dBm or relative power difference compared to a reference, e g., RSRP of the first path, in dB.

[0093] Embodiments are described herein that include details related to channel impulse response and / or association to RS configurations. An example of a measurement may include a channel impulse response. A channel impulse response, including N paths, may be defined by the following equationwhere andare time-varying complex valued coefficients (e.g., expressedfor the channel impulse response and delay, measured in seconds, for the kthpath, respectively. The delta function is defined asFor a sake of simplicity, the coefficients may be assumed to be constant over time, e.g. The WTRUmay report for each path k to the network. The WTRU may report the number of paths, N, to thenetwork. The WTRU may also receive hkand zkfor each path k from the network and / or the number of paths.

[0094] In an example, the WTRU may obtain a Channel Impulse Response (CIR) from the network. The network may indicate PRS configuration(s) such as PRS resource IDs associated with the CIR. For example, the CIR may be associated with PRS resource ID. In this case, the WTRU may determine that the CIR is derived based on the measurements made on the PRS resource associated with the ID. The WTRU may also determine that the channel along the direction of transmission of the PRS or reception of the PRS corresponds to the CIR. In an example, the CIR may be associated with a TRP ID. In this case, the WTRU may determine that the CIR represents the channel between the associated TRP and WTRU. In an example, the CIR may be associated with more than one TRPs where the network may include TRP indices associated with the CIR. In an example, the CIR may be associated with a cell. The WTRU may receive a cell ID or index associated with the CIR from the network. In an example, CIR may be associated with more than one TRPs or PRS resource IDs. The WTRU may determine that the channel between the TRPs and the WTRU corresponds to the CIR. The WTRU may also determine that the channel along thetransmission directions of PRSs associated with IDs or reception directions of the PRS correspond to the CIR.

[0095] In an example, more than one CIRs may be associated with one parameter from PRS configurations (e.g., TRP ID, PRS resource ID, frequency layer ID). For example, the WTRU may receive information related to two CIRs associated with a TRP from the network, e.g.,and h2(t)~T2,k) from the network. The WTRU may also report information related to more than one CIRs associated with a PRS configuration (e.g., TRP ID, PRS resource ID) based on the measurements to the network. There may be more than one CIRs associated with a PRS configuration since the WTRU or network may observe different channel characteristics based on AoA of DL RS or UL RS, for example.

[0096] Channel impulse response may be represented by a delay profile or power delay profile. A power delay profile may be defined as a set of delays and power profiles, such asandwhere pkmay correspond to relative power at the kthpath compared to the first path. A delay profile may be defined as a set of delays [T0, • •• , T^] which indicates path delay for each path above pthreShoid- The WTRU may receive pthreshoidfrom the network to derive a delay profile from a power delay profile.

[0097] In an example, the WTRU may receive an indication from the network on how to generate CIR, PDP or DP based on timing, phase and / or power measurements. The WTRU may send a request to the network to receive an indication on which methodologies to use to generate CIR, PDP or DP based on the measurements the WTRU made. For example, the WTRU may receive a message from the network (e.g, via LPP, RRC, MAC-CE, DCI) indicating the PRS resource indices and associated measurement type(s) (e.g, RSTD, AOA) to use to generate CIR, PDP or DP. In one example, the WTRU may receive an indication from the network indicating to generate CIR, PDP or DP.

[0098] In an example, the WTRU may receive a threshold (e.g, power threshold) from the network and a timing range (e.g. Ops to 1 ps), timing granularity (e.g, every 0.1 ps in the indicated timing range, 100 sample points in the indicated timing range) of CIR, a PDP, and / or DP. The WTRU may determine to report power and timing (e.g, relative timing compared to a reference timing, absolute timing) for any samples whose received power is over the threshold. The WTRU may send measurements in a report to the network (e.g, LMF, base station) via a semi-static (e.g, LPP, RRC) or dynamic message (e.g, UCI, UL MAC-CE). In the examples herein, PRS, DL-RS (e.g., CSI-RS, DM-RS, TRS), and / or SSB may be used interchangeably.

[0099] Embodiments are described herein for the contents of a measurement or location report. In an example, the WTRU may receive a request from the network to report its location and / or measurements made on the PRS. The WTRU may report to the network at least one or a combination of the following in the measurement report. The WTRU may report a PRS ID associated with measurements and / or a WTRU location estimate. The WTRU may report a TRP ID associated with measurements and / or a WTRU location estimate. The WTRU may report a Cell ID associated with measurements and / or a WTRU location estimate. The WTRU may report an ARFCN associated with measurements and / or a WTRU location estimate. The WTRU may report the PRS Resource ID(s) associated with measurements and / or a WTRU location estimate. The WTRU may report the PRS Resource Set I D(s) associated with measurements and / or a WTRU location estimate. The WTRU may report frequency layer I D(s) associated with measurements and / or a WTRU location estimate. The WTRU may report a timestamp indicating when the measurements are made or when the report is made. The WTRU may report a timestamp indicating when inference (e.g., WTRU location estimate generated by AIML model(s)) is applicable. For example, the timestamp may indicate where the WTRU is at for the indicated timestamp. The WTRU may report a RSTD associated with PRS resource I D(s) for each path in multipaths. The WTRU may report a RSRP associated with PRS resource I D(s) for each path in multipaths. The WTRU may report a phase measurement (e.g., RSCP, RSCPD) for each path in multipaths. The WTRU may report uncertainty information (e.g., expressed in terms of a range such as / s) or quality information (e.g., indicating whether the indicatedmeasurement is in the unit of 0.1 ps or 0.01 ps) for measurements. The WTRU may report a TEG (timing error group) associated with measurements or PRS resource ID or PRS resource set ID. The WTRU may report a LOS indicator associated with PRS resource ID or TRP ID. The WTRU may report the WTRU location (e.g., absolute location with geographical coordinates expressed by x and y coordinates, relative location with respect to a reference point (e.g., indicated TRP, cell center)). The WTRU may report uncertainty information for the determined WTRU location (e.g., expressed in terms of a range such as2 meter) or quality information (e.g., indicating whether the indicated WTRU location is in the unit of 0.1 meter or 0.01 meter). The WTRU may report an indication of which method (e.g., RAT dependent positioning method such as DL-TDOA, DL-AoD, or AIML based positioning) is used to determine the WTRU location. The WTRU may report channel impulse response and associated DL-RS configurations used to determine CIRs. The WTRU may report a model or functionality ID used to generate WTRU location estimate.

[0100] Embodiments are described herein for implementing artificial intelligence (Al) or an AIML model for positioning. Artificial intelligence may be broadly described as the behavior exhibited by machines thatmimics cognitive functions to sense, reason, adapt, act, and / or providing the ability to discern patterns. An example of using an AIML model to obtain WTRU location is shown in FIG. 3. As shown in FIG. 3, the WTRU inputs the AIML model 304 with measurements 302 (e.g., timing, phase, power measurements such as RSTD, time of flight, ToA, ToD, carrier phase measurement, carrier phase difference measurement, RSRP, RSRP per path) and the WTRU obtains the WTRU location 306 from the AIML model. The output of the AIML model may be referred to as inference. As an input to the AIML model, if the AIML model is associated with or trained with measurements from more than one TRPs, the WTRU may use measurements made from more than one TRPs. If the AIML model is trained with measurements from more than one TRPs, the WTRU may receive an indication or configuration from the network about identification information about the TRPs (e.g., TRP IDs, PRS IDs) the AIML model is trained with. In the examples described here in, AIML and AI / ML may be used interchangeably.

[0101] Examples of inputs for an AIML model for positioning may include at least one or combination of the following. The inputs for an AIML model for positioning may include a RSRP of PRS resource(s). The inputs for an AIML model for positioning may include a statistical measure of RSRP (e.g., mean, variance etc.) per PRS resource(s). The inputs for an AIML model for positioning may include a maximum or minimum value of RSRP per PRS resource(s). The inputs for an AIML model for positioning may include a RSRP of PRS resource(s) per path. The inputs for an AIML model for positioning may include a RSRP of PRS resource(s) per antenna port. The inputs for an AIML model for positioning may include a RSCP of PRS resource(s) per path. The inputs for an AIML model for positioning may include a RSCP of PRS resource(s) per antenna port. The inputs for an AIML model for positioning may include a RSTD and / or RSCPD of PRS resource(s). The inputs for an AIML model for positioning may include a statistical measure of RSTD per PRS resource(s). The inputs for an AIML model for positioning may include a maximum or minimum value of RSTD per PRS resource(s). The inputs for an AIML model for positioning may include a RSTD and / or RSCPD of PRS resource(s) per path. The inputs for an AIML model for positioning may include a RSTD and / or RSCPD of PRS resource(s) per antenna port. The inputs for an AIML model for positioning may include a time of arrival per PRS resource(s). The inputs for an AIML model for positioning may include a time of arrival per PRS resource(s) per path. The inputs for an AIML model for positioning may include a time of arrival per PRS resource(s) per port. The inputs for an AIML model for positioning may include a statistical measure of Time of arrival per PRS resource(s). The inputs for an AIML model for positioning may include a maximum or minimum value of time of arrival per PRS resource(s). The inputs for an AIML model for positioning may include a CIR estimated based on DL-RS(s) (e.g., PRS, CSI-RS, DM-RS) where CIR may be associated with a TRP or TRPs. The inputs for an AIML model for positioning may include a PDP estimated based on DL-RS(s) (e.g., PRS, CSI-RS, DM-RS)) where CIR may be associated with a TRP or TRPs. The inputs for an AIML model for positioning may include a DP estimated based on DL-RS(s) (e.g., PRS, CSI-RS, DM-RS)) where CIR may be associated with a TRP or TRPs.

[0102] As illustrated in FIG. 4, PRS parameters may be organized in a hierarchical manner. Parameter(s) associated with a higher layer is used by parameter(s) at lower layer(s). For example, if a frequency layer has a parameter comb factor = 2, PRS resource sets, TRPs and PRS resources under the frequency layer also uses comb factor =2. The parameters are organized in a hierarchical manner to reduce signaling overhead from the network.

[0103] The WTRU may be configured with an AIML model. The AIML model may be associated with or valid within an area (e.g., including more than one cells). An advantage of the AIML model being associated with the area is that the WTRU may locate itself anywhere in the area. However, the following challenges may occur. An AIML model is proportional to the size of AIML model input and AIML model complexity and thus, power consumption may be a challenge. Therefore, larger the area an AIML model is associated with, more power consumption that may be expected for the WTRU to generate inference or perform LCM. During LCM, the network may turn on each TRP in the area (so the NW may collect measurements and associated ground truth from the WTRUs in the area), which may be costly in terms of NW-side power consumption and potential loss of time & frequency resources for communication. The WTRU may not be able to execute the configured AIML model with limited remaining power. In addition, the WTRU may not be able to measure neighboring cells’ PRS because measurement gap is not configured by the network. Positioning may continue to be performed when WTRU conditions have changed, as described herein.

[0104] The WTRU may determine applicable AIML positioning functionalities based on WTRU conditions (e.g., battery power, location, availability of measurement gap) and / or assistance information (e.g., associated ID). If the AIML functionality indicated by the network cannot be supported by the WTRU, the WTRU may send a request to activate on of the applicable AIML functionalities (e.g., AIML functionality that is applicable within the serving cell). If there are no applicable AIML functionalities, the WTRU may determine to use the configured fallback positioning method.

[0105] The WTRU may receive a request from the LMF (e.g., via an LPP message) to report capable AIML functionalities. The WTRU may report the number of cells (e.g., 1, 3, 5) the WTRU may support for AIML-based positioning. The WTRU may receive an associated ID (e.g., serving cell ID and a neighboringcell ID), and / or associated PRS configurations (e.g., TRP IDs, PRS IDs). The WTRU may determine the AIML functionality associated with the associated ID. The WTRU may send a request for measurement gap configuration to the base station. If the WTRU does not receive measurement gap configuration within the time window, the WTRU may send an activation request to the LMF to activate the AIML functionality applicable for the serving cell and the request may include the cause (e.g., no measurement gap is configured). The WTRU may receive an associated ID from the network as a response for the request. If there are no applicable AIML functionalities, the WTRU may determine to use the configured fallback positioning method. If the WTRU receives measurement gap configuration within the time window, the WTRU may determine to use the AIML functionality associated with the associated ID to generate WTRU location. The WTRU may receive PRS configurations from the LMF. The WTRU may determine WTRU location based on the determined AIML functionality and the WTRU may report the WTRU location to the LMF.

[0106] An example of signaling exchange between the WTRU and LMF is shown in FIG. 5. At 502, the WTRU may receive a request from the LMF to report supported functionalities. The request may be sent in an LPP message. As a response for the request, the WTRU may report a first set of functionalities at 504. The first set of functionalities may be WTRU capabilities and / or functionalities that may be supported by the WTRU. The functionalities may be indicated in an LPP message. The WTRU may receive assistance information and / or acknowledgement of the reported functionalities from the LMF at 5065. Based on the assistance information, the WTRU may report applicable functionalities (e.g., a second set of functionalities) to the network at 508. The WTRU may determine applicable functionalities based on WTRU conditions (e.g., battery power, location) and / or assistance information (e.g., associated ID). The second set of functionalities may include a subset of the first set of functionalities. The WTRU may receive a request for AIML positioning with indicated functionality at 510. Assistance information may include an associated I D(s) based on which the WTRU may determine applicable functionality. Details of functionalities and applicable functionalities are described herein.

[0107] In an example embodiment, the WTRU may receive a request from the network to report capable functionalities. The WTRU may indicate a first set of functionalities to the network. The WTRU may determine the first set of functionalities based on WTRU capabilities (e.g., the number of cells the WTRU may support through AIML based positioning). The WTRU may receive assistance information for AIML based positioning. The WTRU may determine an associated ID based on the assistance information (e.g., cell ID is the associated ID). The WTRU may indicate applicable functionalities (e.g., a second set offunctionalities) to the network where the second set of functionalities is a subset of the first set of functionalities. The WTRU may determine the applicable functionality that includes indicated associated IDs (e. g . , cell IDs) in the assistance information. If the WTRU determines that there are no applicable functionalities, the WTRU may determine to use the configured fallback positioning method. The WTRU may receive an activation command for one of the functionalities from the second set from the network.

[0108] An AIML functionality may include at least one or combination of the following. In one example, an AIML functionality may define what a WTRU may do with the AIML functionality (e.g., AIML based positioning). The AIML functionality may indicate, infer or imply which AIML model(s) to use to perform AIML based positioning. The AIML functionality may indicate characteristics of input and / or output of an AIML model. Examples of the input of the AIML model may include timing, phase, angle and / or power measurements. Other examples of the input of the AIML model may include DP, PDP and / or CIR. In another example, an AIML functionality may indicate type(s) of measurements the AIML model(s) may accept. In another example, an AIML functionality may indicate validity conditions for inference generated by the AIML model(s). In another example, an AIML functionality may indicate a validity condition for the AIML model(s). In another example, an AIML functionality may indicate type(s) of inference the AIML model(s) may generate (e.g., WTRU location, intermediate metric such as LOS indicator, measurement). In another example, an AIML functionality may indicate capabilities of the AIML model(s) (e.g., latency required to generate inference, the number of inputs, memory size, computational complexity). For example, an AIML functionality may be AIML based positioning. If the WTRU indicates the AIML based positioning as the supportable AIML functionality, it indicates that the WTRU may have an AIML model(s) which are capable of performing AIML based positioning. In another example, the WTRU may indicate that the supportable AIML functionality is BW aggregation based AIML-based positioning. This may indicate that the WTRU has an AIML model that may accept measurements made based on BW aggregation. In another example, the WTRU may indicate that supportable AIML functionality is PDP-based AIML based positioning. This may indicate that the AIML model the WTRU has may accept PDP as its inputs. In another example, the WTRU may indicate the supportable AIML functionality is AIML based positioning with indicated maximum synchronization error. This indicates that the WTRU may have AIML model(s) that may tolerate timing error or network synchronization error up to the indicated maximum synchronization error. Some tolerance in difference in assistance information and / or PRS configuration between training and inference may be allowed. For example, assistance information used by the WTRU to train an AIML model may be different from assistance information the WTRU receives when the WTRU is requested to generateinference based on the trained AIML model. For example, network synchronization error may be different by a few tenths of a micro-second between the training phase and inference phase and such difference may not affect inference performance. The WTRU may be preconfigured or configured with tolerance difference in assistance information between training and inference phase. If the difference is above the tolerable difference the WTRU may determine to use the fallback positioning method or report to the network that the WTRU may not perform AIML based positioning due to the difference. In another example, PRS configurations and / or assistance information may be the same. For example, between training and inference phase, PRS configuration parameters (e.g., Frequency Layer ID, TRP IDs and / or Cell IDs) may be the same for the AIML model to be valid. In another example, the WTRU may indicate that a supportable AIML functionality may accept N PDPs where each PDP is generated based on PRSs received from TRPs. In another example, the WTRU may indicate that the supportable AIML functionality is areabased AIML-based positioning. This may indicate that the WTRU is able to perform positioning with an AIML model(s) which may generate inference (e.g., WTRU location) in the area associated with the AIML model(s). In another example, the WTRU may indicate that the support for an AIM functionality with which INACTIVE mode base AIML based positioning may be achieved.

[0109] The WTRU may determine an applicable AIML functionality based on WTRU condition, WTRU capabilities, NW condition, and / or DL-RS configuration or assistance information given by the network. An AIML functionality may be identified through reporting of WTRU capabilities. The reported capabilities may be related to AIML capabilities (e.g., whether the WTRU is capable of supporting AIML based positioning), positioning capabilities (e.g., whether the WTRU is capable of supporting DL-TDOA, how many TRPs or PRSs the WTRU may measure) and / or communication capabilities (e.g., whether the WTRU is capable of supporting MIMO communication). An AIML functionality may be identified through WTRU side conditions, NW side conditions, and / or DL-RS configurations. For example, the WTRU may indicate that the WTRU has low battery power or hardware is overheating. Such condition may imply that the WTRU may support low-complexity AIML functionality (e.g., making measurements from the serving cell at large measurement periodicity). A DL-RS configuration may identify an AIML functionality. For example, if the DL-RS configuration indicates frequency layer aggregation, it may imply that the WTRU needs to use AIML model(s) that may accept measurements made from aggregated frequency layers as AIML inputs. NW side conditions may identify an AIML functionality. For example, if the NW assistance information indicates that there is a large synchronization error between TRPs or base stations at the network may indicate that the WTRU may use an AIML model(s) that is trained based on a similar condition (e.g., trained with data whichis generated at the same or similar range of synchronization error). An AIML functionality may be indicated by assistance information provided by the network (e.g., associated ID). More examples about the associated ID are described herein. In another example, the WTRU may determine an AIML functionality based on the content of a request sent by the network. For example, the network may send a request to perform positioning and / or AIML based positioning using an indicated set of measurements (e.g., PDP, timing, power, phase, angle measurements). The WTRU may receive a request to report measurements and / or WTRU location to the network. Based on the request about measurements and report content, the WTRU may determine an AIML functionality that may accept the requested measurements and / or yield the requested report content (e.g., WTRU location). The request may include an explicit indication of which functionality to use (e.g., via functionality ID). In another example, the WTRU may determine an AIML functionality based on a configured positioning method. For example, the WTRU may be configured with a timing-based positioning method (e.g., DL-TDOA) and the WTRU may receive, from the network, an indication to use an AIML model to determine the WTRU location. Based on the configured positioning method and / or assistance information, the WTRU may determine the AIML functionality (e.g., which AIML model(s) to use for positioning). In another example, the WTRU may receive a configuration for an AIML based positioning method and based on the configured positioning method, the WTRU may determine the AIML functionality.

[0110] Described herein are embodiments for enabling AIML functionality. Whether the WTRU may use the AIML functionality may depend on WTRU conditions, PRS configurations, and / or NW conditions. If WTRU conditions change dynamically, the WTRU may send an update to the network about supportable AIML functionalities.

[0111] Examples are described herein for capable functionalities. In one example, an AIML functionality may be associated with NW configurations (e.g., PRS configuration). For example, an AIML functionality may be associated with an area (e.g., including more than one cell). In another example, an AIML functionality may be associated with TRPs. In another example, the WTRU may receive a request to report AIML functionalities that the WTRU may support. The WTRU may indicate to the network that the WTRU may support area-based AIML based positioning by indicating the number of cells or TRPs that the WTRU may receive PRS and make measurements. In another example, an AIML functionality may be associated with a task such as positioning, beam management, etc. For example, the WTRU may receive a request to report an AIML functionality (e.g., AIML based positioning, AIML based beam management) that the WTRU may support.

[0112] In one example, an AIML functionality may be associated with hardware capability or software capability at the WTRU (e.g., processing power, battery power, memory size, supportable bandwidth, supported number of transmission or reception antennas). The WTRU may indicate capable functionalities to the network. A functionality may be defined by at least one of the following key performance indicators (KPIs) or capabilities and if the WTRU receives a request from the network, the WTRU may report one of the following KPIs.

[0113] The WTRU may report the accuracy for an area. For example, the WTRU may indicate achievable level accuracy for an area (e.g., less than 0.5 meters for a cell) for a functionality or AIML model. The WTRU may report a complexity (e.g., memory size, computation time, processing time). For example, the WTRU may indicate how long it may take to generate an inference for a functionality or AIML model. The WTRU may report an AIML model input type (e.g., CIR, PDP, DP). For example, the WTRU may indicate the inputs for an AIML model the WTRU is capable of supporting. The WTRU may report an input complexity (e.g., number of samples / paths pre Cl R / PDP / DP). For example, the WTRU may indicate the supportable number of inputs (e.g., number of TRSs, PRS resources) to make measurements on. The WTRU may indicate the number of samples or paths per CIR, PDP or DP the WTRU may make measurements on. The WTRU may report the number of cells, TRPs, zones or areas the WTRU may collect measurements from (e.g., a zone may be defined with respect to a reference point and zone may be expressed in terms of distance or area with respect to the reference point). The WTRU may report the number of BWPs, bandwidth or frequency layers the WTRU may measure. The WTRU may report the measurement type (e.g., power, timing, phase) the WTRU may measure. The WTRU may report the periodicity or frequency of inference generation or reporting generation (e.g., periodicity may be expressed in terms of slots, symbols, frames, subframes, or time unit such as seconds). The WTRU may report the duration for generating inference (e.g., expressed in seconds, minutes). The WTRU may report the RRC state (e.g., RRC_CONNECTED, INACTIVE, IDLE).

[0114] Examples of supportable functionalities are shown in Table 1.Table 1Examples of functionalities

[0115] Examples are provided herein for UE / NW side conditions associated with a functionality. For example, an AIML functionality may be associated with NW side condition or configuration. Examples are described below.

[0116] AIML functionality may be associated with PRS transmission timing with respect to the reference TRP, as described herein. For example, an AIML functionality may be applicable within a timing value. For each range of timing (e.g., first range may be 0 to 1 ps, second range may be 0 to 5ps , a separate AIML functionality may be defined. The range of uncertainty may be defined for TRPs in the configuration.

[0117] AIML functionality may be associated with uncertainty range of TRP locations, as described herein. For example, for each range of uncertainty in TRP locations (e.g., first range may be 0 to 0.1 meter, second range may be 0 to 1 meters), a separate AIML functionality may be defined. The range of uncertainty may be defined for TRPs in the configuration.

[0118] AIML functionality may be associated an error group at the network, as described herein. For example, a transmission timing error group which defines a range of transmission timing error at the network may be associated with an AIML functionality. Each timing error group may be associated with different range of timing error. In another example, a reception timing error group which defines a range of reception timing error at the network may be associated with an AIML functionality.

[0119] An AIML functionality may be associated with one or more parameters from PRS configurations. For example, an AIML functionality may be associated with bandwidth and / or frequency layer(s). An AIML functionality may be associated with a value of bandwidth (e.g., AIML functionality #1 associated with 100MHz, AIML functionality #1 associated with 20MHz). In another example, an AIML functionality may be associated with the number of frequency layers (e.g., 1 layer, 3 layers).

[0120] The WTRU may determine the AIML functionality based on NW side condition or configuration. An AIML functionality may be associated with a combination of the NW side conditions and / or configurations. For example, an AIML may be associated with a range of synchronization error at the network and bandwidth of PRS.

[0121] Embodiments are described herein for a hierarchy in AIML functionalities. For example, AIML functionalities may be configured in a hierarchical manner. Thus, an AIML functionality may be associated with more than one parameters in PRS configurations. For example, if an AIML functionality, indicated bythe associated ID, at a higher layer is activated, the WTRU may determine AIML functionalities under the activated AIML functionality based on WTRU conditions, NW conditions, and / or PRS configurations.

[0122] For example, the WTRU may receive an activation command for the AIML functionality. The WTRU may determine activated parameters (e.g., number of frequency layers to make measurements on, TRP IDs to receive PRSs from, neighboring cell IDs to make measurements) for the AIML functionality based on the PRS configuration.

[0123] In another example, the WTRU may receive an activation command for the AIML functionality associated with a cell. The WTRU may determine that the activated AIML functionality is also associated with PRS configurations (e.g., TRP IDs, PRS IDs, PRS resource set IDs, PRS resource IDs) associated with the cell. For example, if there are more than one PRS resource IDs associated with a frequency layer, the WTRU may determine that if an AIML functionality is associated with a frequency layer, the functionality is also associated with PRS resource IDs associated with the frequency layer. An example is illustrated in FIG. 6, which shows an example of hierarch of PRS parameters in an AIML functionality. As shown in FIG. 6, an AIML functionality #N may associated with the associated ID, PRS frequency layer #1 . The WTRU may determine PRS parameters associated with PRS frequency layer #N (e.g., PRS set I D#1 to #M, PRS resource IDs) are also activated if the AIML functionality #N is activated.

[0124] In one example, an AIML model may be associated with an area as shown in FIG. 7, which comprises an illustration of measurements the WTRU may make for different geographic coverage of an AIML model. For example, the area may include more than one cell. The area may include one cell. In another example, the area may include a portion of a cell, as shown in the figure. The area may be associated with a subset of TRPs in the cell.

[0125] Based on the geographical coverage of an AIML model, the number of measurements the WTRU makes may be different. For example, as illustrated in the figure, the WTRU may make measurements from PRSs transmitted from TRPs in the AIML model with TRP-level coverage 702. For cell level measurements, the WTRU may make measurements on transmitted PRSs from TRPs within the serving orindicated cell 704. For area-level measurements, the WTRU may make measurements on PRSs from the serving cell and neighboring cell 706.

[0126] Relationships between an AIML functionality and an AIML model are described herein. An AIML functionality may be associated with an AIML model. AIML functionality may be implemented by an AIML model. For example, a functionality index may include a model index implemented by an AIML model.

[0127] If an AIML functionality is activated or enabled, the WTRU may determine to make measurements on the PRSs whose configurations are associated with the AIML functionality. Based on the measurements, the WTRU may determine AIML inputs that correspond to the AIML model(s) associated with the activated or enabled AIML functionality.

[0128] In one example, an AIML functionality may be associated with one AIML model or more than one AIML models. Thus, an AIML functionality ID may correspond to more than one AIML models at the WTRU.

[0129] “AIML functionality” and “AIML positioning functionality” may be used interchangeably herein.

[0130] Examples of performance requirements provided by the network are described herein. The WTRU may receive performance requirement(s) from the network. The performance requirement from the network may include at least one of the following. The performance requirement from the network may include accuracy. For example, the required accuracy may be indicated by the network in meters (e.g., less than 1 meter of accuracy) or meters for an area (e.g., less than 0.5 meters of accuracy within 3 cells). The performance requirement from the network may include latency. For example, the required latency may be expressed in terms of seconds. The performance requirement from the network may include coverage. For example, the required coverage may be expressed in terms of units for an area (e.g., square meter), zone IDs, cell IDs or TRP IDs. Zones may be defined with respect to a reference point.

[0131] Embodiments are described herein for a determination of applicable functionality. The WTRU may determine the applicable functionality based on the associated ID and / or WTRU conditions. Provided herein are examples of what an associated ID may represent. In an example, an AIML functionality may be associated with one or more than one associated ID, where each associated ID may indicate WTRU or NW side configuration and / or condition. The WTRU may receive associated IDs from the network and the WTRU may determine the applicable functionality based on the received associated ID. Different associated IDs may be associated with different type of information in the assistance information. For example, a first associated ID may be associated with a cell ID. A second associated ID may be associatedwith a frequency layer ID. Based on the first and second associated ID, the WTRU may determine an applicable functionality.

[0132] In another example, an associated ID may be associated with a set of information elements in the assistance information (e.g., cell ID, network synchronization error). An associated ID may assist the WTRU to determine the applicable functionality. The associated ID may indicate a subset of the PRS configuration and / or assistance information (e.g., TRP locations). An associated ID may be locally or globally unique. An associated ID may be associated with a set of PRS configurations and / or assistance information and may be configured by the network (e.g., LMF). Once the associated ID is indicated, the WTRU may determine which model(s), under the identified functionality, to train and use for inference. If a PRS configuration parameter at a higher layer in the PRS configuration is associated with the associated ID, the WTRU may determine that the associated PRS configuration at a lower layer in the PSR configuration hierarchy is also configured. For example, a first associated ID may be associated with cell ID#1 and frequency layer ID#1. A second associated ID may be associated with cell ID#1 and frequency layer I D#2. An associated ID may be implicit or explicit. For example, the WTRU may be indicated or configured to use a cell ID as an associated ID. In another example, the WTRU may receive an explicit associated ID from the network.

[0133] A WTRU may determine applicable functionality based on the associated ID. An associated ID may be associated with at least one of the information elements in the assistance information provided by the network. Based on the associated ID, the WTRU may determine the associated ID based on the assistance information received by the network. For example, an associated ID may include at least one of the following. An associated ID may include a cell or area ID. For example, the WTRU may determine the applicable functionality based on the cell ID described in assistance information. The WTRU may determine that the applicable functionality should include the indicated cell or area ID. In another example, the WTRU may determine that the applicable functionality should support the number of cells indicated in the area ID. An example of area ID may include an ID assigned to a group of cells. An associated ID may include a group of TRP IDs. For example, the WTRU may determine an applicable functionality based on the group of TRP IDs provided in the assistance information. In another example, a group of TRP IDs may be associated with an ID which is the associated ID. An associated ID may include PRS resource I D(s) or PRS resource set I D(s). An associated ID may be associated with PRS resource I D(s) or PRS resource set ID(s). The WTRU may determine a AIML functionality based on the PRS resource ID(s) or PRS resource set I D(s) in the assistance information. An associated ID may include frequency information. For example,an associated ID may be associated with BW I D(s) or frequency layer ID(s). The WTRU may determine a functionality is applicable or not based on the frequency layer I D(s) or bandwidth I D(s) given in assistance information. An associated ID may include a synchronization error. For example, the WTRU may determine applicable functionality associated with the associated ID related to synchronization error. For example, an associated ID may be associated with a range of synchronization error (e.g, synchronization error ±0.5ps is associated with an associated ID #1) or maximum synchronization error (e.g., up to 0.5ps). An associated ID may include uncertainty in assistance information. For example, a range of uncertainty in TRP location, boresight direction of a PRS, beamwidth of a PRS, synchronization error, transmission and / or transmission or reception timing error may be associated with an associated ID. Another example of an associated ID may include a statistical value such as a standard deviation or variance.

[0134] WTRU conditions are described herein, which may include hard and / or soft conditions. The WTRU may determine the applicable functionality based on WTRU conditions or side conditions. In one example, the WTRU conditions may not be disclosed to the network. The LMF may not know the WTRU conditions (e.g., scheduling restriction imposed by base station). Examples of WTRU conditions are described below.

[0135] An example of WTRU conditions may include remaining battery power. An example of WTRU conditions may include operation mode (e.g., user switches its phone to low-power mode). An example operation mode may include low-power mode. In an example of low power mode, the user may switch the WTRU to low-power mode to prolong battery life, thus allowing more critical tasks to be performed for an extended period before recharging. In situations where the WTRU has access to multiple models with varying power demands, it may opt to use the AI / ML model that may require the least amount of power. An example operation mode may include a Stationary Mode. If the WTRU detects that the device has remained static for a configured duration, it may transition to the Stationary Mode. In this mode, the WTRU may continue to report its previous position without running inference on the AI / ML model. In one example, the WTRU may utilize the accelerometer to determine if the device is stationary. As soon as any movement is detected by the accelerometer, the WTRU may exit the Stationary Mode, and normal operations may resume. In one example, the WTRU may transition to a Sleep Mode, for example, during night hours when it is not in use. In such cases, the Stationary Mode may be implicitly inferred from the device being in Sleep Mode.

[0136] An example of WTRU conditions may include a system constraint. An example of a system constraint may include the priority of PRS compared to other downlink channels. For example, the WTRU may be configured with a prioritization window during which the WTRU may determine to prioritizereception of PRS based on the priority level associated with the window. An example of a system constraint may include an availability of measurement gap configuration. The WTRU may send a request to the network to configure a measurement gap so that the WTRU may make measurements on PRSs transmitted from neighboring cells. The WTRU may make measurements outside of the active BWP during the measurement gap. An example of a system constraint may include scheduling restrictions. For example, the WTRU may receive a cancellation indication for PRS. An example of a system constraint may include the state of the WTRU (e.g., RRCJNACTIVE). An example of a system constraint may include DRX or DTX.

[0137] Triggers are described herein for indicating applicable functionality. The WTRU may determine to indicate applicable functionalities based on WTRU conditions and trigger conditions for reporting the applicable functionality. Examples of trigger conditions may include at least one of the following.

[0138] Examples of trigger conditions may include periodic reporting or indication occasions. For example, the WTRU may be configured with periodic reporting occasions. The WTRU may be configured to monitor WTRU conditions periodically and if a condition(s) is / are satisfied the WTRU may determine to report WTRU conditions. For example, the WTRU may receive a threshold (e.g., battery power level) from the network. If the condition is satisfied, the WTRU may determine to report applicable functionalities to the network at the configured reporting occasions. The reporting occasions may be semi-static. The WTRU may receive an activation and / or deactivation command from the network, activating and / or deactivating periodic reporting duration(s) during which the WTRU is expected to check the configured condition.

[0139] The WTRU may receive a request from the network to indicate the applicable functionality. If the WTRU’s condition has not changed since the last reported occasion, the WTRU may not send an applicable functionality. In another example, the WTRU may send an indication that there is no change required for the functionality.

[0140] The WTRU may send an applicable functionality if the WTRU does not receive configurations from the network to receive PRS. Such configurations may include configurations for measurement gap. Without a measurement gap, the WTRU may not be able to make measurements outside of the active BWP. Thus, the WTRU may determine to indicate an applicable AIML functionality which may not require the WTRU to make measurements on PRS outside of the active BWP (e.g., an AIML functionality applicable to the serving cell only). In another example, the WTRU may receive low priority for PRS during a measurement processing window. In this case, the WTRU may not make measurements on PRS if PRSs and other downlink channels are scheduled within the window. The WTRU may send an indication to the networkindicating the AIML functionality associated with less frequent inference generation. The WTRU may determine to send the indication at a configured reporting or indication occasion. The WTRU may determine to request for an uplink resource from the network to send the indication.

[0141] The WTRU may send an applicable functionality to the LMF when the WTRU’s RRC state changes. For example, if the WTRU’s state changes from CONNECTED to INACTIVE, the WTRU may determine to send an indication to the network indicating an AIML functionality with power saving features (e.g., generates inference less frequently). In another example, the WTRU may send periodicity of measurement occasions or measurement reporting occasions to the LMF when the WTRU’s RRC state change. A measurement occasion may be defined as an instance at which the WTRU makes measurements on received PRS. A measurement reporting occasion may be defined as an instance at which the WTRU reports measurements.

[0142] Examples of trigger conditions may include DRX or DTX configurations. For example, if the WTRU is configured with DTX or DRX configuration (e.g., sleep duration, wake up frequency or duration, on duration), the WTRU may send an indication to the network, indicating an applicable AIML functionality (e.g., AIML functionality with less frequent inference generation).

[0143] Some of the conditions may include hard or soft conditions. For example, hard conditions may be defined as conditions that enable a functionality or AIML model. Examples of hard conditions may include at least one of the following.

[0144] An example of a hard condition may include area. For example, a functionality may be disabled or enabled if the WTRU is not located in the area (e.g., cell, a group of cells) associated with the functionality. The WTRU may determine whether an AIML functionality (e.g., AIML model works in a certain cell or area) is applicable or not based on the cell ID of the serving cell, for example.

[0145] An example of a hard condition may include configurations. For example, a functionality may be disabled if the WTRU is not configured or did not receive configurations associated with the functionality. An example of such configuration may include measurement gaps. If the WTRU did not receive configuration for the measurement gap, the WTRU may not be able to measure PRSs outside of the cell and the WTRU may not be able to perform an area based AIML based positioning where the area includes more than one cells, including the serving cell.

[0146] An example of a hard condition may include invalid AIML functionalities. The WTRU may indicate to the network that currently active or reported AIML functionalities are invalid since validity conditions are not satisfied. For example, if the currently active AIML functionality is valid within the serving cell and theWTRU moves out of the serving cell, the WTRU may determine that the currently active AIML functionality is not valid anymore.

[0147] An example of a hard condition may include the RRC state of the WTRU (e.g., RRCJNACTIVE). The WTRU may indicate to the network the state (e.g., RRCJNACTIVE state) the WTRU is at. The WTRU may receive an indication which AIML functionality to use from the network. In one example, the WTRU may determine to use the AIML functionality associated with the state.

[0148] In one example, soft conditions may be used by the network or WTRU to determine applicable functionalities. However, applicable functionality associated with soft conditions may be enabled, disabled, activated or deactivated by the network irrespective of the determined request from the WTRU. Examples of soft conditions may include at least one of the following.

[0149] An example of a soft condition may include remaining battery power. For example, the WTRU may determine to send an indication to the network indicating a preference of an AIML functionality or model which requires less battery power. The WTRU may receive an indication from the network to use an AIML functionality that may not be the functionality or model indicated by the WTRU. Examples of how the remaining battery power may affect the number of cells an AIML model may support are illustrated in FIG. 8 and FIG. 9. As illustrated in FIG. 8, which includes an example of supportable area depending on the remaining battery power, when the remaining battery power level is high at 802, the WTRU may be able to support an AIML functionality which covers the configured area. When the remaining battery power level is at medium level at 804, the WTRU may be able to support a subset of the configured area. When the remaining batter power level is low at 806, the WTRU may be able to support an AIML functionality that may work in one cell, the serving cell. Another example of supportable area depending on the remaining battery power is illustrated in FIG. 9. In this example, the WTRU is located in the corner of the configured area. Depending on the remaining battery power, the WTRU may determine to indicate how many adjacent cells the WTRU may support for AIML based positioning. In one example, the WTRU may determine the center of coverage based on the associated ID (e.g., cell ID). For example, as indicated in FIG. 9, the WTRU may determine that the center of geographical coverage for AIML-based positioning is the serving cell the WTRU is located in.

[0150] Embodiments are described herein for how applicable functionalities are determined. The WTRU may determine applicable functionality based on WTRU conditions, which may include at least one of the following criteria. The WTRU may determine applicable functionality based on associated I D(s) indicated by the network. An example embodiment in which the WTRU may use the associated ID to determine theapplicable functionality is described below. In the example embodiment, the WTRU may report supportable functionalities, if requested by the LMF. The WTRU may receive PRS configuration and / or assistance information along with the associated ID from the LMF. The WTRU may receive a request for measurements and / or reporting from the LMF. Based on the associated ID and / or the content of the request, the WTRU may report the applicable functionality to the network. In one example, reporting of applicable functionality may imply that an AIML model(s) associated with the functionality is ready to generate inference. The WTRU may determine applicable functionality based on WTRU side conditions. The WTRU may determine applicable functionality based on an explicit indication from the network about which AIML functionality to use. Examples are provided herein for how the WTRU determines applicable functionality based on WTRU condition. For example, if measurement gaps are not configured, the WTRU may measure PRS from the serving cell only. In this case, the WTRU may indicate functionalities that apply to the AIML model or functionality that is applicable to the serving cell or within the serving cell.

[0151] Examples are provided herein for RRC state and AIML functionality. The WTRU may determine the AIML functionality based on the RRC state. Configurations are described of an association between AIML functionality and RRC state. In one example, the WTRU may be configured with one or more than one AIML functionalities associated with an RRC state (e.g, RRCJDONNECTED, RRCJNACTIVE, IDLE). The WTRU may determine the applicable functionality based on the RRC state determined by data communication activity. The WTRU may receive AIML functionalities from the network when the WTRU transitions to RRCJNACTIVE state in RRC messages (e.g., RRC release) for example. If the WTRU determines to use the AIML functionality associated with the RRC state, the WTRU may send a request or message to the LMF that the WTRU needs to switch the AIML functionality. Once the WTRU receives an acknowledgement message from the LMF, granting permission for the switch, the WTRU may determine to use the AIML functionality to obtain WTRU location while the WTRU is in the associated RRC state. In one example, the WTRU may be configured with an AIML functionality that supports AIML based positioning in an area (e.g., including more than one cells). The AIML functionality may be associated with RRCJNACTIVE state. Thus, when the WTRU transitions to the RRCJNATIVE state, the WTRU may determine to activate the AIML functionality that is associated with the RRCJNACTIVE state. If there are more than one AIML functionalities, the WTRU may determine to activate the AIML functionality that meets other requirements indicated by the network (e.g., latency, accuracy). In another example, if the WTRU is inINACTIVE state, the WTRU may determine to use a low-complexity AIML model and / or determine inference less frequently.

[0152] Embodiments are described herein for sending a request when in an RRC state. When the WTRU is in INACTIVE mode, the WTRU may determine to send a request to the LMF with a preferred AIML functionality (e.g., with less frequent inference generation or inference reporting). The WTRU may send the request based on the configured occasions. The WTRU may send an unsolicited request, e.g., without a request from the network. The WTRU may request the base station for UL resources to send the request. The WTRU may use SDT (Small Data Transmission) to send the request. In another example, if the WTRU determines that the validity condition (e.g., area validity, timing validity) of the AIML functionality is invalid during RRCJNACTIVE, the WTRU may send a request (e.g., via LPP message) to the network for a new AIML functionality and / or associated ID. The WTRU may include a preferred AIML functionality and / or associated ID in the request. As the response for the request, the WTRU may obtain a new associated ID, PRS configurations, and / or AIML functionality ID. In another example, if the WTRUs’ RRC state changes, the WTRU may send applicable functionalities to the network. The WTRU may include such information in the RRC (e.g., measurement report) or LPP message (e.g, measurement report, capability reporting). The WTRU may send such request in a unsolicited manner.

[0153] Examples are described herein for treatment of the currently active AIML functionality if an RRC state changes. In one example, when the WTRU transitions from the IDLE or INACTIVE mode to RRC_CONNECTED, the WTRU may report capable AIML functionalities to the network. The WTRU may report capable AIML functionalities to the network after the initial access procedure is complete (e.g, the WTRU receives msg4 or msgB from the network). In another example, the WTRU may determine to deactivate the AIML functionality that the WTRU used during the previous state (e.g, RRCJNACTIVE) when the WTRU transitions into another state (e.g, RRC_CONNECTED). The WTRU may determine to request for AIML functionality from the network if the WTRU determines to deactivate the current AIML functionality. The WTRU may send a request to the network to activate the indicated AIML functionality if the WTRU determines to deactivate the current AIML functionality. In another example, the WTRU may continue to use the AIML functionality the WTRU used during the previous RRC state if at least one of the following conditions is satisfied. The condition may include if the WTRU is configured to continue to use the AIML functionality from the previous state. The condition may include if the WTRU determines to continue to use the AIML functionality as long as the WTRU side conditions (e.g, battery level) are met. The condition may include if the WTRU determines to continue to use the AIML functionality as long as validityconditions (e.g., area, time) are satisfied. The conditions described herein may be configured by the network (e.g., LMF, base station).

[0154] The WTRU may receive a request, from the LMF, to report supportable AIML functionalities. The WTRU may report AIML functionalities to the LMF. The WTRU may receive a request, from the LMF, for AIML based positioning with an indicated AIML functionality. The WTRU may use the indicated AIML functionality (e.g., a first AIML functionality) to obtain the WTRU location and report the WTRU location to the LMF. The WTRU may receive RRC_Release command from the base station. The WTRU may send a request to the LMF, requesting to activate an AIML functionality (e.g., a second AIML functionality) that is associated with RRCJNACTIVE state where the request includes the desired AIML functionality index. The WTRU may receive a deactivation command from the LMF for the first AIML functionality and / or may receive an activation command for the second AIML functionality. The WTRU may use the second AIML functionality to obtain the WTRU location until the WTRU transitions to RRC_CONNECTED to obtain the WTRU location and may report the WTRU location to the LMF. If the WTRU transitions into RRC_CONNECTED, the WTRU may deactivate the second AIML functionality.

[0155] Embodiments are provided herein for determination of AIML functionality based on performance requirements. The determination of the applicable functionality may be affected by performance requirements. The WTRU may be configured to report applicable functionalities that meet performance requirement(s) imposed by the network. For example, the WTRU may determine that the applicable functionality determined based on the WTRU condition may not satisfy the performance requirement indicated by the network. In this case, the WTRU may determine that there are no applicable functionalities. The WTRU may determine to prioritize applicable functionalities that meet the requirement indicated by the network. The WTRU may be configured to determine to prioritize WTRU condition (e.g., remaining battery power) to determine the applicable functionality. In this case, the WTRU may indicate applicable functionality which may not satisfy the performance requirement imposed by the network.

[0156] WTRU conditions (e.g., battery power) may affect one of the following parameters. The parameters may include a validity condition of the AIML model (e.g., remaining battery power may reduce the validity area). The parameters may include types of measurements it may make (e.g., low battery power means the WTRU may make time and / or power measurements, limiting its inputs to PDP (power delay profile) or DP (delay profile), potentially switching to an AIML model that use DP instead of PDP). The parameters may include an amount of time to generate inference (e.g., low battery power may increase the processing time). The parameters may include a number of paths / samples it may generate for Cl R / PDP / DP. Theparameters may include a number of AIML models supported. The parameters may include a frequency of inference generation of AIML based positioning (e.g., low battery power may reduce frequency of inference generation). The parameters may include a frequency of reporting of AIML based positioning (e.g., low battery power may reduce frequency of reporting).

[0157] Examples are provided herein describing the relationships between first and second set of functionalities. In one example, if the WTRU may receive a request from the network, the WTRU may indicate a first set of functionalities. Based on the WTRU condition, the WTRU may determine to indicate applicable functionalities to the network which may include a second set of functionalities. The second set of functionalities may include a subset of the first set of functionalities. Examples of the first and second set of functionalities are described herein.

[0158] The first set of functionalities may include an area with N elements and / or at least one functionality in the second set of functionalities may include an area with M elements where N>M. For example, the first set may include {1 , 3, 5} cells while the second set may include {1 , 3} cells. The first set of functionalities may include inference generation or reporting periodicity including {T1 , T2, T3} and / or second set may include {T2, T3} where the unit may include seconds, frames, subframes or slots. The first set of functionalities may include bandwidth with {B1 , B2, B3) and / or second set may include {B1 , B2) where the unit is Hz. The first set of functionalities may include measurement types including power, phase and relative timing and / or at least one functionality in the second set of functionalities may include power and relative timing. Another functionality in the second set may include relative timing. The first set of functionalities may include the number of samplers for CIR, PDP or DP including {N1 , N2, N3} and / or the second set of functionalities may include {N1 , N2}. The first set of functionalities may include the number of frequency layers or frequency layer ID, {FL1 , FL2, FL3) and / or second set may include {FL1 , FL2) where FL1 indicates frequency layer I D#1. In another example, the first set may include the number of supportable frequency layers {1 , 2, 3, 4} and / or the second set may include {1 , 2}. The first set of functionalities may include number of samples per CIR, PDP, DP measurement, e.g., {N1 , N2, N3} and / or the second set of functionalities may include {N1 }.

[0159] The first set of functionalities may depend on the WTRU condition. For example, the WTRU may receive a request from the network to report supportable AIML functionalities. The WTRU may report or indicate functionalities based on the remaining battery power. At a different occasion, the WTRU may receive a request from the network. If the remaining battery power is sufficient, the WTRU may report a second set of AIML functionalities which may include the first set of AIML functionalities. The WTRU mayindicate more AIML functionalities in the second set compared to the AIML functionalities reported in the first set. First and second set of functionality may include a combination of the examples described herein.

[0160] Examples are described herein for provision of application functionalities from the network. In one example, the WTRU may receive applicable functionalities from the network. An example is illustrated in FIG. 10. The WTRU may receive a request from the network to report capable functionalities at 1002. The WTRU may report supported functionalities of the WTRU at 1004. At 1006, the WTRU may receive applicable functionalities which, for example, may be a subset of the capable functionalities reported at 1004. At 1008, the WTRU may receive a request for AIML positioning with indicated functionality. The WTRU may send a request for measurement gap configuration to the base station at 1010. The WTRU may receive measurement gap configuration from the base station. At 1012, the WTRU may receive a measurement gap configuration from the base station. The WTRU may receive a request for a report of WTRU conditions at 1014. The WTRU may send a report including the WTRU conditions at 1016 (e.g., remaining battery power, status of measurement gap configuration, Priority level of PRS compared to DL channels such as PDCCH, PDSCH). The WTRU may receive an activation command activating one of the applicable functionalities from the LMF. At 1018, the WTRU may receive assistance information including PRS configurations related to the activated functionality and / or receive an acknowledgement.

[0161] In one example, a functionality may be associated with PRS configuration(s). Thus the WTRU may determine PRS configuration based on enabled or activated AIML functionality.

[0162] Validity conditions are described herein for AIML functionality. The WTRU may determine applicable functionalities based on a validity condition(s) associated with an AIML functionality. The validity conditions may include an area validity. For example, the WTRU may receive an associated ID (e.g., cell ID). Based on the associated ID the WTRU may determine the applicable AIML functionality. If the WTRU is not in the cell corresponding to the indicated cell ID, the WTRU may determine that the AIML functionality is not applicable. Thus, the WTRU may send a request to the network to deactivate the currently active AIML functionality. The WTRU may fall back to the configured fallback positioning method (e.g., GNSS, DL- TDOA), if the WTRU determines that the currently active AIML functionality is not valid anymore.

[0163] The validity conditions may include a time validity. The WTRU may determine that the AIML functionality is not valid if a validity timer associated with the AIML functionality expires. The WTRU maystart the validity timer if the WTRU receives an activation command for the AIML functionality from the network.

[0164] The validity conditions may include a configuration validity. In one example, the WTRU may determine that the AIML functionality is not valid if a PRS configuration associated with the AIML functionality is not aligned with the PRS configuration given by the network. For example, an AIML functionality which may support 3 PRS frequency layers may be activated by the network. The WTRU may determine that the activated AIML functionality is not valid if the network disables frequency layer aggregation, disabling 3-PRS frequency layer aggregation.

[0165] The validity conditions may include an RRC state validity. In one example, an AIML functionality may be valid for a RRC state. For example, an AIML functionality may be valid while the WTRU is in RRC_CONNECTED, RRCJNACTIVE or RRCJDLE state. Based on the RRC state, the WTRU may determine to activate or enable the AIML functionality associated with the RRC state. For example, the WTRU may be configured with an AIML functionality that is applicable for the serving cell during RRC CONNECTED state. The WTRU may be configured with an AIML functionality that is applicable for the serving or camping cell and neighboring cells for RRC INACTIVE state. The WTRU may be configured with the AIML functionality with N inputs for an AIML model for RRCJDONNECTED state while the AIML functionality associated with RRCJNACTIVE state has M inputs where N>M. In one example, if the RRC state validity condition for the AIML functionality is not satisfied (e.g., the WTRU’s RRC state changes), the WTRU may send a request to the network for AIML functionalities. The WTRU may determine a set of valid AIML functionalities based on the RRC state. Once the RRC state changes, the WTRU may send an indication to the network (e.g., LMF) that the AIML functionality changed based on the RRC state. The WTRU may be configured with AIML functionalities associated with each of the RRC state. If the RRC state validity condition is not satisfied, the WTRU may determine to deactivate the AIML functionality and / or indicate to the network (e.g., LMF) that the AIML functionality is deactivated.

[0166] Examples are described herein for activation and / or deactivation of applicable AIML functionality. In one example, the WTRU may receive an activation command from the network where the activation command may indicate the applicable functionality. The WTRU may indicate one or more than one applicable functionalities to the network where each functionality may be associated with an ID. The WTRU may receive an activation command from the network via RRC, LPP, MAC-CE or DCI, for example.

[0167] The activation command may include one or more types of information. For example, the activation command may include a functionality ID. The activation command may include a timing at whichthe indicated functionality should be indicated. The timing information may include absolute time and / or relative time compared to a reference time (e.g., when the WTRU received the activation command from the network). The activation command may include a duration of activation. The duration of activation may indicate how long the WTRU may use the indicated AIML functionality. The activation command may include a start and / or end time of usage of the activated AIML functionality. The activated AIML functionality may be deactivated by a deactivation command sent by the network.

[0168] Embodiments are described herein for fallback WTRU behavior. In one example, the WTRU may determine to use a fallback positioning method. A potential fallback positioning method may include DL- TDOA, DL-AoD, GNSS, etc. In one example, the WTRU may determine to use the positioning method indicated by the network. In another example, the WTRU may determine to use the configured fallback positioning method if an applicable functionality is not available at the WTRU. The applicable functionality may not be available at the WTRU if at least one of the following conditions is satisfied. An example condition may include that no AIML functionalities satisfy the WTRU condition(s). An example condition may include that no AIML functionalities are aligned with NW configuration and / or associated ID. In one example, the WTRU may indicate to the network that the WTRU is falling back to the configured positioning method. If the WTRU receives an acknowledgement message from the network, the WTRU may determine to use the fallback positioning method.

[0169] In an example embodiment, the WTRU may indicate capable functionalities (e.g., the 6 capable functionalities shown in Table 1). The WTRU may receive PRS configurations and / or cell IDs from which PRSs may be transmitted and / or accuracy requirement (e.g., less than 1 meter) from the network. The WTRU may indicate that the WTRU may support one or more of the capable functionalities. For example, the WTRU may indicate that the WTRU may support functionality number 6 of the capable functionalities in Table 1 , indicating that the measurement gap is not configured by the base station (e.g., the WTRU may measure PRSs from the serving cell). The WTRU may receive a request for a DL-TDOA (non AIML based positioning).

[0170] Examples are described herein illustrating a change of functionality during AIML based positioning. Exchange of signals between the WTRU and LMF is shown in FIG. 11 . If the WTRU receives a request from the LMF, the WTRU may report supported functionalities to the LMF at 1102. The WTRU may receive assistance information and / or an acknowledgment from the LMF at 1104. The WTRU may report applicable functionalities to the LMF at 1106. The WTRU may receive a request for AIML based positioning with indicated functionality from the LMF at 1108. Based on the WTRU conditions, the WTRU may send arequest for a change in the AIML functionality 1110. The WTRU may indicate preferred AIML functionalities to the LMF. At 1112, the WTRU may receive assistance information (e.g., associated ID) from the LMF which, for example, may indicate the functionality the WTRU is to use to determine the WTRU location.

[0171] Examples are provided herein for causes of a request for change of the configured AIML functionality. Some WTRU conditions may change dynamically. An example WTRU condition that may change dynamically may include WTRU battery power, mobility, and / or priority of PRS.

[0172] The WTRU may send a request for a change of functionality in an unsolicited manner (e.g., without a request from the network). The WTRU may be configured with occasions by the network at which the WTRU may send an unsolicited request (e.g., for a change of functionality, request to change the functionality to indicated AIML functionality). The WTRU may send an indication of a preferred AIML functionality to the network. In the request, the WTRU may include the cause for the request (e.g., how much battery power is remaining by indicating percentage of battery left, how fast the WTRU is moving, priority level of the PRS, availability of measurement gap). WTRU battery power level may be associated with how many surrounding cells the AIML model may support. If one-cell AIML functionality is selected, the NW or WTRU may determine that the cell corresponds to the serving cell.

[0173] Examples are described herein for requests for an activation or deactivation of an AIML functionality. In one example, the WTRU may determine to send a request for activation or deactivation of an AIML functionality based on a WTRU condition. In one example, the WTRU may send a request for deactivation of the current AIML functionality to the network if the WTRU determines that the activated AIML functionality may not be supported due to the WTRU condition (e.g., low battery power). The WTRU may include a functionality ID in the deactivation request. The WTRU may send an activation request for an AIML functionality based on the WTRU condition. The WTRU may include a functionality ID in the activation request. The activation command may include a functionality ID which may include one of the applicable functionality IDs and / or supportable functionality IDs indicated by the WTRU.

[0174] An exemplary embodiment is shown in FIG. 12, which illustrates an example of signaling exchange between the WTRU, a base station, and LMF. The WTRU may receive a request from the LMF for supportable functionalities at 1202. The WTRU may indicate the supportable functionalities (e.g., a list of numbers of cells the WTRU’s AIML model(s) may support) to the LMF at 1204. The WTRU may receive assistance information related to positioning from the LMF at 1206. At 1208, the WTRU may indicate applicable functionalities to the network based on the received assistance information and / or WTRU conditions. The WTRU may receive a request for AIML based positioning from the network with a firstfunctionality (e.g., serving cell ID and neighboring cell ID) at 1210. The WTRU may send a request for configuration of measurement gap(s) from the base station at 1212. The WTRU may receive measurement gap configuration from the base station at 1214. Based on the measurement gap configuration, the WTRU may determine to send an activation for a second AIML functionality (e.g., serving cell ID) at 1216, which for example, is different from the first functionality indicated by the network. The WTRU may send a deactivation request to the LMF with the ID for the first functionality. The WTRU may receive assistance information associated with the second functionality and / or an acknowledgment from the LMF at 1218. The WTRU may receive PRS configurations from the LMF. Based on the measurements made on the PRS, the WTRU may determine inputs for the AIML model at the WTRU and may obtain the WTRU location estimate from the AIML model. The WTRU may report the WTRU location estimate. The request for a measurement gap from the WTRU may be sent in an RRC message.

[0175] The WTRU may receive a request from the LMF (e.g., via an LPP message) to report capable AIML functionalities. The WTRU may report the number of cells (e.g., 1, 3, 5) the WTRU may support for AIML-based positioning. The WTRU may receive an associated ID (e.g., serving cell ID and / or a neighboring cell ID), and / or associated PRS configurations (e.g., TRP IDs, PRS IDs). The WTRU may determine the AIML functionality associated with the associated ID. The WTRU may send a request for measurement gap configuration to the base station. If the WTRU does not receive a measurement gap configuration within the time window, the WTRU may send an activation request to the LMF to activate the AIML functionality applicable for the serving cell only and the request may include the cause (e.g., no measurement gap is configured). The WTRU may receive an associated ID from the network as a response for the request. If there are no applicable AIML functionalities, the WTRU may determine to use the configured fallback positioning method. If the WTRU receives the measurement gap configuration within the time window, the WTRU may determine to use the AIML functionality associated with the associated ID to generate WTRU location. The WTRU may receive PRS configurations from the LMF. The WTRU may determine WTRU location based on the determined AIML functionality and the WTRU may report the WTRU location to the LMF.

[0176] The WTRU may receive a request from the network to report capable functionalities. The WTRU may indicate one or more functionalities (e.g., functionality number 6 shown in Table 1). The WTRU may receive PRS configurations and / or cell IDs from which PRSs are transmitted and accuracy requirement(s) (e.g., less than 1 meter) from the network and 5-cell area. The WTRU may indicate that the WTRU will use another functionality (e.g., functionality number 2 in the Table 1, which may indicate the default rule is touse the highest-accuracy model). The WTRU may receive acknowledgement from the network. The WTRLI may request to use functionality #1 of Table 1 (e.g., lack of battery power). The WTRU may receive a request for a DL-TDOA (non AIML based positioning).

[0177] Based on the proposed method, the WTRU may be configured with a positioning method which allows the WTRU to perform positioning continuously even when WTRU conditions change.

Claims

1. CLAIMS:1 . A wireless transmit / receive unit (WTRU) comprising: a processor configured to: determine applicable artificial intelligence (Al) / machine learning (ML) positioning functionality supported by the WTRU based on one or more conditions and assistance information, wherein the one or more conditions comprise at least one of battery power, location, or an availability of a measurement gap; send a request to activate the applicable AI / ML positioning functionality based on the WTRU not receiving a measurement gap configuration within a time window; receive an activation command to activate the applicable AI / ML positioning functionality; and activate the applicable AI / ML positioning functionality based on the indication.

2. The WTRU of claim 1 , wherein the assistance information comprises an associated identifier, wherein the applicable AI / ML positioning functionality is associated with the associated identifier, and wherein the associated identifier indicates a configuration or condition associated with the WTRU or a network.

3. The WTRU of claim 2, wherein the associated identifier indicates a cell identifier, an area identifier, a positioning reference signals (PRS) configuration, or a transmit-receive point (TRP) location.

4. The WTRU of claim 1 , wherein the processor is configured to: determine applicable AI / ML positioning functionality supported by the WTRU further based on a number of cells the WTRU can support through AI / ML based positioning.

5. The WTRU of claim 1 , wherein the processor is configured to: receive an indication of the time window from a network.

6. The WTRU of claim 1 , wherein the processor is configured to: receive a request from a location management function (LMF) to report the applicable AI / ML positioning functionality.

7. The WTRU of claim 1 , wherein the processor is configured to determine to use a fallback positioning method when there is no applicable AI / ML positioning functionality.

8. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: determining applicable artificial intelligence (Al) / machine learning (ML) positioning functionality supported by the WTRU based on one or more conditions and assistance information, wherein the one or more conditions comprise at least one of battery power, location, or an availability of a measurement gap; sending a request to activate the applicable AI / ML positioning functionality based on the WTRU not receiving a measurement gap configuration within a time window; receiving an activation command to activate the applicable AI / ML positioning functionality; and activating the applicable AI / ML positioning functionality based on the indication.

9. The method of claim 8, wherein the assistance information comprises an associated identifier.

10. The method of claim 9, wherein the associated identifier indicates a cell identifier, an area identifier, a positioning reference signals (PRS) configuration, or a transmit-receive point (TRP) location.11 . The method of claim 8, further comprising: determining AI / ML positioning functionality is further based on the number of cells the WTRU can support through AI / ML based positioning.

12. The method of claim 8, further comprising: receiving an indication of the time window from a network.

13. The method of claim 8, further comprising: receiving a request from a location management function (LMF) to report the applicable AI / ML positioning functionality.

14. A wireless transmit / receive unit (WTRU) comprising: a processor and memory configured to:receive a positioning reference signals (PRS) configuration and an associated identifier, wherein the associated identifier indicates one or more transmit-receive point (TRP) locations; determine an applicable artificial intelligence (Al) / machine learning (ML) positioning functionality supported by the WTRU based on the PRS configuration and the associated identifier; and send a request to activate the applicable AI / ML positioning functionality.

15. The WTRU of claim 14, wherein the processor is configured to: send an indication of the number of cells the WTRU can support for AI / ML positioning.

16. The WTRU of claim 14, wherein the associated identifier indicates one or more of PRS identifiers, PRS resource set identifiers, or PRS resource identifiers.

17. The WTRU of claim 14, wherein the processor is configured to: determine a fallback when there is no applicable AI / ML positioning functionality.

18. The WTRU of claim 14, wherein the processor is configured to: receive a request from a location management function (LMF) to report a capable AI / ML positioning functionality.

19. The WTRU of claim 14, wherein the request to activate the applicable AI / ML positioning functionality is based on the WTRU not receiving a measurement gap configuration within a time window.

20. The WTRU of claim 14, wherein the processor is configured to: determine a location of the WTRU based on the determined AI / ML positioning functionality; and send, to a location management function (LMF), a report comprising the location of the WTRU.

Images