Methods for enabling ai / ML-based positioning

Abstract

An access mobility and management device (AMF) may receive a location request for a current location of a wireless transmit / receive unit (WTRU). An AMF may select one or more network data analytics functions (NWDAF), one or more AI / ML models that perform AI / ML based positioning, and / or a location management function (LMF). The LMF may support AI / ML based positioning and the selected one or more AI / ML models. The AMF may send, to the selected LMF, the location request, and / or information associated with each of the selected one or more AI / ML models. The AMF may receive, from the selected LMF, a response indicating the current location of the WTRU.

Description

METHODS FOR ENABLING AI / ML-BASED POSITIONINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 553,063, filed on February 13, 2024, the entire contents of which are incorporated herein by reference.BACKGROUND

[0002] The 5G network support for location services is defined in Release 18 standards. A location management function (LMF) may play a central role in this framework. The LMF may perform the new radio positioning protocol A (NRPPa) procedures with the user equipment (UE), also known as the wireless transmit / receive unit (WTRU), and / or its serving radio access network (RAN) to collect measurements and / or determine the WTRU location. Mobile Originated (e.g., location request initiated by a WTRU) and / or Mobile Terminated (e.g., location request initiated by an external location services (LCS) client) location procedures may be supported.SUMMARY

[0003] A first network device and / or function (e.g., an access mobility and management device (AMF)) may receive a location request for a current location of a wireless transmit / receive unit (WTRU). The first network device and / or function (e.g., AMF) may select one or more of a second network device and / or function (e.g., a network data analytics functions (NWDAF)), one or more artificial intelligence or machine learning models (AI / ML) models that perform AI / ML based positioning, and / or a third network device and / or function (e.g., a location management function (LMF)). The third network device and / or function (e.g., LMF) may support AI / ML based positioning and the selected one or more AI / ML models. The first network device and / or function (e.g., AMF) may send to the selected third network device and / or function (e.g., LMF) , the location request, and / or information associated with each of the selected one or more AI / ML models. The first network device and / or function (e.g., AMF) may receive fromthe selected third network device and / or function (e.g., LMF), a response indicating the current location of the WTRU.

[0004] The location request may be sent by a location services client, by a gateway mobile location center (GMLC), and / or by a location services client via a GMLC. The first network device and / or function (e.g., AMF) may send, to the selected third network device and / or function (e.g., LMF), an indication that the first network device and / or function (e.g., AMF) has determined that AI / ML based positioning is expected, and one or more addresses associated with each of the selected second network device and / or function (e.g., NWDAFs). The information associated with each of the selected one or more AI / ML models comprises one or more identifiers of the selected AI / ML model.

[0005] The first network device and / or function (e.g., AMF) may determine whether to apply an AI / ML based positioning based on one or more of the availability of the AI / ML model for the WTRU, availability of the AI / ML model for the area, availability of the third network device and / or function (e.g., LMF) supporting the AI / ML-based positioning, and / or whether the WTRU supports a positioning measurement required by the AI / ML model. One or more of the AI / ML models may be stored within the one or more of the second network device and / or function (e.g., NWDAFs). Each of the one or more second network device and / or function (e.g., NWDAFs) may further comprise a fourth network device and / or function (e.g., a model training logical function (MTLF)). The fourth network device and / or function (e g., MTLF) may train the one or more AI / ML models stored on the one or more second network device and / or function (e.g., NWDAFs).

[0006] A fifth network device and / or function (e.g., a network repository function (NRF)) may provide the first network device and / or function (e.g., AMF) with one or more identifiers of the one or more AI / ML models that the third network device and / or function (e.g., LMF) supports. The response may include one or more identifiers of the AI / ML model used to perform AI / ML based positioning. The first network device and / or function (e.g., AMF may send the response to a gateway mobile location center (GMLC), location services client, and / or a locations services client via a GMLC.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0011] FIG. 2 depicts an example AMF-initiated model transfer to LMF.

[0012] FIG. 3 depicts an example AMF-initiated model transfer to LMF.DETAILED DESCRIPTION

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

[0014] 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 othernetworks 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 subscriptionbased 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 headmounted 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.

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

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

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

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

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

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

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

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

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

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

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

[0026] 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. 1 A may be configured to communicate with the base station 114a, which may employ acellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

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

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

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

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

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

[0032] 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 lightemitting 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), readonly 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).

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

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

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

[0036] 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 (notshown) or via processor 118). In an embodiment, the WRTU 102 may include a halfduplex 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)).

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

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

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

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

[0041] 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 acontrol plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

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

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

[0044] The ON 106 may facilitate communications with other networks. For example, the ON 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.

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

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

[0047] 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 tothe 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 (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

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

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

[0050] 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+80configuration, 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).

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

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

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

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

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

[0056] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c usingsubframe 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).

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

[0058] 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. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

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

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

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

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

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

[0064] In view of Figures 1 A-1 D, and the corresponding description of Figures 1 A-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.

[0065] 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 perform testing using over-the-air wireless communications.

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

[0067] An access mobility and management device (AMF) may collect the artificial intelligence and machine learning (AI / ML) models for positioning purposes from the network data analytics functions (NWDAF) and / or model training logical function (MTLF) before a LCS procedure occurs. During a location services (LCS) procedure, the AMF may select and / or send suitable models to the selected location management function (LMF) to perform AI / ML-based positioning.

[0068] During a LCS procedure, the AMF may inform the selected LMF of the NWDAF and / or MTLF address and the LMF retrieves the necessary AI / ML models from the NWDAF and / or MTLF and use them for AI / ML-based positioning.

[0069] 3GPP has been introducing AI / ML capabilities in its standards since Release 16. On the core network side, the System Architecture working groups have defined a framework with centralized NWDAF to support data analytics provisioning.

[0070] The radio access network (RAN) working group also has started study on AI / ML for NR interfaces in Release 18. Positioning accuracy enhancement using AI / ML capabilities is an important component of the study. The following two models are defined for positioning: direct AI / ML positioning and AI / ML assisted positioning.

[0071] In the direct AI / ML positioning model, the AI / ML model directly generates the positioning output. For example, the AI / ML model trained in the serving next generation radio access network (NG-RAN) may use fingerprinting based on channel observation as the input and generates the positioning result.

[0072] In the AI / ML assisted positioning model, the AI / ML model does not directly generate the positioning output but. Rather, the AI / ML assisted positioning model may be used to process and / or enhance the positioning measurements for more accurate positioning determination.

[0073] The AI / ML models that support direct or assisted AI / ML positioning may be in various entities, such as WTRU, NG-RAN, LMF, and / or NWDAF. Thus, there may be different combinations of the entities that provide AI / ML-enhanced measurements. There may be different combinations of the entities that can perform the final model inference to produce the positioning result.

[0074] Assuming the model inference for positioning is performed in 5G core (5GC) LMFs, as described by Case 2b (e.g., WTRU-assisted / LMF-based positioning with LMF- side model), and Case 3b (e.g., NG-RAN node assisted positioning with LMF-side model) in technical report (TR) 38.843, and also assuming the model training is performed in 5GC NWDAF(s), new methods may be needed for the LMF to obtain the necessary model(s) from the NWDAF(s).

[0075] New methods may address how the model(s) transfer triggered and / or initiated; how to identify the model(s) to be transferred; and / or the CN interface and / or procedure enhancements that facilitates model transfer between NWDAF(s) and / or LMF(s).

[0076] An AMF initiated model transfer may be provided for LMF-side model. For example, AMF may initiate model transfer to LMF. An 5GC AMF may perform the one or more of the following actions for AI / ML-based positioning. The AMF may retrieve and / or store AI / ML model(s) for positioning purposes from the NWDAF. The AMF may determine whether AI / ML-based positioning is used based on one or more factors. The AMF may select an LMF that supports AI / ML-based positioning and / or select the AI / ML model(s) from the local repository. The AMF may send the AI / ML model(s) to the LMF.

[0077] In this solution, it is assumed that some NWDAF and / or MTLF(s) in 5GC, which supports AI / ML-based positioning, has available AI / ML models trained for positioning purposes. In this solution, a model identifier (ID) may uniquely identify a model. The supported AI / ML models of a NWDAF and / or MTLF may be known to other network functions (NFs) (e.g. AMF) via local configuration and / or network repository function (NRF) query. It is also assumed that some LMF(s) in 5GC support using AI / ML model inference for positioning results. Whether a LMF supports AI / ML model inference, and / or the model IDs that the LMF supports may be known to other NFs (e.g., AMF) via local configuration and / or NRF query.

[0078] In one option, as depicted in FIG. 2, an AMF that supports AI / ML-based positioning, may subscribe to a NWDAF’s and / or a MTLF’s model provisioning service to obtain AI / ML models for positioning. The AMF may locally store the obtained AI / ML models in its local model repository. When a LCS procedure is initiated, and / or the AMF has selected a LMF that supports AI / ML model inference for positioning, the AMF may select one or more models from its local model repository. The AMF may select based on the area that the target WTRU is in and / or transfer the selected model(s) to the LMF. The LMF may use the received model to perform inference and / or produce positioning results.

[0079] FIG. 2 depicts an example AMF-initiated model transfer 200 to LMF. An AMF that supports AI / ML-based positioning may invoke model provisioning service of the NWDAF and / or MTLF to obtain AI / ML models for positioning purposes. At 204, the AMF may send a Nnwdaf_MLModellnfo_Request to the selected NWDAF. In addition to existing model filer information, such as “Area of Interest”, specified for this request, the AMF may also include new filters designed for positioning related analytics. For example, the AMF may specify one or more “output type(s)”. One example of the desired output type may be WTRU position. Another example of the desired output type may be the time difference of arrival (TDoA) which may be further used to calculate the WTRU position. At 204, the NWDAF may return the requested model information to the AMF in Nnwdaf_MLModellnfo_Response.

[0080] Based on the received model information, the AMF may further interact with other NFs, such as ADRF (not shown in FIG. 2), to retrieve the AI / ML models. At 208, the AMF may locally store the retrieved models and manage them, e.g., purge obsolete models that are no longer valid. At 212, an external LCS client may sends a LCS request to a gateway mobile location center (GMLC) for a target WTRU location.

[0081] The GMLC may obtain the serving AMF address from, e.g., a unified data management (UDM) (not shown in FIG. 2). At 216, the GMLC may invoke the Namf_Location_ProvidePositioninglnfo service operation towards the AMF to request the current location of the WTRU.

[0082] At 220, the AMF may determine that AI / ML-based positioning may apply to this request. The AMF may base its determination on multiple factors: whether the AI / MLmodel for the target WTRU area is available, whether the LMF supporting the AI / ML- based positioning is available, whether the WTRU supports the positioning measurement required by the AI / ML model, etc.

[0083] At 224, the AMF may select the LMF that supports AI / ML-based positioning and / or the LMF’s supported models available in the AMF’s local repository. The AMF then select one or more AI / ML models for the LMF to use. The selection of AI / ML models may be based on LMF’s supported model IDs, target area, and / or positioning accuracy requirements, etc. Alternatively, the AMF may initiate a negotiation procedure with the selected LMF (not shown in FIG. 2), to obtain more specific information (e.g. positioning method, and / or supported positioning measurements, etc.) of the LMF’s support for AI / ML-based positioning. The AMF may use the obtained information for better AI / ML model selection.

[0084] At 228, the AMF may invoke the Nlmf_Location_DetermineLocation service operation towards the LMF to request the current location of the WTRU. In the request, the AMF may indicate AI / ML-based positioning is expected and include the selected AI / ML model(s). At 232, the LMF may collect positioning measurements required as the AI / ML model input by interacting with the WTRU and / or the RAN node. At 236, the LMF may perform the model inference to obtain AI / ML-based positioning result. If for some reason that AI / ML-based positioning is not executable, e.g. the required data input is not available, the LMF may revert to traditional positioning method.

[0085] At 240, the LMF may return the Nlmf_Location_DetermineLocation Response towards the AMF to return the current location of the WTRU. The LMF may indicate in the response whether the result is obtained through AI / ML-based positioning or traditional positioning. The LMF may append more details of the AI / ML-based positioning method such as the used Model ID, etc.

[0086] At 244, the AMF may return the Namf_Location_ProvidePositioninglnfo Response towards the GMLC / LRF to return the current location of the WTRU. At 248, the GMLC may send the location service response to the external location services client.

[0087] In another example, an 5GC AMF may perform one or more of the following actions for AI / ML-based positioning: the AMF may determine one or more desired AI / MLmodels for the location service request, e.g., based on required positioning performance (e.g., accuracy and / or latency, etc.) and / or applicable areas, etc. The AMF may locate the NWDAF(s) that may provide desired AI / ML models for AI / ML-based positioning.The AMF may select the LMF that supports AI / ML-based positioning. The AMF may inform the LMF the NWDAF address that the LMF may request the desired AI / ML models.

[0088] In this solution, as described in FIG. 3, when a LCS procedure is initiated, and / or the AMF has selected a LMF that supports AI / ML model inference for positioning, the AMF may inform the LMF the address of NWDAF and / or MTLF which has available AI / ML models for positioning. The LMF may then request the NWDAF to provide one or more models.

[0089] FIG. 3 depicts another example AMF-initiated model transfer to LMF. At 304, an external LCS client sends a LCS request to the GMLC for a target WTRU location. At 308, the GMLC obtains the serving AMF address (e.g. from UDM, not shown in the figure) and invokes the Namf_Location_ProvidePositioninglnfo service operation towards the AMF to request the current location of the WTRU.

[0090] At 312, the AMF may determine that AI / ML-based positioning may apply to this request based on multiple factors. The AMF may determine the desired AI / ML models, e.g., based on required positioning performance (e.g., accuracy, latency, etc.), applicable areas, etc. The AMF then locates the one or more NWDAF / MLTF that may support the model provisioning for AI / ML-based positioning. The AMF may further inquire about the available model information in these NWDAFs (not shown in FIG. 3).

[0091] At 316, the AMF may select the LMF that supports AI / ML-based positioning. And the model IDs that the LMF supports may be known to the AMF as local configuration or through NRF query.

[0092] At 320, the AMF may invoke the Nlmf_Location_DetermineLocation service operation towards the LMF to request the current location of the WTRU. In the request, the AMF may indicate that AI / ML-based positioning is expected. The AMF may include the NWDAF address that may provide desired AI / ML models and / or model IDs to be retrieved.

[0093] At 324, the LMF may send a Nnwdaf_MLModellnfo_Request to the received NWDAF address. It may include its supported Model IDs, WTRII target area, WTRU identifier, etc. as model filters. The LMF retrieves the desired AI / ML models from the NWDAF / MTLF. At 328, the LMF may store the models in its local repository. At 332, the LMF may collect positioning measurements required as the AI / ML model input by interacting with the WTRU and the RAN node.

[0094] At 336, the LMF may perform the model inference to obtain AI / ML-based positioning result. If that AI / ML-based positioning is not executable, e.g. the required data input is not available, the LMF may revert to traditional positioning method.

[0095] At 340, the LMF may returns the Nlmf_Location_DetermineLocation Response towards the AMF to return the current location of the WTRU. The LMF may indicate in the response whether the result is obtained through AI / ML-based positioning or traditional positioning. The LMF may append more details of the AI / ML-based positioning method such as the Model ID used, etc. At 344, the AMF may return the Namf_Location_ProvidePositioninglnfo Response towards the GMLC / LRF to return the current location of the WTRU. At 348, the GMLC may send the location service response to the external location services client.

Claims

CLAIMSWhat is claimed is:1 . A method performed by an access mobility and management device (AMF), the method comprising: receiving a location request for a current location of a wireless transmit / receive unit (WTRU); selecting one or more network data analytics functions (NWDAF), one or more artificial intelligence or machine learning models (AI / ML) models that perform AI / ML based positioning, and a location management function (LMF) that supports AI / ML based positioning and the selected one or more AI / ML models; sending, to the selected LMF, the location request, and information associated with each of the selected one or more AI / ML models; and receiving, from the selected LMF, a response indicating the current location of the WTRU.

2. The method of claim 1 , wherein the location request is sent by a location services client, by a gateway mobile location center (GMLC), or by a location services client via a GMLC.

3. The method of claim 1 , further comprising: sending, to the selected LMF, an indication that the AMF has determined that AI / ML based positioning is expected and one or more addresses associated with each of the selected NWDAFs.

4. The method of claim 1 , wherein the information associated with each of the selected one or more AI / ML models comprises one or more identifiers of the selected AI / ML model.

5. The method of claim 1 , wherein determining whether to apply an AI / ML based positioning is based on one or more of availability of the AI / ML model for the WTRU,availability of the AI / ML model for the area, availability of the LMF supporting the AI / ML- based positioning, or whether the WTRU supports a positioning measurement required by the AI / ML model.

6. The method of claim 1 , wherein the one or more AI / ML models are stored within the one or more NWDAFs.

7. The method of claim 6, wherein each of the one or more NWDAFs further comprises a model training logical function (MTLF), and wherein the MTLF trains the one or more AI / ML models stored on the one or more NWDAFs.

8. The method of claim 1 , wherein a network repository function (NRF) provides the AMF with one or more identifiers of the one or more AI / ML models that the LMF supports.

9. The method of claim 1 , wherein the response comprises one or more identifiers of the AI / ML model used to perform AI / ML based positioning.

10. The method of claim 1 , further comprising: sending the response to a gateway mobile location center (GMLC), location services client, or a locations services client via a GMLC.

11. An access mobility and management device (AMF), comprising a processor and a memory, the processor and the memory configured to: receive a location request for a current location of a wireless transmit / receive unit (WTRU); select one or more network data analytics functions (NWDAF), one or more artificial intelligence or machine learning models (AI / ML) models that perform AI / ML based positioning, and a location management function (LMF) that supports AI / ML based positioning and the selected one or more AI / ML models;send, to the selected LMF, the location request, and information associated with each of the selected one or more AI / ML models; and receive, from the selected LMF, a response indicating the current location of the WTRU.

12. The AMF of claim 11 , wherein the location request is sent by a location services client, by a gateway mobile location center (GMLC), or by a location services client via a GMLC.

13. The AMF of claim 1 , wherein the processor is further configured to: send, to the selected LMF, an indication that the AMF has determined that AI / ML based positioning is expected and one or more addresses associated with each of the selected NWDAFs.

14. The AMF of claim 11 , wherein the information associated with each of the selected one or more AI / ML models comprises one or more identifiers of the selected AI / ML model.

15. The AMF of claim 11 , wherein determining whether to apply an AI / ML based positioning is based on one or more of availability of the AI / ML model for the WTRU, availability of the AI / ML model for the area, availability of the LMF supporting the AI / ML- based positioning, or whether the WTRU supports a positioning measurement required by the AI / ML model.

16. The AMF of claim 11 , wherein the one or more AI / ML models are stored within the one or more NWDAFs.

17. The AMF of claim 16, wherein each of the one or more NWDAFs further comprises a model training logical function (MTLF), and wherein the MTLF trains the one or more AI / ML models stored on the one or more NWDAFs.

18. The AMF of claim 11 , wherein a network repository function (NRF) provides the AMF with one or more identifiers of the one or more AI / ML models that the LMF supports.

19. The AMF of claim 11 , wherein the response comprises one or more identifiers of the AI / ML model used to perform AI / ML based positioning.

20. The AMF of claim 11 , wherein the processor is further configured to: send the response to a gateway mobile location center (GMLC), location services client, or a locations services client via a GMLC.

Images