[go: up one dir, main page]

WO2025189755A1 - Détermination d'un ensemble de fonctionnalités applicables unifiées - Google Patents

Détermination d'un ensemble de fonctionnalités applicables unifiées

Info

Publication number
WO2025189755A1
WO2025189755A1 PCT/CN2024/125795 CN2024125795W WO2025189755A1 WO 2025189755 A1 WO2025189755 A1 WO 2025189755A1 CN 2024125795 W CN2024125795 W CN 2024125795W WO 2025189755 A1 WO2025189755 A1 WO 2025189755A1
Authority
WO
WIPO (PCT)
Prior art keywords
applicable
functionalities
supported
conditions
functionality
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/125795
Other languages
English (en)
Inventor
Robin Rajan THOMAS
Congchi ZHANG
Joachim Löhr
Vahid POURAHMADI
Tapisha SONI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/125795 priority Critical patent/WO2025189755A1/fr
Publication of WO2025189755A1 publication Critical patent/WO2025189755A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present disclosure relates to wireless communications, and more specifically to techniques for determining a set of unified applicable functionalities based on supported functionalities and user equipment (UE) and/or network conditions.
  • UE user equipment
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like) .
  • the wireless communications system may support wireless communications across various radio access technologies (RATs) including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • RATs radio access technologies
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.
  • Some implementations of the method and apparatuses described herein may include means for transmitting, to a UE, a request message for parameters and UE conditions for artificial intelligence and machine learning (AI/ML) positioning.
  • the method and apparatuses described herein may include means for receiving a response message comprising a list of one or more supported or applicable functionalities and UE conditions.
  • the method and apparatuses described herein may include means for determining a set of unified applicable functionalities based at least in part on the list of one or more supported or applicable functionalities and UE conditions.
  • the method and apparatuses described herein may include means for receiving, from a network entity, a request message for parameters and UE conditions for AI/ML positioning.
  • the method and apparatuses described herein may include means for determining a list of one or more supported or applicable functionalities and UE conditions.
  • the method and apparatuses described herein may include means for transmitting a response message comprising the list of one or more supported or applicable functionalities and UE conditions.
  • the method and apparatuses described herein may include means for receiving a message to activate or deactivate a functionality of a set of unified applicable functionalities based at least in part on the response message.
  • Figure 1 illustrates an example of a wireless communication system in accordance with aspects of the present disclosure.
  • Figure 2 illustrates an example of a protocol stack, in accordance with aspects of the present disclosure.
  • FIG. 3 illustrates an example of a downlink (DL) based positioning, in accordance with aspects of the present disclosure.
  • Figure 4 illustrates an example of a functional framework for AI/ML for an air interface, in accordance with aspects of the present disclosure.
  • Figure 5 illustrates an example of a functional framework for AI/ML for an air interface, in accordance with aspects of the present disclosure.
  • FIG. 6 illustrates an example of a transfer procedure for long term evolution (LTE) positioning protocol (LPP) capability exchange, in accordance with aspects of the present disclosure.
  • LTE long term evolution
  • LPP positioning protocol
  • Figure 7 illustrates an example of an indication procedure for LPP capability exchange, in accordance with aspects of the present disclosure.
  • Figure 8 illustrates an example of a mapping structure of an associated identifier (ID) to information relating to UE and network conditions and applicable functionalities, in accordance with aspects of the present disclosure.
  • ID associated identifier
  • Figure 9 illustrates an example of a nesting structure of associated IDs and corresponding sub-items, in accordance with aspects of the present disclosure.
  • Figure 10 illustrates an example of a network-solicited functionality exchange procedure with a UE, in accordance with aspects of the present disclosure.
  • Figure 11 illustrates an example of a network-solicited functionality exchange procedure with a RAN node, in accordance with aspects of the present disclosure.
  • Figure 12 illustrates an example of a network-based functionality exchange procedure with a UE, in accordance with aspects of the present disclosure.
  • Figure 13 illustrates an example of a UE-initiated functionality exchange procedure, in accordance with aspects of the present disclosure.
  • Figure 14A illustrates an example of a functionality exchange and storage procedure, in accordance with aspects of the present disclosure.
  • Figure 14B is a continuation of the procedure of Figure 14A.
  • Figure 15 illustrates an example of a UE, in accordance with aspects of the present disclosure.
  • Figure 16 illustrates an example of a processor, in accordance with aspects of the present disclosure.
  • FIG 17 illustrates an example of a network equipment (NE) , in accordance with aspects of the present disclosure.
  • NE network equipment
  • Figure 18 illustrates a flowchart of a method performed by a NE, in accordance with aspects of the present disclosure.
  • Figure 19 illustrates a flowchart of a method performed by a UE, in accordance with aspects of the present disclosure.
  • Wireless communication systems beyond 5G may implement AI/ML positioning to improve the location estimate accuracy of a device (e.g., UE) in challenging radio conditions, such as environments with heavy non-line-of-sight (NLOS) conditions.
  • AI/ML positioning is direct AI/ML positioning, where the output of the AI/ML model is a user’s location (e.g., UE’s position) .
  • assisted AI/ML positioning where the output is an enhanced positioning measurement with associated information such as an enhanced line-of-sight (LOS) or NLOS (LOS/NLOS) classification of the measurement as an output of the AI/ML model.
  • AI/ML functionality-based LCM framework may be implemented to enable the activation or deactivation (and/or the fallback or switching) of various AI/ML functionality via Third Generation Partnership Project (3GPP) procedures including specified 3GPP signaling and messages.
  • 3GPP Third Generation Partnership Project
  • an AI/ML model may be trained on one or more functionalities, which depends on the combination of information provided by the UE and/or network, e.g., base station.
  • multiple AI/ML models may be trained on the same functionality.
  • a UE-side model refers to an AI/ML model that is deployed directly to the UE. Due to hardware/computing and power constraints at the UE, a UE-side model may be lightweight and/or optimized for a resource-constrained device. For example, there is no existing procedural framework which supports the trigger, request and reporting of supported and/or applicable functionality as well as the mapping or structural framework of a functionality in terms of certain UE or network conditions.
  • the present disclosure aims to address the aforementioned issues in order to enhance AI/ML model functionality-based LCM procedures.
  • Various embodiments are detailed to cover different functionality-based LCM scenarios.
  • aspects of the present disclosure describe the mapping details and inter-dependency of the information related to associated IDs, UE supported/applicable functionality, UE and network conditions. Additional aspects of the present disclosure describe static and dynamic UE and network conditions and their signaling.
  • a first solution describes a framework for defining the relationship among UE applicable functionalities, UE conditions, network conditions, and associated identifiers (IDs) , as well as information structures for exchanging the same.
  • a second solution describes techniques and procedures to enable the network (e.g., a location management function (LMF) or location services (LCS) server) to solicit functionality-based LCM parameters from a UE (such as a list of one or more supported or applicable functionalities and UE conditions) and coordinate with one or more next-generation NodeBs (gNBs) to develop a set of unified AI/ML functionalities, which can be later activated.
  • a location management function LMF
  • LCS location services
  • a third solution describes techniques and procedures to enable the provisioning of a list/index of unified functionalities from the network (e.g., an LMF) to UE and thereafter the UE can select the recommended unified applicable functionality to be activated.
  • the network e.g., an LMF
  • a fourth solution describes techniques and procedures to enable the UE to initiate/trigger the provisioning of a set of UE-supported functionalities (or a set of applicable functionalities) .
  • a fifth solution describes techniques and procedures to enable an access and mobility management function (AMF) to support storage of UE conditions and/or UE applicable functionalities to be retrieved at a later time instance.
  • AMF access and mobility management function
  • FIG. 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106.
  • the wireless communications system 100 may support various radio access technologies (RATs) .
  • RATs radio access technologies
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a new radio (NR) network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network.
  • NR new radio
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a wireless communication network entity, a radio access network (RAN) , a NodeB, an eNodeB (eNB) , a gNB, or other suitable terminology.
  • An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection.
  • an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area.
  • an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN) .
  • NTN non-terrestrial network
  • different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.
  • the one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • An NE 102 may support communications with the CN 106, or with another NE 102, or both.
  • an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N2, or network interface) .
  • the NE 102 may communicate with each other directly.
  • the NE 102 may communicate with each other or indirectly (e.g., via the CN 106.
  • one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • the CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the CN 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
  • NAS non-access stratum
  • the CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network may include an application server.
  • one or more UEs 104 may communicate with the application server.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102.
  • the CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106) .
  • the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the NEs 102 and the UEs 104 may support different resource structures.
  • the NEs 102 and the UEs 104 may support different frame structures.
  • the NEs 102 and the UEs 104 may support a single frame structure.
  • the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations frequency range #1 (FR1) (410 MHz –7.125 GHz) , frequency range #2 (FR2) (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , frequency range #4 (FR4) (52.6 GHz –114.25 GHz) , frequency range #4a (FR4a) or frequency range #4-1 (FR4-1) (52.6 GHz –71 GHz) , and frequency range #5 (FR5) (114.25 GHz –300 GHz) .
  • FR1 frequency range #1
  • FR2 frequency range #2
  • FR3 7.125 GHz –24.25 GHz
  • FR4 frequency range #4
  • FR4a frequency range #4a
  • FR4-1 FR4-1
  • FR5 114.25 GHz
  • the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • Figure 2 illustrates an example of a protocol stack 200, in accordance with aspects of the present disclosure. While Figure 2 shows a UE 206, a RAN node 208, and a 5GC 210 (e.g., comprising at least an AMF) , these are representative of a set of UEs 104 interacting with an NE 102 (e.g., base station) and a CN 106. As depicted, the protocol stack 200 comprises a user plane protocol stack 202 and a control plane protocol stack 204.
  • the user plane protocol stack 202 includes a PHY layer 212, a MAC sublayer 214, a radio link control (RLC) sublayer 216, a packet data convergence protocol (PDCP) sublayer 218, and a service data adaptation protocol (SDAP) layer 220.
  • the control plane protocol stack 204 includes a PHY layer 212, a MAC sublayer 214, a RLC sublayer 216, and a PDCP sublayer 218.
  • the control plane protocol stack 204 also includes a radio resource control (RRC) layer 222 and a non-access stratum (NAS) layer 224.
  • RRC radio resource control
  • NAS non-access stratum
  • the AS layer 226 (also referred to as “AS protocol stack” ) for the user plane protocol stack 202 may include at least SDAP, PDCP, RLC and MAC sublayers, and the physical layer.
  • the AS layer 228 for the control plane protocol stack 204 may include at least RRC, PDCP, RLC and MAC sublayers, and the physical layer.
  • the layer-1 (L1) includes the PHY layer 212.
  • the layer-2 (L2) is split into the SDAP sublayer 220, PDCP sublayer 218, RLC sublayer 216, and MAC sublayer 214.
  • the layer-3 includes the RRC layer 222 and the NAS layer 224 for the control plane and includes, e.g., an internet protocol (IP) layer and/or PDU Layer (not depicted) for the user plane.
  • IP internet protocol
  • L1 and L2 are referred to as “lower layers, ” while L3 and above (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers. ”
  • the PHY layer 212 offers transport channels to the MAC sublayer 214.
  • the PHY layer 212 may perform a beam failure detection procedure using energy detection thresholds, as described herein.
  • the PHY layer 212 may send an indication of beam failure to a MAC entity at the MAC sublayer 214.
  • the MAC sublayer 214 offers logical channels (LCHs) to the RLC sublayer 216.
  • the RLC sublayer 216 offers RLC channels to the PDCP sublayer 218.
  • the PDCP sublayer 218 offers radio bearers to the SDAP sublayer 220 and/or RRC layer 222.
  • the SDAP sublayer 220 offers QoS flows to the core network (e.g., 5GC) .
  • the RRC layer 222 provides for the addition, modification, and release of carrier aggregation (CA) and/or dual connectivity.
  • CA carrier aggregation
  • the RRC layer 222 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs) .
  • the NAS layer 224 is between the UE 206 and an AMF in the 5GC 210. NAS messages are passed transparently through the RAN.
  • the NAS layer 224 is used to manage the establishment of communication sessions and for maintaining continuous communications with the UE 206 as it moves between different cells of the RAN.
  • the AS layers 226 and 228 are between the UE 206 and the RAN (i.e., RAN node 208) and carry information over the wireless portion of the network. While not depicted in Figure 2, the IP layer exists above the NAS layer 224, a transport layer exists above the IP layer, and an application layer exists above the transport layer.
  • the MAC sublayer 214 is the lowest sublayer in the L2 architecture of the NR protocol stack. Its connection to the PHY layer 212 below is through transport channels, and the connection to the RLC sublayer 216 above is through LCHs.
  • the MAC sublayer 214 therefore performs multiplexing and demultiplexing between LCHs and transport channels: the MAC sublayer 214 in the transmitting side constructs MAC PDUs (also known as transport blocks (TBs) ) from MAC service data units (SDUs) received through LCHs, and the MAC sublayer 214 in the receiving side recovers MAC SDUs from MAC PDUs received through transport channels.
  • MAC PDUs also known as transport blocks (TBs)
  • SDUs MAC service data units
  • the MAC sublayer 214 provides a data transfer service for the RLC sublayer 216 through LCHs, which are either control LCHs which carry control data (e.g., RRC signaling) or traffic LCHs which carry user plane data.
  • LCHs which are either control LCHs which carry control data (e.g., RRC signaling) or traffic LCHs which carry user plane data.
  • the data from the MAC sublayer 214 is exchanged with the PHY layer 212 through transport channels, which are classified as uplink (UL) or DL. Data is multiplexed into transport channels depending on how it is transmitted over the air.
  • the PHY layer 212 is responsible for the actual transmission of data and control information via the air interface, i.e., the PHY layer 212 carries all information from the MAC transport channels over the air interface on the transmission side. Some of the important functions performed by the PHY layer 212 include coding and modulation, link adaptation (e.g., adaptive modulation and coding (AMC) ) , power control, cell search and random access (for initial synchronization and handover purposes) and other measurements (inside the 3GPP system (i.e., NR and/or LTE system) and between systems) for the RRC layer 222.
  • the PHY layer 212 performs transmissions based on transmission parameters, such as the modulation scheme, the coding rate (i.e., the modulation and coding scheme (MCS) ) , the number of physical resource blocks (PRBs) , etc.
  • MCS modulation and coding scheme
  • the protocol stack 200 may be an NR protocol stack used in a 5G NR system.
  • an LTE protocol stack comprises similar structure to the protocol stack 200, with the differences that the LTE protocol stack lacks the SDAP sublayer 220 in the AS layer 226, that an EPC replaces the 5GC 210, and that the NAS layer 224 is between the UE 206 and an MME in the EPC.
  • the present disclosure distinguishes between a protocol layer (such as the aforementioned PHY layer 212, MAC sublayer 214, RLC sublayer 216, PDCP sublayer 218, SDAP sublayer 220, RRC layer 222 and NAS layer 224) and a transmission layer in multiple-input multiple-output (MIMO) communication (also referred to as a “MIMO layer” or a “data stream” ) .
  • a protocol layer such as the aforementioned PHY layer 212, MAC sublayer 214, RLC sublayer 216, PDCP sublayer 218, SDAP sublayer 220, RRC layer 222 and NAS layer 22
  • MIMO multiple-input multiple-output
  • the transmission of at least one PRS enables the UE 206 to perform UE positioning-related measurements to enable the computation of a UE’s location estimate and are configured per TRP, where a TRP may transmit one or more beams.
  • DL-TDOA downlink time difference of arrival
  • DL-AoD downlink angle-of-departure
  • Multi-RTT multiple-cell round trip time
  • E-CID enhanced cell identity
  • UL-TDOA uplink time difference of arrival
  • U-AoA uplink angle-of-arrival
  • the DL-TDOA positioning method makes use of the DL reference signal time difference (RSTD) (and optionally DL PRS reference signal received power (RSRP) ) of DL signals received from multiple transmission points (TPs) , at the UE 206.
  • RSTD DL reference signal time difference
  • RSRP DL PRS reference signal received power
  • the UE 206 measures the DL RSTD (and optionally DL PRS RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE 206 in relation to the neighboring TPs.
  • the DL-AoD positioning method makes use of the measured DL PRS RSRP of downlink signals received from multiple TPs, at the UE 206.
  • the UE 206 measures the DL PRS RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE 206 in relation to the neighboring TPs.
  • the Multi-RTT positioning method makes use of the UE reception-to-transmission (Rx-Tx) measurements and DL PRS RSRP of downlink signals received from multiple TRPs, measured by the UE 206 and the measured gNB Rx-Tx measurements and UL sounding reference signal RSRP (SRS-RSRP) at multiple TRPs of uplink signals transmitted from UE 206.
  • Rx-Tx reception-to-transmission
  • SRS-RSRP UL sounding reference signal RSRP
  • the UE 206 measures the UE Rx-Tx measurements (and optionally DL PRS RSRP of the received signals) using assistance data received from the positioning server, and the TRPs measure the gNB Rx-Tx measurements (and optionally UL SRS-RSRP of the received signals) using assistance data received from the positioning server.
  • the measurements are used to determine the round trip time (RTT) at the positioning server which are used to estimate the location of the UE 206.
  • the position of a UE 206 is estimated with the knowledge of its serving ng-eNB, gNB and cell and is based on Uu (e.g., LTE) signals.
  • the information about the serving ng-eNB, gNB and cell may be obtained by paging, registration, or other methods.
  • the NR E-CID positioning method refers to techniques which use additional UE measurements and/or NR radio resource and other measurements to improve the UE location estimate using NR signals.
  • the UE 206 may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE 206 generally is not expected to make additional measurements for the sole purpose of positioning; i.e., the positioning procedures do not supply a measurement configuration or measurement control message, and the UE 206 reports the measurements that it has available rather than being required to take additional measurement actions.
  • the UL-TDOA positioning method makes use of the time difference of arrival (and optionally UL SRS-RSRP) at multiple Reception Points (RPs) of uplink signals transmitted from UE 206.
  • the RPs measure the UL TDOA (and optionally UL SRS-RSRP) of the received UL signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE 206.
  • the UL-AoA positioning method makes use of the measured azimuth and the zenith of arrival at multiple RPs of uplink signals transmitted from UE 206.
  • the reception points measure azimuth angle-of-arrival (A-AoA) and/or zenith angle-of-arrival (Z-AoA) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE 206.
  • RAT-dependent positioning techniques involve the 3GPP RAT and core network entities to perform the position estimation of the UE 206, which are differentiated from RAT-independent positioning techniques which rely on global navigation satellite system (GNSS) , inertial measurement unit (IMU) sensor, wireless local area network (WLAN) and BLUETOOTH technologies for performing target device (i.e., UE 206) positioning.
  • GNSS global navigation satellite system
  • IMU inertial measurement unit
  • WLAN wireless local area network
  • BLUETOOTH BLUETOOTH
  • RAT-Independent positioning techniques are supported in Rel-16: network-assisted GNSS, barometric pressure sensor positioning, WLAN positioning, BLUETOOTH positioning, TBS positioning, motion sensor positioning.
  • GNSS network-assisted GNSS methods make use of UEs 206 that are equipped with radio receivers capable of receiving GNSS signals.
  • GNSS encompasses both global and regional/augmentation navigation satellite systems.
  • GLONASS Global Positioning System
  • BDS BeiDou Navigation Satellite System
  • Regional navigation satellite systems include Quasi Zenith Satellite System (QZSS) while the many augmentation systems, are classified under the generic term of Space Based Augmentation Systems (SBAS) and provide regional augmentation services.
  • QZSS Quasi Zenith Satellite System
  • SBAS Space Based Augmentation Systems
  • different GNSSs e.g., GPS, Galileo, etc.
  • the barometric pressure sensor method makes use of barometric sensors to determine the vertical component of the position of the UE 206.
  • the UE 206 measures barometric pressure, optionally aided by assistance data, to calculate the vertical component of its location or to send measurements to the positioning server for position calculation. This method should be combined with other positioning methods to determine the 3D position of the UE 206.
  • the WLAN positioning method makes use of the WLAN measurements (e.g., WLAN AP identifiers and, optionally, signal strength or other measurements) and databases to determine the location of the UE 206.
  • the UE 206 measures received signals from WLAN APs, optionally aided by assistance data, to send measurements to the positioning server for position calculation. Using the measurement results and a references database, the location of the UE 206 is calculated.
  • the UE 206 makes use of WLAN measurements and optionally WLAN AP assistance data provided by the positioning server, to determine its location.
  • the Bluetooth positioning method makes use of Bluetooth measurements (beacon identifiers and optionally other measurements) to determine the location of the UE 206.
  • the UE 206 measures received signals from Bluetooth beacons. Using the measurement results and a references database, the location of the UE 206 is calculated.
  • the Bluetooth methods may be combined with other positioning methods (e.g., WLAN) to improve positioning accuracy of the UE 206.
  • a TBS includes a network of ground-based transmitters, broadcasting signals only for positioning purposes.
  • the current type of TBS positioning signals are the Metropolitan Beacon System (MBS) signals and PRS.
  • MBS Metropolitan Beacon System
  • the UE 206 measures received TBS signals, optionally aided by assistance data, to calculate its location or to send measurements to the positioning server for position calculation.
  • this method makes use of different sensors such as accelerometers, gyros, magnetometers, to calculate the displacement of the UE 206.
  • the UE 206 estimates a relative displacement based upon a reference position and/or reference time.
  • the UE 206 sends a report comprising the determined relative displacement which can be used to determine the absolute position. This method should be used with other positioning methods for hybrid positioning.
  • Figure 3 illustrates a network architecture 300 for DL-based positioning measurements and reference signals (RS) , in accordance with aspects of the present disclosure.
  • the DL PRS can be transmitted by different base stations (e.g., serving gNB and neighboring gNB (s) ) using narrow beams over FR1 (i.e., frequencies from 410 MHz to 7125 MHz) and FR2 (i.e., frequencies from 24.25 GHz to 52.6 GHz) , which is relatively different when compared to LTE where the PRS was transmitted across the whole cell.
  • FR1 i.e., frequencies from 410 MHz to 7125 MHz
  • FR2 i.e., frequencies from 24.25 GHz to 52.6 GHz
  • a UE 206 may receive DL PRS from a neighboring first gNB/TRP (denoted “gNB1–TRP1” ) 304, from a neighboring second gNB (denoted “gNB2–TRP1” ) 306, and also from a third gNB/TRP (denoted “gNB3–TRP1” ) 308 which is a reference or serving gNB.
  • a neighboring first gNB/TRP denoted “gNB1–TRP1”
  • gNB2–TRP1 neighboring second gNB
  • gNB3–TRP1 third gNB/TRP
  • each gNB/TRP 304, 306, 308 is configured with a first resource set ID (depicted as “Resource Set ID#0” ) 310 and a second resource set ID (depicted as “Resource Set ID#1” ) 312.
  • the UE 206 receives DL PRS on transmission beams; here, receiving DL PRS from the gNB1–TRP1 304 on DL PRS resource ID #3 from the second resource set ID 312, receiving DL PRS from the gNB2–TRP1 306 on DL PRS resource ID #3 from the first resource set ID 310, and receiving DL PRS from the gNB3–TRP1 308 on DL PRS resource ID #1 from the second resource set ID 312.
  • UE positioning measurements such as RSTD and PRS RSRP measurements are made between different beams (e.g., between a different pair of DL PRS resources or DL PRS resource sets) –as opposed to different cells as was the case in LTE.
  • a location server 302 e.g., an LMF
  • Table 2 and Table 3 show the RS-to-measurements mapping required for each of the supported RAT-dependent positioning techniques at the UE and gNB, respectively.
  • Table 2 UE measurements to enable RAT-dependent positioning techniques
  • Table 3 gNB measurements to enable RAT-dependent positioning techniques
  • the different DL measurements including DL PRS RSRP, DL RSTD and UE Rx-Tx time difference required for the supported RAT-dependent positioning techniques are shown in Table 4.
  • the following measurement configurations may be specified: A) 4 Pair of DL RSTD measurements can be performed per pair of cells (each measurement is performed between a different pair of DL PRS resources/resource sets with a single reference timing) ; B) 8 DL PRS RSRP measurements can be performed on different DL PRS resources from the same cell.
  • the UL AoA is defined as the estimated azimuth angle (A-AoA) and vertical (zenith) angle (Z-AoA) of a UE with respect to a reference direction, wherein the reference direction is defined.
  • the UL-AoA is determined at the gNB antenna for an UL channel corresponding to this UE.
  • estimated azimuth angle is measured relative to geographical North and is positive in a counter-clockwise direction and estimated vertical angle is measured relative to zenith and positive to horizontal direction.
  • estimated azimuth angle is measured relative to x-axis of the local coordinate system and positive in a counter-clockwise direction and estimated vertical angle is measured relative to z-axis of the local coordinate system and positive to x-y plane direction.
  • the bearing, downtilt and slant angles of the local coordinate system are defined (e.g., according to 3GPP TS 38.901) .
  • the UL relative time of arrival is the beginning of subframe i containing at least one sounding reference signal (SRS) received in a RP j, relative to the relative time of arrival (RTOA) reference time.
  • Multiple SRS resources can be used to determine the beginning of one subframe containing SRS received at an RP.
  • the reference point for T UL-RTOA may be: the Rx antenna connector for a type 1-C base station (e.g., as described in 3GPP TS 38.104) ; the Rx antenna (i.e., the center location of the radiating region of the Rx antenna) for a type 1-O or 2-O base station (e.g., as described in 3GPP TS 38.104) , or the Rx transceiver array boundary connector for a type 1-H base station (e.g., as described in 3GPP TS 38.104) .
  • the gNB Rx-Tx time difference is defined as T gNB-RX –T gNB-TX , where T gNB-RX is the TRP received timing of uplink subframe #i containing SRS associated with UE, defined by the first detected path in time, and where T gNB-TX is the TRP transmit timing of downlink subframe #j that is closest in time to the subframe #i received from the UE.
  • Multiple SRS resources can be used to determine the start of one subframe containing SRS.
  • the reference point for the T gNB-RX may be: the Rx antenna connector for a type 1-C base station (e.g., as described in 3GPP TS 38.104) ; the Rx antenna (i.e., the center location of the radiating region of the Rx antenna) for a type 1-O or 2-O base station (e.g., as described in 3GPP TS 38.104) , or the Rx transceiver array boundary connector for a type 1-H base station (e.g., as described in 3GPP TS 38.104) .
  • the reference point for the T gNB-TX may be: the Tx antenna connector for a type 1-C base station (e.g., as described in 3GPP TS 38.104) ; the Tx antenna (i.e., the center location of the radiating region of the Tx antenna) for a type 1-O or 2-O base station (e.g., as described in 3GPP TS 38.104) , or the Tx transceiver array boundary connector for a type 1-H base station (e.g., as described in 3GPP TS 38.104) .
  • the UL SRS-RSRPP is defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry the received UL SRS signal configured for the measurement, where UL SRS-RSRPP for 1st path delay is the power contribution corresponding to the first detected path in time.
  • the reference point for UL SRS-RSRPP shall be: the Rx antenna connector for a type 1-C base station (e.g., as described in 3GPP TS 38.104) ; based on the combined signal from antenna elements corresponding to a given receiver branch for a type 1-O or 2-O base station (e.g., as described in 3GPP TS 38.104) , or the Rx transceiver array boundary connector for a type 1-H base station (e.g., as described in 3GPP TS 38.104) .
  • FR1 and FR2 if receiver diversity is in use by the gNB for UL SRS-RSRPP measurements, then: 1) The reported UL SRS-RSRPP value for the first and additional paths shall be provided for the same receiver branch (es) as applied for UL SRS-RSRP measurements, or 2) The reported UL SRS-RSRPP value for the first path shall not be lower than the corresponding UL SRS-RSRPP for the first path of any of the individual receiver branches and the reported UL SRS-RSRPP for the additional paths shall be provided for the same receiver branch (es) as applied UL SRS-RSRPP for the first path.
  • Figure 4 illustrates an example of a functional framework 400 (i.e., a functional block diagram) for AI/ML for an air interface, in accordance with aspects of the present disclosure.
  • the general framework includes multiple processes that enable AI/ML functionality over the air interface.
  • the data collection function 402 is a function that provides input data to the model training function 404, the management function 406, and the Inference function 408.
  • the training data refers to data needed as input for the AI/ML model training function 404.
  • the monitoring data refers to data needed as input for the management of AI/ML models or AI/ML functionalities.
  • the inference data refers to data needed as input for the AI/ML inference function 408.
  • the model training function 404 is a function that performs AI/ML model training, validation, and testing which may generate model performance metrics which can be used as part of the model testing procedure.
  • the model training function 404 is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on training data delivered by a data collection function 402, if required.
  • model training function 404 is used to deliver trained, validated, and tested AI/ML models to the model storage function 410, or to deliver an updated version of a model to the model storage function 410.
  • the management function 406 is a function that oversees the operation (e.g., selection/ (de) activation/switching/fallback) and monitoring (e.g., performance) of AI/ML models or AI/ML functionalities.
  • the management function 406 is also responsible for making decisions to ensure the proper inference operation based on data received from the data collection function 402 and the inference function 408.
  • the management instruction is an output of the management function 406.
  • the management instruction refers to information needed as input to manage the inference function 408.
  • the information in the management instruction may include selection, or activation/deactivation, or switching of AI/ML models or AI/ML-based functionalities, fallback to non-AI/ML operation (i.e., not relying on inference process) , etc.
  • the model transfer/delivery request is another output of the management function 406 used to request model (s) to the model storage function 410.
  • the performance feedback /retraining request is another output of the management function 406 and refers to information needed as input for the model training function 404, e.g., for model (re) training or updating purposes.
  • the inference function 408 is a function that provides outputs from the process of applying AI/ML models or AI/ML functionalities, using the data that is provided by the data collection function 402 (i.e., inference data) as an input.
  • the inference function 408 is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on inference data delivered by a data collection function 402, if required.
  • the inference output is an output of the Inference function 408 and refers to data used by the management function 406 to monitor the performance of AI/ML models or AI/ML functionalities.
  • the inference function 408 applies AI/ML models or AI/ML functionalities (e.g., using the inference data) to produce the inference output.
  • the model storage function 410 is a function responsible for storing trained/updated models that can be used to perform the inference function 408. Note that the model storage function 410 may be a reference point when applicable for protocol terminations, model transfer/delivery, and related processes. It should be stressed that its purpose does not encompass restricting the actual storage locations of models. Therefore, the impact of all data/information/instruction flows may be evaluated on a case by case basis.
  • the model transfer/delivery is an output of the model storage function 410 and is used to deliver an AI/ML model to the Inference function 408.
  • the AI/ML model outputs the UE location.
  • One example of direct AI/ML positioning includes fingerprinting based on channel observation as the input of AI/ML model.
  • the AI/ML model outputs new measurement and/or enhancement of existing measurement.
  • the AI/ML model may output LOS/NLOS identification, timing and/or angle of measurement, or likelihood of measurement information.
  • case 1 characterized by UE-based positioning with UE-side model, direct AI/ML or AI/ML assisted positioning
  • case 2a characterized by UE-assisted/LMF-based positioning with UE-side model, AI/ML assisted positioning
  • case 2b characterized by UE-assisted/LMF-based positioning with LMF-side model, direct AI/ML positioning
  • case 3a characterized by a next generation radio access network (NG-RAN) node assisted positioning with gNB-side model, AI/ML assisted positioning
  • case 3b characterized by NG-RAN node assisted positioning with LMF-side model, direct AI/ML positioning.
  • NG-RAN next generation radio access network
  • an LMF-side model refers to an AI/ML model that is deployed directly to the LMF.
  • a gNB-side model refers to an AI/ML model that is deployed directly to the gNB (or similar RAN node) .
  • the LMF-side models and gNB-side models may be more complex and/or computationally intensive since the LMF and gNB do not share the same computing and power constraints as the UE.
  • Figure 5 illustrates another example of a functional framework 500 (i.e., a functional block diagram) for AI/ML for RAN intelligence, in accordance with aspects of the present disclosure.
  • the general framework includes multiple processes that enable AI/ML functionality over the air interface.
  • the data collection function 502 is a function that provides input data to the model training function 504 and the model inference function 506.
  • AI/ML algorithm specific data preparation e.g., data pre-processing and cleaning, formatting, and transformation
  • Examples of input data may include measurements from UEs or different network entities, feedback from the actor 508, and output from an AI/ML model.
  • the training data is an output of the data collection function 502 and refers to the data needed as input for the AI/ML Model Training function 504.
  • the inference data is another output of the data collection function 502 and refers to the data needed as input for the AI/ML model inference function 506.
  • the model training function 504 is a function that performs the ML model training, validation, and testing which may generate model performance metrics as part of the model testing procedure.
  • the model training function 504 is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on training data delivered by a data collection function 502, if required.
  • the model deployment/update is an output of the model training function 504 which may be used to initially deploy a trained, validated, and tested AI/ML model to the model inference function 506, or to deliver an updated model to the model inference function 506.
  • the model inference function 506 is a function that provides AI/ML model inference output (e.g., predictions or decisions) .
  • the model inference function 506 provides model performance feedback to model training function 504.
  • the model inference function 506 is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on inference data delivered by a data collection function 502, if required.
  • the inference output of the AI/ML model produced by a model inference function 506 may be provided to the actor 508.
  • the model performance feedback is an optional output of the model inference function 506 which may be used for monitoring the performance of the AI/ML model, when available.
  • the actor 508 is a function that receives the output from the model inference function 506 and triggers or performs corresponding actions.
  • the actor 508 may trigger actions directed to other entities or to itself. Accordingly, the actor 508 may output feedback, i.e., information that may be needed to derive training data, inference data or to monitor the performance of the AI/ML model and its impact to the network through updating of key performance indicators (KPIs) and performance counters.
  • KPIs key performance indicators
  • the UE 206 may support the functions of a positioning reference unit (PRU) .
  • PRU positioning reference unit
  • a UE 206 that accesses the RAN node 208 and/or the 5GC 210 via an NR satellite shall not operate as a PRU.
  • the PRU supports service level association, association update and disassociation with a serving LMF.
  • the PRU may send service level association, association update or disassociation to LMF via LCS supplementary service message.
  • the PRU may support association with multiple LMFs, e.g., for the case a PRU is in multiple LMF overlapped serving areas.
  • the PRU information included in a PRU association or PRU association update contains one or more than one of the following aspects: A) PRU positioning capabilities; B) location information (if known) ; and C) the PRU ON/OFF state. Note that the PRU ON/OFF states may indicate temporarily availability of the PRU functionality of a UE at the serving LMF.
  • a target device e.g., a UE or PRU
  • a server e.g., a location services server
  • capabilities may refer to positioning and protocol capabilities related to LPP and the positioning methods supported by LPP.
  • Figure 6 illustrates an example of a transfer procedure 600 for LPP capability exchange, in accordance with aspects of the present disclosure.
  • the capability transfer procedure 600 may be performed between a location target 602 and a location server 604.
  • the location server 604 sends a RequestCapabilities message to the location target 602 (see messaging 606) .
  • the location server 604 may indicate the types of capability needed.
  • the location target 602 responds with a ProvideCapabilities message to the location server 604 (see messaging 608) .
  • the capabilities shall correspond to any capability types specified in Step 1.
  • This message shall include the endTransaction information element (IE) set to TRUE.
  • IE endTransaction information element
  • Figure 7 illustrates an example of an indication procedure 700 for LPP capability exchange, in accordance with aspects of the present disclosure.
  • the capability indication procedure 700 may be performed between a location target 702 and a location server 704.
  • the location target 702 sends a ProvideCapabilities message to the location server 704 (see messaging 706) .
  • This message shall include the endTransaction IE set to TRUE.
  • the indication procedure 700 ends.
  • a transmission point refers to a set of geographically co-located transmit antennas (e.g., antenna array (with one or more antenna elements) ) for one cell, part of one cell or one PRS-only TP.
  • Transmission Points can include base station (eNodeB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a PRS-only TP, etc.
  • eNodeB base station
  • One cell can be formed by one or multiple transmission points. For a homogeneous deployment, each transmission point may correspond to one cell.
  • a reception point refers to set of geographically co-located receive antennas (e.g., antenna array (with one or more antenna elements) ) for one cell, part of one cell or one UL-SRS-only RP.
  • Reception Points can include base station (ng-eNB or gNB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a UL-SRS-only RP, etc.
  • One cell can include one or multiple reception points. For a homogeneous deployment, each reception point may correspond to one cell.
  • a TRP refers to set of geographically co-located antennas (e.g., antenna array (with one or more antenna elements) ) supporting TP and/or RP functionality.
  • a “PRS-only TP” refers to a TP which only transmits PRS signals or DL-PRS for PRS-based TBS positioning and is not associated with a cell.
  • a positioning reference unit (PRU) at a known location can perform positioning measurements (e.g., RSTD, RSRP, UE Rx-Tx time difference measurements, etc. ) and report these measurements to a location server.
  • the PRU can transmit SRS to enable TRPs to measure and report UL positioning measurements (e.g., RTOA, UL-AoA, gNB Rx-Tx time difference, etc. ) from PRU at a known location.
  • the PRU measurements can be compared by a location server with the measurements expected at the known PRU location to determine correction terms for other nearby target devices.
  • the DL and/or UL location measurements for other target devices can then be corrected based on the previously determined correction terms.
  • a PRU may also comprise of a TRP with a known location.
  • the term “supported functionalities” refers to functionalities that UE can indicate by using UE capability information (via RRC/LPP signaling) .
  • the term “applicable functionalities” refers to functionalities that the UE is ready to apply at inference.
  • the term “activated functionalities” refers to functionalities already enabled for performing inference.
  • target-UE refers to a UE of interest whose position (e.g., absolute position or relative position) is to be obtained by the network or by the UE itself, e.g., using one or more of the positioning methods described herein.
  • position e.g., absolute position or relative position
  • ML machine learning
  • a first solution describes a framework for defining the relationship among UE applicable functionalities, UE conditions, network conditions, and associated identifiers (IDs) , as well as information structures for exchanging the same.
  • a second solution describes techniques and procedures to enable the network (e.g., LMF) to solicit (i.e., request) functionality-based LCM parameters from a UE (such as a list of one or more supported or applicable functionalities and UE conditions) and coordinate with the gNBs to develop a set of unified AI/ML functionalities, which can be later activated.
  • LMF network management
  • UE such as a list of one or more supported or applicable functionalities and UE conditions
  • a third solution describes techniques and procedures to enable the provisioning of a list/index of unified functionalities from the network (e.g., an LMF) to UE and thereafter the UE can select the recommended unified applicable functionality to be activated.
  • the network e.g., an LMF
  • a fourth solution describes techniques and procedures to enable the UE to initiate/trigger the provisioning of a set of UE-supported functionalities (or a set of applicable functionalities) .
  • a fifth solution describes techniques and procedures to enable an AMF to support storage of UE conditions and/or UE applicable functionalities to be retrieved at a later time instance.
  • any reference made to device e.g., UE position information (or location information) may refer to either an 2D/3D absolute position, 2D/3D relative position, distance, relative direction with respect to another node/entity, ranging in terms of distance, ranging in terms of direction or combination thereof.
  • a set of unified functionalities may be defined and associated with a set of associated IDs.
  • Each of the unified functionalities may be mapped to a combination of conditions and functionalities, i.e., supported and/or applicable functionalities.
  • the UE conditions or UE applicable functionalities refer to the ability of a target UE to support different types of position methods, different aspects of a particular position method (e.g., support of different types of assistance data) and common features that are applicable to multiple positioning methods (e.g., ability to handle LPP message segments) .
  • the UE conditions include both “static” or “non-variable” UE conditions, as well as “dynamic” or “variable” UE conditions.
  • the UE has to report the same positioning capabilities across multiple positioning sessions, which leads to the concept that some of the UE’s positioning capabilities can be dynamic and can be different depending on the type of LMF connected with the UE. This is primarily due to the LMF selection procedure being handled by the AMF, e.g., certain LMFs may not support all or certain AI/ML positioning capabilities, certain LMFs may not have the necessary hardware capabilities for AI/ML procedures, certain LMFs can only handle either direct AI/ML positioning or assisted AI/ML positioning or both, and so forth.
  • Some exemplary scenarios include (but are not limited to) : A) processing capabilities, B) energy savings, C) privacy, D) radio configuration conditions, and E) type of LMF deployment.
  • this type of UE condition largely depends on the hardware capabilities of the UE in terms of e.g., memory limits, storage limits, number of processing/GPU cores. This relates to the ability for the UE to co-share processes related to communication and positioning, depending on which operation is prioritized at a given time, e.g., if positioning is prioritized, more resources may be allocated over larger bandwidths, enable DL-PRS aggregation, higher measurement capability, all in effort for higher accuracy location estimates, on the other hand if communication is prioritized then the UE conditions related to positioning can be limited by the UE, e.g., use of smaller supported DL-PRS symbols, use of lower processing capabilities.
  • a reduced capability (RedCap) or IoT UE may be due to energy constraints such as battery level, deactivate certain positioning functionalities, thus operate under limited UE conditions, therefore decide only to report lower processing capabilities or Tx frequency hopping and so forth.
  • a UE may decide to report only limited capabilities to the network in certain cases which are not regulatory/emergency, e.g., in order preserve user location privacy.
  • the UE conditions are directly dependent on the network conditions, e.g., in terms of current radio configurations:
  • the CA configuration could dynamically be updated in a given positioning session, e.g., the frequency band combination indicator, which is applicable to the current network configuration, transmitted within the srs-PosResourceConfigCA-BandList RRC information element.
  • the UE’s SRS positioning capability is only reported per the currently configured band and the network would require another set of capabilities/UE conditions/UE applicable functionalities need to be reported to the network, e.g., base station or LMF by the UE, when the UE moves from the current serving cell, or the band combination is updated during an ongoing session.
  • the dl-PRS-ResourcesBandCombinationList IE contains the current band combination configuration, the UE reports all band combinations applicable to the current configuration and will have to report another set of capabilities/UE conditions if the network band configuration is updated at a given time.
  • LMFs may have different functionalities/capabilities in terms of e.g., AI/ML positioning or non-AI/ML positioning, different vendor implementations, and therefore a UE may only report the UE capabilities/UE conditions/UE applicable functionalities for which it was requested, while reserving another set of UE capabilities/UE conditions/UE applicable functionality for another LMF depending on the LMF’s support of those functionalities/capabilities.
  • an identifier e.g., associated ID
  • applicable functionalities considering UE and network conditions needs to be defined in such a manner that avoids any ambiguity between UE and network while ensuring that consistency is maintained between training and inference. This assists in avoiding any performance loss of AI/ML models due to data input misalignment.
  • Figure 8 illustrates an example of a mapping structure 800 of an associated ID to information relating to UE and network conditions and applicable functionalities, in accordance with aspects of the present disclosure.
  • the associated ID 802 can be derived at the network entity, e.g., LMF, according to the number of unified applicable functionalities 804.
  • unified functionality is used to differentiate a “UE applicable functionality” in that the unified functionality considers the combination of UE conditions, UE supported/applicable functionality and gNB conditions into a single set of unified functionalities.
  • UE applicable functionality refers to functionalities that the UE is ready to apply at inference (from UE perspective) , which is used in a broader sense.
  • a certain LMF may only support a maximum X ⁇ N number of associated IDs 802, which can be up to deployment or implementation.
  • the associated ID 802 may be exchanged to align on a particular set of UE or network conditions.
  • the unified applicable functionalities 804 may be derived at a centralized wireless communication network entity, e.g., LMF or NWDAF (e.g., LMF can forward this information to NWDAF) .
  • Each unified applicable functionality 804 further comprises one or more UE supported functionalities 806 (e.g., if the model is not available at the UE) and/or one or more UE applicable functionalities 808 and/or one or more gNB (s) condition sets 810.
  • each UE supported functionality 806 may further comprise of a set of UE conditions 812, which may also be referred to as “UE capabilities” in other implementations.
  • the UE conditions 812 may be split into one or more static capabilities (or static feature groups) 814 and one or more dynamic UE capabilities (or dynamic feature groups) 816.
  • each UE applicable functionality 808 may further comprise of a set of UE conditions 818.
  • the UE conditions 818 may be split into one or more UE internal hardware parameters/conditions 820 and one or more dynamic UE conditions 822.
  • the indication that these capabilities/conditions are static or dynamic may be sent explicitly or known implicitly to the network.
  • the one or more UE internal hardware parameters/conditions 820 are not known to the network or part of protecting the proprietary implementation, and therefore not signaled. In other implementations, at least one of the UE internal hardware parameters/conditions 820 may be reported to the network.
  • the gNBs condition sets 810 may be split into gNB antenna/radio configurations 824 (e.g., antenna boresight, DL-PRS boresight direction in terms of azimuth angles, DL-PRS boresight elevation angles, DL-PRS configuration, band information, etc. ) and gNB internal hardware parameters/conditions 826 (e.g., processor speed/power, memory usage, radio frequency (RF) related variables, etc. ) .
  • This may also be referred to as “assistance data” in the context of the 3GPP positioning framework.
  • the gNB antenna/radio configurations 824 may be further broken down into dynamic UE capabilities (or feature groups) 816, implying that each gNB configuration is associated with a reported UE capability and that if the configuration changes, then so does the corresponding UE capability, and dynamic gNB conditions 828, which may comprise area information such as physical cell identity (PCI) , TRP ID, cells, NR cell global identifier (NCGI) , absolute radio frequency channel number (ARFCN) , zone ID, or other geographical coverage information or temporal information, e.g., time interval for which training and inference is needed to be consistent.
  • PCI physical cell identity
  • TRP ID cells
  • NGI NR cell global identifier
  • ARFCN absolute radio frequency channel number
  • zone ID or other geographical coverage information or temporal information, e.g., time interval for which training and inference is needed to be consistent.
  • the gNB internal hardware parameters/conditions 826 are known to the network, and therefore not signaled. In other implementations, the UE internal hardware parameters/conditions 826 may be reported to the network. Note that the dashed lines around the blocks indicate optional blocks that may or may not be included depending on the scenario, while dashed arrows indicate a dependency between blocks.
  • Figure 9 illustrated an example of a nesting structure of the information according to Figure 8.
  • a first associated ID (denoted as “Associated ID 1” ) corresponds to a first unified functionality (denoted as “Unified Applicable Functionality 1” )
  • a second associated ID (denoted as “Associated ID 2” ) corresponds to a second unified functionality (denoted as “Unified Applicable Functionality 2” )
  • Each unified functionality may correspond to a UE supported functionality, or a UE applicable functionality, or a gNB configuration, or combinations thereof.
  • the UE supported functionalities, and the UE applicable functionalities are each associated with UE conditions and capabilities, for example, a static condition and/or a dynamic condition.
  • each gNB configuration may be associated with a radio configuration.
  • the UE supported functionality and the UE applicable functionality may be integrated into a single IE structure.
  • the relevant UE condition and capability fields may be updated, e.g., in case there is a change of the UE supported functionality between training and inference.
  • the associated ID (or similar ID, e.g., configuration ID) may be an explicit ID, e.g., having a value specifically included in the message/signaling.
  • the associated ID may be implicitly indicated, e.g., depending on the DL-PRS configuration index related to the number of TRPs each associated with a DL-PRS configuration (e.g., nr-DL-PRS-ResourceSetList-r16) for each TRP up to maximum number of TRPs (e.g., 64) .
  • the associated ID may be a simpler mapping of the gNB condition set, comprising only radio configuration parameters, e.g., DL-PRS configuration, or legacy assistance data elements.
  • the associated ID may be derived from a combination of TRP-ID, DL-PRS-ID, PCI ID, NCGI ID, and NR ARFCN. In other embodiments, the associated ID may be simply composed of one or more combinations of TRP-ID, DL-PRS-ID, PCI ID, NCGI ID, and/or NR ARFCN.
  • the associated ID may be unique per cell, PCI ID, NCGI ID, NR ARFCN or per combination of TRPs.
  • the unified applicable functionality can further consider, in addition to UE capabilities, a gNB condition and/or a dynamic UE condition.
  • TAG timing error group
  • the individual elements within the assistance data may be mapped to an associated ID or any defined ID.
  • the assistance data may additionally (or alternatively) comprise: geographical coordinates of the TRPs served by the gNB (including a transmission reference location for each DL-PRS resource ID, a timing relative to the serving (reference) TRP of candidate NR TRPs, a reference location for the transmitting antenna of the reference TRP, and/or relative locations for transmitting antennas of other TRPs) , TRP beam/antenna information (including azimuth angle, zenith angle, and/or relative power between PRS resources per angle per TRP) , spatial direction information (e.g. azimuth, elevation, etc.
  • DL-PRS resources of the TRPs served by the gNB e.g., a DL-PRS configuration (e.g., of candidate NR TRPs/base stations, PCIs, global cell IDs (GCIs) , ARFCN, and/or PRS IDs of candidate NR TRPs for measurement)
  • SSB information of the TRPs e.g., the time/frequency occupancy of SSBs
  • a PRS-only TP indication e.g., the time/frequency occupancy of SSBs
  • PRS-only TP indication e.g., the time/frequency occupancy of SSBs
  • on-demand DL-PRS configurations e.g., the validity area of the assistance data
  • data facilitating the integrity results determination of the calculated location e.g., an indication of which DL-PRS resource sets across DL-PRS positioning frequency layers are linked for DL-PRS bandwidth aggregation, a fine timing relative to the serving (reference) T
  • the dynamic UE conditions may further consider network conditions provided by LMF, but which may change depending on the UE preference.
  • the individual elements within the legacy assistance data may be mapped to an associated ID or any defined ID, the legacy assistance data comprising, for example, LOS/NLOS indicators, PRU measurements, and/or PRU location information.
  • Each of the above information elements may comprise further IEs with corresponding value ranges.
  • the UE needs a unified mechanism in which to report the same set of dynamic UE capabilities, gNB conditions or dynamic UE conditions during the inference stage to ensure consistency between training and inference. Due to the complexity of considering all possible changes or combinations, since each IE has different values and there could be numerous conditions applicable.
  • the LMF provides an indication of the change of gNB conditions (for any given reason, e.g., resource availability, etc. ) during inference. For example, if a condition changes from the set of gNB 1 conditions described above, then the LMF may signal the changed condition by indicating the associated sub-ID (also referred to as a “sub-associated ID” ) , such as gNB 1-1, or gNB 1-2, etc., which informs the UE that one or more sub-conditions have changed during the inference stage.
  • sub-ID also referred to as a “sub-associated ID”
  • a similar set of procedures may also apply to the dynamic UE conditions and/or dynamic network conditions (e.g., dynamic UE/NW conditions) .
  • dynamic network conditions e.g., dynamic UE/NW conditions
  • the UE implicitly understands that the rest of the remaining sub-conditions have not changed since training.
  • the signaling overhead of conveying such information depends on the number of sub-conditions, which have changed.
  • an ID (such as associated ID or any other defined ID) may be associated with one or more sub-conditions, described above. However, the ID may be limited in capturing the number of combinations of parameters across all sub-conditions and dynamic UE capabilities.
  • the UE may indicate its desired gNB condition in terms of a gNB condition sub-ID (also referred to as a “sub-condition ID” ) , e.g., a preferred value range of IEs within a sub-ID.
  • a gNB condition sub-ID also referred to as a “sub-condition ID”
  • the UE may selectively inform the network of a change in UE capability during inference, while also indicating a preference for a certain gNB or a dynamic UE/NW condition or assistance data, e.g., as specified with each sub-condition.
  • the network may also inform the UE of a change in a gNB condition or dynamic UE/NW conditions or assistance data via an indication of the change in sub-condition ID or simply signaling the new set of sub-conditions during the inference stage.
  • the network and UE may exchange the requirement of limited configurations and conditions that are essentially critical for the AI to be applicable.
  • a list of configurations may be input for inference, but not all conditions of the configuration are relevant for the applicability determination.
  • TRP/ARP location information and “DL-PRS beam-power information” really matter for the applicability determination.
  • Such implementations may also apply to the dynamic UE condition set, wherein network conditions are initially provided by the LMF, but may change depending on the UE preference.
  • D-UE-1 [PRU measurement and location information]
  • D-UE-2 [expected LOS/NLOS at previous location]
  • D-UE-3 [requested area for inference (e.g., TRP-ID, DL-PRS-ID, PCI ID, CGI ID, ARFCN, etc. ) ]
  • D-UE-4 [requested temporal information (e.g., time period in UTC time, etc. ) for inference] .
  • the UE may inform the LMF about the sub-ID (e.g., sub-associated ID or sub-condition ID) under which its AI functionality is applicable.
  • the LMF may inform the UE about the sub-ID that can be configured to the UE, wherein the UE then selects a condition from the applicable sub-ID.
  • new message contents and messaging procedures are defined wherein a core network entity (such as location server, LMF, or NWDAF) requests supported functionalities of one or more AI/ML models stored at the UE-side.
  • the core network entity may trigger the request for supported functionalities.
  • the core network entity may receive a trigger from another network entity/function or UE.
  • the “UE-side” comprises of the UE device as well as an over-the-top (OTT) server associated to one or more UE devices.
  • OTT over-the-top
  • the AI/ML models may be used to perform either direct AI/ML positioning or assisted AI/ML positioning.
  • a key aspect of the second solution is that the network entity determines, and selects, which of the applicable functionalities are to be activated. This is essentially a network coordinated decision (e.g., among LMF, serving gNBs/TRPs, neighboring gNBs/TRPs, involved UEs, etc. ) , whereby the applicable functionality comprises a combination of UE and network conditions.
  • Figure 10 illustrates an example of a network-solicited functionality exchange procedure 1000, e.g., with a UE, in accordance with aspects of the present disclosure.
  • the exemplary variant depicted in Figure 10 represents a reactive approach for systematic procedures to request, report, update, activate/deactivate supported and applicable functionality for AI/ML models for positioning.
  • the procedure 1000 involves a wireless communication network entity 1002, such as an LMF or location server or NWDAF, and a UE 1004.
  • the network entity 1002 may be an embodiment of the NE 102 and/or the CN 106.
  • the UE 1004 may be an embodiment of the UE 104 and/or the UE 206.
  • the network entity 1002 may transmit a request message, e.g., using LPP RequestCapabilities message, relating to the supported functionalities of one or more UE-sided models (see signaling 1006) .
  • the supported functionalities may comprise of supported functionalities of one or more UE-sided models, which are known to the UE but not yet available on the local UE device, e.g., the AI/ML model is to be fetched or downloaded at certain future instance time instance.
  • the network entity may also request the static and/or dynamic UE conditions from the UE.
  • the network entity 1002 may transmit a request message relating to the applicable functionalities of one or more UE-sided models.
  • the network entity 1002 (such as an NWDAF) may request for the supported or applicable functionality via a request message sent to an LMF, e.g., via network function (NF) interface, which serves as a further trigger to send another LPP request to the one or more UEs for the UE functionalities or UE conditions, e.g., as per Step 1 of Figure 10.
  • LMF network function
  • NF network function
  • Examples of static UE conditions (also static UE capabilities) over the lifetime of the UE 1004’s LPP session or UE 1004’s connection to the network may include, but are not limited to: support of AI/ML positioning (in general) , support of direct AI/ML positioning, support of assisted AI/ML positioning, support of non-AI/ML (i.e., legacy) positioning methods, support of reporting time domain representations of positioning measurements (e.g., including sample-based and/or path-based measurements) , support of AI/ML positioning assistance data, supporting of certain data collection reporting modes including labelled and/or un-labelled data, and combinations thereof.
  • support of AI/ML positioning in general
  • support of direct AI/ML positioning support of assisted AI/ML positioning
  • support of non-AI/ML (i.e., legacy) positioning methods support of reporting time domain representations of positioning measurements (e.g., including sample-based and/or path-based measurements)
  • support of AI/ML positioning assistance data supporting of certain data collection reporting modes including labelled and/or un-labelled data
  • Examples of dynamic UE conditions over the lifetime of the UE 1004’s LPP session or UE 1004’s connection to the network may include, but are not limited to: support of DL-PRS processing capability (e.g., including processing of certain types of DL-PRS resource configurations) , support of AI/ML positioning measurement capabilities, support of non-AI/ML positioning measurement capabilities, support of direct AI/ML positioning capabilities, support of assisted AI/ML positioning capabilities, support of DL-PRS quasi-co-location (QCL) processing capabilities, support of DL-PRS processing capabilities, total number samples supported, mapping of measured quantity to reported quantity value associated to a k-value, total number of subsamples supported, area information in which training and/or inference is performed, and combinations thereof.
  • DL-PRS processing capability e.g., including processing of certain types of DL-PRS resource configurations
  • AI/ML positioning measurement capabilities e.g., including processing of certain types of DL-PRS resource configurations
  • the network entity 1002 may also request that that the UE 1004 may report changes in (dynamic) UE conditions, wherein if the network entity 1002 does not indicate such support in the request message, then the network entity 1002 assumes that the UE 1004 does not report updated changes in the UE conditions.
  • the UE 1004 may trigger a UE-initiated request, e.g., on-demand PRS or using the LPP ProvideLocationInformation message to provide the updated UE condition.
  • Step 1 the network entity 1002 and the UE 1004 are aware about the associated IDs, which may be configured during the training phase.
  • the UE 1004 which receives the message in Step 1, may respond to the network entity 1002’s request by transmitting an LPP message with one or more of the UE 1004’s supported functionalities and static and/or dynamic UE conditions (see signaling 1008) .
  • the supported functionalities and static and/or dynamic UE conditions may be transmitted in terms of a list/index, e.g., for the case where more than one supported functionalities is being transmitted.
  • the UE 1004 transmits the LPP ProvideCapabilityInformation message to indicate the supported functionalities and static and/or dynamic UE conditions.
  • the UE 1004 initially sends all the supported functionalities of the one or more AI/ML models. Thereafter, the UE 1004 may transmit another message, e.g., using LPP ProvideCapabilityInformation message, to the network indicating all the applicable functionalities of the one or more available AI/ML models at the UE 1004 with or without associated information.
  • This message may be transmitted based on either a request by the LMF, e.g., using LPP RequestCapabilities message, as in Step 1 or may be transmitted in an unsolicited manner, i.e., without a request from the network.
  • the UE may only simply report the associated ID (s) of the one or more applicable functionalities.
  • the UE conditions may comprise per-UE or per-band feature groups (FGs) .
  • each FG may be static or dynamic.
  • each sub-feature within each FG may be static or dynamic.
  • the UE 1004 does not send UE static conditions and dynamic conditions; instead, the UE 1004 may report only the set of functionalities that are applicable. This may allow the network entity 1002 (e.g., LMF) to know which functionalities are currently possible for the UE 1004, thereby the network entity 1002 will only be able to activate/configure from these reported applicable functionalities. In this way, the UE 1004 can keep the UE conditions confidential without revealing them to the gNB. For example, the UE 1004 may not want to tell their battery level, or graphics processing unit (GPU) availability, and so forth.
  • GPU graphics processing unit
  • an explicit priority indicator may include a “bit” or “integer” representations of the priority, e.g., the lowest number, e.g., “1” or “0” is the highest priority, while the highest number, e.g., “N” is the lowest priority.
  • an implicit priority indicator may include the transmission of the applicable functionality in descending order of priority within a list/index, where the first applicable functionality on the list is the highest priority applicable functionality, while the last applicable functionality is lowest priority.
  • an implicit priority indicator may include the transmission of the applicable functionality in ascending order of priority within a list/index, where the last applicable functionality on the list is the highest priority applicable functionality, while the first applicable functionality is lowest priority.
  • the network entity 1002 determines and selects one or more unified applicable functionalities, e.g., for activation (see block 1010) .
  • the network entity 1002 may also take into account the received prioritization, where applicable. For example, the network entity 1002 may consider the received applicable functionalities from the UE perspective, the UE conditions and the gNB/TRP (e.g., NG-RAN) conditions. Such procedures are described in further detail below.
  • the network entity 1002 upon determining/selecting the one or more unified applicable functionalities in Step 3, activates or configures the one or more unified applicable functionalities by transmitting an LPP message to the UE 1004 (see signaling 1012) .
  • the network entity 1002 may activate or configure the one or more unified applicable functionalities via the LPP ProvideAssistanceData message.
  • the one or more unified applicable functionalities can be signaled in terms of assistance data, e.g., DL-PRS configurations.
  • the activation command may be explicit in terms of an activation or configuration message associated to each assistance data element, e.g., DL-PRS configuration with an associated ID or in another implementation it may simply be an activation command or configuration with an associated ID (reduce signaling overhead of indicating each of the assistance data elements, e.g., DL-PRS configuration) .
  • the activation command or configuration may also be implicit via the inclusion of each assistance data element, e.g., DL-PRS configuration, which implies that such applicable functionality has been activated or configured, wherein the exclusion of a particular each assistance data element, e.g., DL-PRS configuration (applicable functionality) implies that that DL-PRS configuration (applicable functionality) has not been activated or configured.
  • each assistance data element e.g., DL-PRS configuration
  • DL-PRS configuration appcable functionality
  • the network entity 1002 may explicitly or implicitly signal the activation command or configuration using other LMF-to-UE LPP messages such as LPP ProvideCapability message or LPP ProvideLocationInformation message.
  • this Step 4 LPP ProvideAssistanceData message may include the inference configuration or inference assistance data required at inference to obtain the UE location at inference.
  • the inference configuration or inference assistance data required at inference may also be transmitted using the LPP RequestLocationInformation message.
  • the LMF may explicitly or implicitly indicate that the applicable functionality is to be only activated in a certain defined area based on the validity area of the assistance data elements, e.g., DL-PRS configuration, wherein an area is defined as a CGI, PCI, ARFCN, zone, or combination thereof or in terms of a list of areas wherein an applicable functionality has been activated.
  • DL-PRS configuration e.g., DL-PRS configuration
  • an area is defined as a CGI, PCI, ARFCN, zone, or combination thereof or in terms of a list of areas wherein an applicable functionality has been activated.
  • a further message may be transmitted from a network entity 1002 to UE 1004 to request for the UE location computed using either AI/ML positioning or non-AI/ML positioning or a combination of both positioning methods, e.g., using LPP RequestLocationInformation message and thereafter the network entity 1002 may receive the response from the UE 1004, e.g., using the LPP ProvideLocationInformation response message.
  • the network entity 1002 or the UE 1004, or both may detect that one or more UE conditions (or UE capabilities, or UE applicable functionalities) have changed or that other aspects of an AI/ML model have changed (see block 1014) .
  • This step may be initiated upon any changes, or deviations, or updates of the UE conditions (or UE capabilities, or UE applicable functionalities) , which in turn may cause an update in the applicable functionality from the UE perspective.
  • one or more network or gNB conditions may have also changed, which may be covered by this step.
  • the UE 1004 transmits an LPP message to the network entity 1002 to update the one or more UE conditions, or another changed aspect of AI/ML model (see signaling 1016) .
  • This step is required when the applicable functionality from the UE perspective or UE conditions are updated.
  • the UE 1004 provides the aforementioned update using an unsolicited LPP message, such as the LPP ProvideCapabilityInformation message.
  • the UE 1004 indicates the update by transmitting an indication of another associated ID within the scope of the list of associated ID (s) and applicable functionalities transmitted.
  • the LPP RequestAssistanceData message may also be used to implement Step 6.
  • this message may be transmitted to the network entity 1002 upon request by the network entity regarding any change of the UE applicable functionality or UE conditions, e.g., using the LPP RequestCapabilities message.
  • changes in some of the explicit parameters included within the applicable functionalities may also be indicated via Step 6, e.g., changes in certain desired DL-PRS configuration parameters such as resource ID, resource set ID, resource time gap, RE offset, symbol offset, bandwidth, comb size, QCL, subcarrier spacing (numerology) , resource priority, etc.
  • the UE 1004 may also define a new applicable functionality from the UE perspective. In another implementation, the UE 1004 can accordingly change the list of applicable functionalities, without explicitly signaling that the UE 1004 has updated conditions.
  • the UE 1004 may assign an explicit or implicit priority indicator for each of the updated applicable functionalities, enabling the network entity 1002 (e.g., LMF) to understand the context of each of the updated applicable functionality.
  • an explicit priority indicator may include a “bit” or “integer” representations of the priority, e.g., the lowest integer number, e.g., “1” or “0” is the highest priority, while the highest integer number, e.g., “N” is the lowest priority.
  • an implicit priority indicator may include the transmission of the applicable functionality in descending order of priority within a list/index, where the first applicable functionality on the list is the highest priority applicable functionality, while the last applicable functionality is lowest priority.
  • the implicit priority indicator may include the transmission of the applicable functionality in ascending order of priority within a list/index, where the last applicable functionality on the list is the highest priority applicable functionality, while the first applicable functionality is lowest priority.
  • the network entity 1002 selects and activates the one or more new/updated applicable functionalities by transmitting an LPP message to the UE 1004 (see signaling 1018) .
  • the network entity 1002 may activate the one or more unified applicable functionalities via the LPP ProvideAssistanceData message.
  • the one or more new/updated applicable functionalities can be signaled in terms of one or more DL-PRS configurations.
  • the supplementary service (SS) messages with LPP containers may also be used to transfer the information from the network entity 1002 to the UE 1004, or from the UE 1004 to the network entity 1002 (e.g., LMF) .
  • SS supplementary service
  • Figure 11 illustrates an example of a network-solicited RAN condition exchange procedure 1100, e.g., with an NG-RAN node, gNB or TRP, in accordance with aspects of the present disclosure.
  • the exemplary variant depicted in Figure 11 represents procedures to request, report, and update NG-RAN node/gNB/TRP conditions, referred to hereafter as “RAN conditions”, and to activate/deactivate supported and applicable functionalities based on the RAN conditions.
  • RAN conditions procedures to request, report, and update NG-RAN node/gNB/TRP conditions
  • the procedure 1100 involves a wireless communication network entity 1102, such as an LMF or location server or NWDAF, and a RAN node 1104.
  • the network entity 1102 may be an embodiment of the network entity 1002, the NE 102 and/or the CN 106.
  • the RAN node 1104 is a NG-RAN node, or gNB, or TRP, and may be an embodiment of the NE 102 and/or the RAN node 208.
  • the network entity 1102 may transmit a request message relating to the supported NG-RAN node/gNB/TRP conditions, referred to hereafter as “RAN conditions” (see signaling 1106) .
  • the supported RAN conditions may comprise of additional conditions, which are required to ensure consistency between training and inference of AI/ML models on the UE-side. In the other implementations, consistency between training and inference of AI/ML models on the LMF-side are also supported.
  • the network entity 1102 may also request the static and/or dynamic RAN conditions from the RAN node 1104. Note that This message is transmitted to all RAN nodes 1104 connected to the network entity 1102 according to a certain deployment. In other implementations, this Step may also be initiated to update an existing RAN condition during inference applicable to both LMF-initiated and UE-initiated on-demand PRS.
  • the network entity 1102 may request for the RAN conditions via a request message sent to a LMF, e.g., via an NF interface, which serves as a further trigger to send another NR Positioning Protocol A (NRPPa) request to the one or more RAN nodes 1104 for the RAN conditions, e.g., as per Step 1 of Figure 11.
  • NRPPa NR Positioning Protocol A
  • Step 1 may also occur during the training phase, where a set of associated ID is defined at the network entity 1102.
  • static RAN conditions may include, but are not limited to: support of AI/ML positioning in general, support of direct AI/ML positioning, support of assisted AI/ML positioning, support of non-AI/ML (legacy) positioning methods, and/or support of broadcast of AI/ML positioning assistance data, such as, TRP beam antenna information, TRP beam antenna angles, and so forth.
  • Examples of dynamic RAN conditions may include, but are not limited to: DL-PRS configuration parameters, e.g., PRS resource set ID, subcarrier spacing, PRS bandwidth, start PRB, point A, comb size, cyclic prefix (CP) type, resource set periodicity, resource set slot offset, resource repetition factor, resource time gap, resource number of symbols, PRS muting options 1 and 2, RE offset, PRS resource ID, sequence ID, resource symbol offset, PRS beam information, DL-PRS resource coordinates relative to the TRP coordinate, antenna reference point (ARP) location information, TRP timing error group (TEG) information, TRP Tx TEG association, TRP RxTx TEG information, QCL information including source, aggregated PRS resource List, SRS configuration parameters, and so forth.
  • DL-PRS configuration parameters e.g., PRS resource set ID, subcarrier spacing, PRS bandwidth, start PRB, point A, comb size, cyclic prefix (CP) type, resource set periodicity, resource set slot offset,
  • the RAN node 1104 which receives the message in Step 1, may respond to the network entity 1102’s request by transmitting a NRPPa message, e.g., with all the supported RAN conditions (see signaling 1108) .
  • the RAN conditions may be transmitted in terms of a list/index, e.g., for the case where more than one RAN conditions is being transmitted.
  • the UE 1004 transmits the NRPPa TRP Information Response message to indicate the RAN conditions.
  • the network entity 1102 determines and selects the one or more unified applicable functionalities, e.g., for activation (see block 1110) .
  • the network entity 1002 may determine/select the unified applicable functionalities in terms of the received RAN conditions according to the procedure of Figure 11, and one or more received applicable functionalities from UE perspective and UE conditions, e.g., according to the procedure of Figure 10.
  • the network entity 1102 upon determining/selecting the one or more unified applicable functionalities in Step 3, activates or configures the one or more unified applicable functionalities by transmitting an NRPPa message to the RAN node 1104 (see signaling 1112) .
  • the network entity 1102 may request for activation or configuration of the one or more unified applicable functionalities via the NRPPa PRS Configuration Request message.
  • the configuration/activation of a particular condition can be signaled in terms of DL-PRS configurations that may be applicable to one or more RAN nodes 1104.
  • the network entity 1102 may transmit another similar message to configure and activate SRS transmissions by the RAN node 1104.
  • the RAN node 1104 transmits a response message (e.g., a NRPPa PRS Configuration Response message) confirming the configuration/activation of a particular condition (or DL-PRS configuration or other implementation SRS transmission) , which may be applicable to one or more RAN nodes 1104 (see signaling 1114) .
  • a response message e.g., a NRPPa PRS Configuration Response message
  • a particular condition or DL-PRS configuration or other implementation SRS transmission
  • the network entity 1102 or the RAN node 1104, or both may detect that one or more RAN conditions have changed (see block 1116) .
  • This step may be initiated upon any changes, or deviations, or updates of the RAN conditions, which in turn may cause an update in the applicable functionality defined at the network entity 1102, e.g., removal of a TRP, or addition of a TRP, etc.
  • the step may be UE-initiated implying that a change or update of RAN conditions, e.g., DL-PRS configuration is desired from the UE perspective and therefore the network entity 1102 may transmit an updated message to the RAN node 1104.
  • the RAN node 1104 transmits an NRPPa message to the network entity 1102 to update the one or more RAN conditions (see signaling 1118) . This step is required if the RAN conditions are updated. This enables the RAN node 1104 to provide the aforementioned update using unsolicited an NRPPa message, e.g., NRPPa PositioningInformationUpdate message. In certain embodiments, the RAN node 1104 indicates the update by transmitting an indication of another associated ID within the scope of the list of associated ID (s) and applicable functionalities transmitted.
  • the RAN node 1104 may also define a new RAN condition (or DL-PRS or SRS configuration) .
  • the network entity 1102 requests the RAN node 1104 to configure/activate the updated condition, which may be equivalent to DL-PRS configuration that may be applicable to one or more RAN nodes 1104 (see signaling 1120) .
  • the network entity 1102 may configure or activate the updated condition via the NRPPa PRS Configuration Request message.
  • the RAN node 1104 transmits a response message (e.g., a NRPPa PRS Configuration Response message) confirming the configuration/activation of the updated RAN condition (or DL-PRS configuration or other implementation SRS transmission) , which may be applicable to one or more RAN nodes 1104 (see signaling 1122) .
  • a response message e.g., a NRPPa PRS Configuration Response message
  • the network entity 1102 may configure or activate the updated condition via the NRPPa PRS Configuration Request message.
  • the SS messages with LPP containers may also be used to transfer the information from LMF to UE or from UE to LMF.
  • the procedures to initiate one or more steps in Figure 11 may be UE-initiated for UE-sided models or in other implementations LMF-initiated for network-sided models, e.g., AI/ML models at the LMF or NWDAF.
  • the steps outlined in the procedures of Figures 10 and 11 may happen in parallel, in the case of UE-sided models or network-sided models.
  • the coordination between the network entity 1102 and the RAN node 1104 on reception of RAN conditions and the coordination between network entity 1102 and the UE on the reception of the supported/applicable functionalities and/or UE conditions can occur independently.
  • new message contents are defined wherein a core network entity (such as location server, LMF, or NWDAF) can provision the UE with a list of all applicable functionalities based on prior reception of UE capabilities, UE conditions, UE applicable functionalities, RAN conditions, and/or DL-PRS configurations.
  • a core network entity such as location server, LMF, or NWDAF
  • the UE is supported to select the required applicable functionalities from the received list of all applicable functionalities to be activated from the network.
  • the UE applicable functionality is different from the applicable functionality provided by the LMF in that the UE applicable functionality is only applicable to one or more UEs, while the applicable functionality provided by the LMF is a “global” applicable functionality derived from a combination of UE applicable functionality, UE conditions, RAN conditions.
  • This embodiment introduces a flexibility such that UE may play stronger role in the selection of an applicable functionality/one or more applicable functionalities out of all possible applicable functionalities provided by the network at this time that is most suited to ensure consistency between training and inference of its own UE-sided models.
  • Figure 12 illustrates an example of a network-based functionality exchange procedure 1200, e.g., with a UE, in accordance with aspects of the present disclosure.
  • the exemplary variant depicted in Figure 12 represents network-based functionality exchange procedures to report a UE selection of a desired applicable functionality, and to activate/deactivate an applicable functionality for AI/ML models for positioning.
  • the procedure 1200 involves a wireless communication network entity 1202, such as an LMF or location server or NWDAF, and a UE 1204.
  • the network entity 1202 may be an embodiment of the network entity 1002, the network entity 1102, the NE 102 and/or the CN 106.
  • the UE 1204 may be an embodiment of the UE 1004, the UE 104, and/or the UE 206.
  • the network entity 1202 e.g., LMF
  • the network entity 1202 has received (e.g., collected) the necessary UE capabilities and/or UE supported functionalities and/or UE applicable functionalities, in addition to RAN conditions and/or configurations (see block 1206) .
  • the network entity 1202 transmits an LPP message to provide a complete list (e.g., as complete as possible) of all applicable functionalities or assistance data in terms of pre-defined configurations to the UE 1204 (see signaling 1208) with associated information, e.g., ID, index IDs, associated IDs, priority information, and so forth.
  • the list of (e.g., all) applicable functionalities may be implemented with either UE-specific signaling or broadcast signaling such as posSIB, SIB, etc. (if applicable functionalities are common to more than one UE) .
  • the UE 1204 may transmit an LPP RequestCapabilityInformation message or an LPP
  • this step may also provide the inference configuration in terms of required assistance data elements needed to perform inference at the UE.
  • the UE may trigger Step 1 via a request message before Step 1 occurs, e.g., using the LPP RequestAssistanceData message.
  • the network entity 1202 may assign an explicit or implicit priority indicator for each of the applicable functionalities, enabling the UE 1204 to understand the context of each of the received applicable functionality from the network perspective.
  • an explicit priority indicator may include a “bit” or “integer” representations of the priority, e.g., the lowest integer number, e.g., “1” or “0” is the highest priority, while the highest integer number, e.g., “N” is the lowest priority.
  • an implicit priority indicator may include the transmission of the applicable functionality in descending order of priority within a list/index, where the first applicable functionality on the list is the highest priority applicable functionality, while the last applicable functionality is lowest priority.
  • an implicit priority indicator may include the transmission of the applicable functionality in ascending order of priority within a list/index, where the last applicable functionality on the list is the highest priority applicable functionality, while the first applicable functionality is lowest priority.
  • the UE 1204 determines and selects the desired unified applicable functionality or functionalities, e.g., for desired activation or configuration, out of the list of all received unified applicable functionalities provided by the network (see block 1210) .
  • the selection is based on the received prioritization, where applicable.
  • the UE 1204 transmits an indication regarding its desired applicable functionality or functionalities (see signaling 1212) .
  • the indication may be implemented in the form of a transmitting an associated ID related to the desired applicable functionalities.
  • the UE may transmit an index or list of associated IDs in the case that there are multiple desired/recommended applicable functionalities to be activated.
  • the UE 1204 may respond with a few (i.e., more than one) functionalities or assistance data elements selected from the candidate functionalities or assistance data elements that the network entity 1202 first provided in Step 1 (e.g., which are feasible to be activated from the network side) and the network entity 1202 selects one of them and then also inform the UE 1204 which one is the final confirmed functionality in a separate step, such as in another implementation of Step 4.
  • the network entity 1202 activates or configures the desired/recommended functionality based on the received information from the UE 1204 (see block 1214) .
  • the network entity 1202 sends a confirmation message to the UE 1204, so the UE 1204 can make sure that his proposed functionality gets activated.
  • a further message may be transmitted from a network entity 1202 to UE 1204 to request for the UE location computed using either AI/ML positioning or non-AI/ML positioning or a combination of both positioning methods, e.g., using LPP RequestLocationInformation message and thereafter the network entity 1202 may receive the response from the UE 1204, e.g., using the LPP ProvideLocationInformation response message.
  • the network entity 1202 or the UE 1204, or both may detect a change of UE conditions (or UE capabilities, or UE applicable functionalities) or may detect is a need to update the previously activated functionalities (see block 1216) .
  • a change in RAN or network conditions may also be detected.
  • the UE 1204 transmits the desired/updated functionality via another updated message with a similar indications as described Step 3 (see signaling 1218) .
  • other LPP messages such as RequestAssistanceData, ProvideLocationInformation may be enhanced to carry the updated desired applicable functionalities.
  • the network transmits an updated configuration to the UE, e.g., using LPP ProvideAssistanceData message in case of a change in RAN or network conditions.
  • the UE 1204 may transmit the updated functionalities based on an explicit or implicit priority indicator for each of the updated applicable functionalities received by the network in Step 1.
  • an explicit priority indicator may include a “bit” or “integer” representations of the priority, e.g., the lowest integer number, e.g., “1” or “0” is the highest priority, while the highest integer number, e.g., “N” is the lowest priority.
  • an implicit priority indicator may include the transmission of the applicable functionality in descending order of priority within a list/index, where the first applicable functionality on the list is the highest priority applicable functionality, while the last applicable functionality is lowest priority.
  • an implicit priority indicator may include the transmission of the applicable functionality in ascending order of priority within a list/index, where the last applicable functionality on the list is the highest priority applicable functionality, while the first applicable functionality is lowest priority.
  • the SS messages with LPP containers may also be used to transfer the information from the network entity 1202 to the UE 1204, or from the UE 1204 to the network entity 1202 (e.g., LMF) .
  • the network entity 1202 may further activate the updated functionality or may activate an applicable functionality out of a set of desired applicable functionalities provided by the UE 1204.
  • new message contents and messaging procedures enable a UE to proactively initiate/trigger the provision of UE supported functionalities and/or UE applicable functionalities.
  • Figure 13 is an exemplary procedural call flow of the UE-initiated procedure to proactively provide UE supported/applicable functionality to the network.
  • Figure 13 illustrates an example of a UE-initiated functionality exchange procedure 1300, in accordance with aspects of the present disclosure.
  • the exemplary variant depicted in Figure 13 represents a UE-initiated proactive transfer of supported and/or applicable functionality, and the activation or deactivation of an applicable functionality for AI/ML models for positioning.
  • the procedure 1300 involves a wireless communication network entity 1302, such as an LMF or location server or NWDAF, and a UE 1304.
  • the network entity 1302 may be an embodiment of the network entity 1002, the network entity 1102, the network entity 1202, the NE 102 and/or the CN 106.
  • the UE 1304 may be an embodiment of the UE 1004, the UE 1204, the UE 104, and/or the UE 206.
  • the UE 1304 receives a request either internally from an LCS client or over-the-top (OTT) server to perform AI/ML-based positioning inference procedures (see signaling 1306) .
  • OTT server may be, e.g., a server managed by a vendor of a chipset of the UE 1304.
  • the UE 1304 provides a list of UE supported functionalities and/or desired applicable functionalities, e.g., desired assistance data elements and/or UE conditions, e.g., static, dynamic to the network entity 1302 (e.g., LMF or NWDAF) (see signaling 1308) .
  • the network entity 1302 e.g., LMF or NWDAF
  • the UE 1304 may transmit an unsolicited LPP ProvideCapability or and LPP RequestAssistanceData message.
  • the supplementary service messages with LPP containers may also be used to transfer the list/index of supported/desired applicable functionalities and/or UE conditions and UE supported/applicable functionalities to the network entity 1302.
  • the UE 1304 can refrain from transmission of its own conditions and instead only report the set of applicable functionalities that matches the current UE conditions.
  • the UE 1304 may transmit the functionalities, e.g., desired assistance data based on an explicit or implicit priority indicator for each of the functionalities or assistance data elements.
  • an explicit priority indicator may include a “bit” or “integer” representations of the priority, e.g., the lowest integer number, e.g., “1” or “0” is the highest priority, while the highest integer number, e.g., “N” is the lowest priority.
  • an implicit priority indicator may include the transmission of the functionality in descending order of priority within a list/index, where the first functionality on the list is the highest priority functionality, while the last functionality is lowest priority.
  • the implicit priority indicator may include the transmission of the applicable functionality in ascending order of priority within a list/index, where the last functionality on the list is the highest priority functionality, while the first functionality is lowest priority.
  • the network entity 1302 determines and selects the desired/recommended unified functionality based on the received applicability information from the UE 1304 (see block 1310) .
  • the network entity 1302 (e.g., LMF) transmits an activation command or configuration according to the desired/recommended unified functionality taking into account the received information from the UE 1304 (see signaling 1312) .
  • the network entity 1302 may transmit the desired assistance data either explicitly or implicitly in the form of certain associated information, e.g., associated IDs. This assistance data may also serve as the inference configuration.
  • a further message may be transmitted from a network entity 1302 to UE 1304 to request for the UE location computed using either AI/ML positioning or non-AI/ML positioning or a combination of both positioning methods, e.g., using LPP RequestLocationInformation message and thereafter the network entity 1302 may receive the response from the UE 1304, e.g., using the LPP ProvideLocationInformation response message.
  • the network entity 1302 or the UE 1304, or both may detect that one or more UE conditions (or UE capabilities, or UE applicable functionalities) have changed (see block 1314) .
  • This step may be initiated upon any changes, or deviations, or updates of the UE conditions, which in turn may cause an update in the applicable functionality from the UE perspective.
  • a change in RAN or network conditions may also be detected.
  • the UE 1304 transmits an LPP message to the network entity 1302 to update the one or more UE conditions (or UE capabilities, or UE applicable functionalities) (see signaling 1316) .
  • This step is required when the applicable functionality from the UE perspective or UE conditions are updated.
  • the UE 1304 provides the aforementioned update using an unsolicited LPP message, such as the LPP ProvideCapabilityInformation message.
  • the UE 1304 indicates the update by transmitting an indication of another associated ID within the scope of the list of associated ID (s) and applicable functionalities transmitted.
  • the network entity 1302 may request the UE 1304 for any change in the supported functionality or UE conditions or UE applicable functionality using a DL message, e.g., LPP RequestCapability message.
  • changes in some of the explicit parameters included within the applicable functionalities may also be indicated via this step, e.g., changes in certain DL-PRS configuration parameters such as resource ID, resource set ID, resource time gap, RE offset, symbol offset, bandwidth, comb size, QCL, subcarrier spacing (numerology) , resource priority, etc.
  • the UE 1304 may also define a new applicable functionality from the UE perspective. In another implementation, the UE 1304 can accordingly change the list of applicable functionalities, without explicitly signaling that the UE 1304 has updated conditions.
  • the UE 1304 transmits the desired/updated UE functionality via another updated message with similar indication.
  • other LPP messages such as RequestAssistanceData, ProvideLocationInformation may be enhanced to carry the updated desired applicable functionalities.
  • Step 6 upon receiving the message in Step 5, the network entity 1302 (e.g., LMF) selects and activates the one or more new/updated applicable functionalities via an activation command or configuration using the LPP ProvideAssistanceData message, where the new/updated applicable functionalities or configuration can be signaled in terms of DL-PRS configurations (see signaling 1318) .
  • the network entity 1302 e.g., LMF
  • the SS messages with LPP containers may also be used to transfer the information from the network entity 1302 to the UE 1304, or from the UE 1304 to the network entity 1302 (e.g., LMF) .
  • the AMF may store the UE conditions and/or UE supported/applicable functionalities and can provide this to the LMF at a later time without having to initiate another request capability procedure with the UE.
  • This serves to reduce latency and air interface signaling and offers the opportunity to rely on CN signaling to store the UE conditions and/or supported/applicable functionality, provided that there is availability of these UE conditions/UE supported/applicable functionalities.
  • the storage also enables provision of the UE conditions, or UE supported functionalities, or UE applicable functionalities for any new request for AI/ML positioning procedures.
  • Figures 14A and 14B illustrate a functionality exchange and storage procedure 1400, in accordance with aspects of the present disclosure.
  • the exemplary variant of Figure 14 enables storage of UE conditions and UE applicable conditions at AMF.
  • the procedure 1400 involves a UE 1402, an NG-RAN 1404, an AMF 1406, and an LMF 1408.
  • the serving AMF 1406 receives a location request (see block 1410) .
  • some entity in the 5GC or CN e.g., gateway mobile location center (GMLC) or other LCS entity
  • GMLC gateway mobile location center
  • the serving AMF 1406 may first receive a UE/user location request from an LCS Client or Application Function.
  • the serving AMF 1406 for the target UE 1402 determines the need for some location service (e.g., to locate the UE 1402 for an emergency call, for network verified location) .
  • the UE 1402 may request some location service (e.g., mobile originating location request (MO-LR) , positioning request, or delivery of assistance data) to the serving AMF 1406, e.g., using an uplink NAS transport message (see signaling 1412) .
  • the UE 1402 may also directly transfer the UE conditions (or UE supported functionalities, or UE applicable functionalities) to the AMF 1406 using uplink NAS transport level signaling, N1 interface, e.g., Namf_Communication, Namf_MT, Namf_Location, or similar messages.
  • the uplink supplementary service messages with LPP containers may also be used to transfer the UE conditions and UE supported/applicable functionalities to the network.
  • the AMF 1406 transfers the received location service request to the LMF 1408, e.g., via the Nlmf_Location_DetermineLocation Request message comprising the stored UE conditions and UE supported functionalities and/or UE applicable functionalities (see signaling 1414) .
  • the AMF 1406 may include the UE conditions (and/or UE supported functionalities and/or UE applicable functionalities) received in Step 2 for a future UE request for AI/ML positioning.
  • the location service request can also include a further indicator on whether a preferred type of method for the location computation, i.e., using AI/ML based positioning methods and also including a further indicator on the type of AI/ML positioning method.
  • the preferred type may be a direct AI/ML positioning technique, or an assisted AI/ML positioning technique, or a non-AI/ML positioning technique.
  • the AMF 1406 may further indicate RAT-dependent techniques (e.g., time difference of arrival (TDOA) , multi-RTT, UL-AoA, DL-AoD, DL carrier phase positioning and so forth) or RAT-independent positioning techniques (e.g., WLAN, assisted GNSS (A-GNSS) , and so forth) .
  • TDOA time difference of arrival
  • A-GNSS assisted GNSS
  • the UE conditions may not be stored in the network and can be received from the LMF 1408 after the completion of Step 8 (below) or an equivalent message that can transmit one or more UE conditions (or UE supported functionalities and/or UE applicable functionalities) .
  • the absence of any UE conditions and UE applicable functionalities in Step 2 may implicitly indicate that the AMF 1406 does not have any stored UE conditions (or UE supported functionalities and/or UE applicable functionalities) .
  • the UE conditions (or UE supported functionalities and/or UE applicable functionalities) may be stored in the AMF after Step 1a has been completed.
  • Steps 3-7 represent LPP and/or NRPPa procedures including capability exchange further comprising UE conditions (or UE supported functionalities and/or UE applicable functionalities) , DL-PRS confirmation provisions, Measurements, TRP information exchange, and UE location calculation.
  • the LMF 1408 initiates a UE positioning procedure 1416 by transmitting an LPP request capabilities message to the UE 1402 (see signaling 1418) .
  • the UE 1402 transmits an LPP provide capabilities message to the LMF 1408 (see signaling 1420) .
  • the LMF 1408 and the UE 1402 exchange LPP messages (see signaling 1422) .
  • the LMF 1408 may transmit a DL-PRS configuration (e.g., associated with a unified applicable functionality as described herein) to the UE 1402.
  • the UE 1402 may transmit positioning-related measurements to the LMF 1408.
  • the LMF 1408 exchanges NRPPa messages with the NG-RAN 1404 (see signaling 1424) .
  • the LMF 1408 may request RAN condition information, and the NG-RAN 1404 may transmit an NRPPa message containing associated IDs and RAN conditions, as described herein.
  • the LMF 1408 determines the location of the UE 1402 (see block 1426) . This ends the UE positioning procedure 1416.
  • the LMF 1408 reports the result of the UE positioning procedure 1416 by transmitting the Nlmf_Location_DetermineLocation response message towards the AMF 1406 (see signaling 1428) .
  • the Nlmf_Location_DetermineLocation response message provides the location of the UE 1402 and may additionally include some meta information, such as the final location method used, e.g., AI/ML or non-AI/ML based positioning.
  • the LMF 1408 may provide the UE conditions and UE applicable functionalities for AMF storage and retrieval at a future time for new AI/ML-based location request.
  • the UE 1402 may directly provide the UE conditions (or UE supported functionalities and/or UE applicable functionalities) to the serving AMF 1406 at the NAS level for storage.
  • the AMF 1406 stores the received UE conditions (or UE supported functionalities and/or UE applicable functionalities) for use at a future instance (see block 1430) .
  • storage limits may be specified in terms of the number of UE conditions and UE supported/applicable functionalities can be stored at a given time for a number of a UEs. If the UE conditions and UE applicable functionalities are not utilized within a certain specified period, these may be flushed or removed from the AMF.
  • the AMF 1406 forwards the UE location to the entity or node that initiated /triggered the location request (see block 1432) .
  • the supplementary service (SS) messages with LPP containers may also be used to transfer the information from the network entity 1002 to the UE 1004, or from the UE 1004 to the network entity 1002 (e.g., LMF) .
  • FIG. 15 illustrates an example of a UE 1500 in accordance with aspects of the present disclosure.
  • the UE 1500 may include a processor 1502, a memory 1504, a controller 1506, and a transceiver 1508.
  • the processor 1502, the memory 1504, the controller 1506, or the transceiver 1508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
  • the processor 1502, the memory 1504, the controller 1506, or the transceiver 1508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • the processor 1502 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central processing unit (CPU) , an ASIC, a field programmable gate array (FPGA) , or any combination thereof) .
  • the processor 1502 may be configured to operate the memory 1504.
  • the memory 1504 may be integrated into the processor 1502.
  • the processor 1502 may be configured to execute computer-readable instructions stored in the memory 1504 to cause the UE 1500 to perform various functions of the present disclosure.
  • the memory 1504 may include volatile or non-volatile memory.
  • the memory 1504 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1502, cause the UE 1500 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such the memory 1504 or another type of memory.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • the processor 1502 and the memory 1504 coupled with the processor 1502 may be configured to cause the UE 1500 to perform one or more of the UE functions described herein (e.g., executing, by the processor 1502, instructions stored in the memory 1504) . Accordingly, the processor 1502 may support wireless communication at the UE 1500 in accordance with examples as disclosed herein.
  • the UE 1500 may be configured to support a means for receiving, from a network entity, a request message for parameters and UE conditions for AI/ML positioning.
  • the UE 1500 may be configured to support a means for determining a list of one or more supported or applicable functionalities and UE conditions.
  • the UE 1500 may be configured to support a means for transmitting a response message comprising the list of one or more supported or applicable functionalities and UE conditions.
  • the request message comprises a list of candidate parameters associated with the UE, and associated information for each candidate parameter.
  • the candidate parameters may include a supported functionality, a supported UE capability, an applicable functionality, or an applicable UE capability, or a combination thereof.
  • the associated information may include an identifier, or a prioritization assignment (e.g., an explicit priority indicator or an implicit priority indicator) , or a combination thereof.
  • the list of one or more supported or applicable functionalities and UE conditions may include a set of associated IDs.
  • each associated ID may be mapped to a UE supported functionality, a UE applicable functionality, a UE condition, or a network condition, or a combination thereof.
  • a respective unified applicable functionality of the set of unified applicable functionalities comprises a combination of at least one received UE condition, at least one network condition, and at least one applicable AI/ML functionality.
  • each unified applicable functionality of the set of unified applicable functionalities is mapped to an associated ID.
  • the list of one or more supported or applicable functionalities and UE conditions may include at least one dynamic UE condition.
  • the at least one dynamic UE condition may include one or more of: A) a PRS processing capability, B) a measurement capability, C) a number of supported samples, D) a total number of subsamples, E) a mapping of measured quantity to reported quantity value associated to a k-value, F) an area information in which AI/ML training or AI/ML inference is performed, G) PRU information, H) a LOS or NLOS indication, I) a requested area for AI/ML inference, J) a requested time period for AI/ML inference, or combinations thereof.
  • the list of one or more supported or applicable functionalities and UE conditions comprises at least one static UE condition.
  • the at least one static UE condition may include one or more of: A) a set of supported direct AI/ML positioning techniques, B) a set of supported assisted AI/ML positioning techniques, C) a set of supported non-AI/ML positioning techniques, D) support of broadcast of AI/ML positioning assistance data, E) support of reception of TRP beam antenna information, F) a set of supported TRP beam antenna angles, or combinations thereof.
  • the UE 1500 is configured to determine a change to an update to a parameters from an initial list of candidate parameters and transmit an update message indicating the updated parameter.
  • the updated parameter comprises one or more of: A) an updated supported functionality, B) an updated applicable functionality, C) an updated UE condition, D) an updated unified applicable functionality, E) an updated network condition, F) an updated network configuration, or a combination thereof.
  • the controller 1506 may manage input and output signals for the UE 1500.
  • the controller 1506 may also manage peripherals not integrated into the UE 1500.
  • the controller 1506 may utilize an operating system (OS) such as or other operating systems.
  • the controller 1506 may be implemented as part of the processor 1502.
  • the UE 1500 may include at least one transceiver 1508. In some other implementations, the UE 1500 may have more than one transceiver 1508.
  • the transceiver 1508 may represent a wireless transceiver.
  • the transceiver 1508 may include one or more receiver chains 1510, one or more transmitter chains 1512, or a combination thereof.
  • a receiver chain 1510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receiver chain 1510 may include one or more antennas for receiving the signal over the air or wireless medium.
  • the receiver chain 1510 may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receiver chain 1510 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receiver chain 1510 may include at least one decoder for decoding/processing the demodulated signal to receive the transmitted data.
  • a transmitter chain 1512 may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmitter chain 1512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmitter chain 1512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmitter chain 1512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
  • FIG. 16 illustrates an example of a processor 1600 in accordance with aspects of the present disclosure.
  • the processor 1600 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1600 may include a controller 1602 configured to perform various operations in accordance with examples as described herein.
  • the processor 1600 may optionally include at least one memory 1604, which may be, for example, an L1, or L2, or L3 cache. Additionally, or alternatively, the processor 1600 may optionally include one or more arithmetic-logic units (ALUs) 1606.
  • ALUs arithmetic-logic units
  • the processor 1600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1600) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 1602 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1600 to cause the processor 1600 to support various operations in accordance with examples as described herein.
  • the controller 1602 may operate as a control unit of the processor 1600, generating control signals that manage the operation of various components of the processor 1600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1604 and determine subsequent instruction (s) to be executed to cause the processor 1600 to support various operations in accordance with examples as described herein.
  • the controller 1602 may be configured to track memory address of instructions associated with the memory 1604.
  • the controller 1602 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1600 to cause the processor 1600 to support various operations in accordance with examples as described herein.
  • the controller 1602 may be configured to manage flow of data within the processor 1600.
  • the controller 1602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1600.
  • ALUs arithmetic logic units
  • the memory 1604 may include one or more caches (e.g., memory local to or included in the processor 1600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1604 may reside within or on a processor chipset (e.g., local to the processor 1600) . In some other implementations, the memory 1604 may reside external to the processor chipset (e.g., remote to the processor 1600) .
  • caches e.g., memory local to or included in the processor 1600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 1604 may reside within or on a processor chipset (e.g., local to the processor 1600) . In some other implementations, the memory 1604 may reside external to the processor chipset (e.g., remote to the processor 1600) .
  • the memory 1604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1600, cause the processor 1600 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the controller 1602 and/or the processor 1600 may be configured to execute computer-readable instructions stored in the memory 1604 to cause the processor 1600 to perform various functions.
  • the processor 1600 and/or the controller 1602 may be coupled with or to the memory 1604, the processor 1600, the controller 1602, and the memory 1604 may be configured to perform various functions described herein.
  • the processor 1600 may include multiple processors and the memory 1604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the one or more ALUs 1606 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 1606 may reside within or on a processor chipset (e.g., the processor 1600) .
  • the one or more ALUs 1606 may reside external to the processor chipset (e.g., the processor 1600) .
  • One or more ALUs 1606 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 1606 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 1606 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1606 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1606 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1606 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 1600 may support the functions of a UE, in accordance with examples as disclosed herein.
  • the processor 1600 may be configured to support a means for receiving, from a network entity, a request message for parameters and UE conditions for AI/ML positioning.
  • the processor 1600 may be configured to support a means for determining a list of one or more supported or applicable functionalities and UE conditions.
  • the processor 1600 may be configured to support a means for transmitting a response message comprising the list of one or more supported or applicable functionalities and UE conditions.
  • the processor 1600 may be configured to support a means for receiving a message to activate or deactivate a functionality of a set of unified applicable functionalities based at least in part on the response message.
  • the set of unified applicable functionalities comprises one or more functionalities to be activated or configured.
  • the processor 1600 is configured to receive an activation or configuration message comprising an indication of the one or more functionalities to be activated or configured.
  • the request message comprises a list of candidate parameters associated with the UE, and associated information for each candidate parameter.
  • the candidate parameters may include a supported functionality, a supported UE capability, an applicable functionality, or an applicable UE capability, or a combination thereof.
  • the associated information may include an identifier, or a prioritization assignment (e.g., an explicit priority indicator or an implicit priority indicator) , or a combination thereof.
  • the list of one or more supported or applicable functionalities and UE conditions may include a set of associated IDs.
  • each associated ID may be mapped to a UE supported functionality, a UE applicable functionality, a UE condition, or a network condition, or a combination thereof.
  • a respective unified applicable functionality of the set of unified applicable functionalities comprises a combination of at least one received UE condition, at least one network condition, and at least one applicable AI/ML functionality.
  • each unified applicable functionality of the set of unified applicable functionalities is mapped to an associated ID.
  • the list of one or more supported or applicable functionalities and UE conditions may include at least one dynamic UE condition.
  • the at least one dynamic UE condition may include one or more of: A) a PRS processing capability, B) a measurement capability, C) a number of supported samples, D) a total number of subsamples, E) a mapping of measured quantity to reported quantity value associated to a k-value, F) an area information in which AI/ML training or AI/ML inference is performed, G) PRU information, H) a LOS or NLOS indication, I) a requested area for AI/ML inference, J) a requested time period for AI/ML inference, or combinations thereof.
  • the list of one or more supported or applicable functionalities and UE conditions comprises at least one static UE condition.
  • the at least one static UE condition may include one or more of: A) a set of supported direct AI/ML positioning techniques, B) a set of supported assisted AI/ML positioning techniques, C) a set of supported non-AI/ML positioning techniques, D) support of broadcast of AI/ML positioning assistance data, E) support of reception of TRP beam antenna information, F) a set of supported TRP beam antenna angles, or combinations thereof.
  • the processor 1600 is configured to determine a change to an update to a parameters from an initial list of candidate parameters and transmit an update message indicating the updated parameter.
  • the updated parameter comprises one or more of: A) an updated supported functionality, B) an updated applicable functionality, C) an updated UE condition, D) an updated unified applicable functionality, E) an updated network condition, F) an updated network configuration, or a combination thereof.
  • the processor 1600 may support the functions of a network entity (e.g., an LMF, a location server, or a NWDAF) , in accordance with examples as disclosed herein.
  • the processor 1600 may be configured to support a means for transmitting, to a UE, a request message for parameters and UE conditions for AI/ML positioning.
  • the parameters may include functionality-based LCM parameters, such as a list of one or more supported or applicable functionalities and UE conditions.
  • the processor 1600 may be configured to support a means for receiving a response message comprising a list of one or more supported or applicable functionalities and UE conditions. In some embodiments, the processor 1600 is configured to provision one or more UE supported or applicable functionalities in response to the response message.
  • the processor 1600 may be configured to support a means for determining a set of unified applicable functionalities based at least in part on the list of one or more supported or applicable functionalities and UE conditions.
  • the processor 1600 is configured to transmit, to an access network, a second request message for configuration parameters and network conditions for a list of TRPs, and to receive a second response message comprising a list of TRP and configuration parameters.
  • the processor 1600 may be further configured to determine (e.g., based on the received list of UE applicable functionalities, UE conditions, network conditions, or combinations thereof) the unified applicable functionality to be activated or configured and an associated identifier for the selected/determined unified applicable functionality.
  • the set of unified applicable functionalities comprises one or more functionalities to be activated or configured.
  • the processor 1600 is configured to transmit an activation or configuration message comprising an indication of the one or more functionalities to be activated or configured.
  • the network entity comprises a location server, an LMF, or base station (e.g., gNB, TRP, or NG-RAN node) supporting one or more positioning configuration capabilities or location computation capabilities.
  • a location server e.g., an LMF, or base station (e.g., gNB, TRP, or NG-RAN node) supporting one or more positioning configuration capabilities or location computation capabilities.
  • base station e.g., gNB, TRP, or NG-RAN node
  • the request message comprises a list of candidate parameters associated with the UE, and associated information for each candidate parameter.
  • the candidate parameters may include a supported functionality, a supported UE capability, an applicable functionality, or an applicable UE capability, or a combination thereof.
  • the associated information may include an identifier, or a prioritization assignment (e.g., an explicit priority indicator or an implicit priority indicator) , or a combination thereof.
  • the list of one or more supported or applicable functionalities and UE conditions may include a set of associated IDs.
  • each associated ID may be mapped to a UE supported functionality, a UE applicable functionality, a UE condition, or a network condition, or a combination thereof.
  • the processor 1600 is configured to receive, from the UE, an update message indicating an update to a parameter from an initial list of candidate parameters.
  • the updated parameter comprises one or more of: A) an updated supported functionality, B) an updated applicable functionality, C) an updated UE condition, D) an updated unified applicable functionality, E) an updated network condition, F) an updated network configuration, or a combination thereof.
  • a respective unified applicable functionality of the set of unified applicable functionalities comprises a combination of at least one received UE condition, at least one network condition, and at least one applicable AI/ML functionality.
  • each unified applicable functionality of the set of unified applicable functionalities is mapped to an associated ID.
  • the list of one or more supported or applicable functionalities and UE conditions may include at least one dynamic UE condition.
  • the at least one dynamic UE condition may include one or more of: A) a PRS processing capability, B) a measurement capability, C) a number of supported samples, D) a total number of subsamples, E) a mapping of measured quantity to reported quantity value associated to a k-value, F) an area information in which AI/ML training or AI/ML inference is performed, G) PRU information, H) a LOS or NLOS indication, I) a requested area for AI/ML inference, J) a requested time period for AI/ML inference, or combinations thereof.
  • the list of one or more supported or applicable functionalities and UE conditions comprises at least one static UE condition.
  • the at least one static UE condition may include one or more of: A) a set of supported direct AI/ML positioning techniques, B) a set of supported assisted AI/ML positioning techniques, C) a set of supported non-AI/ML positioning techniques, D) support of broadcast of AI/ML positioning assistance data, E) support of reception of TRP beam antenna information, F) a set of supported TRP beam antenna angles, or combinations thereof.
  • FIG. 17 illustrates an example of a NE 1700 in accordance with aspects of the present disclosure.
  • the NE 1700 may include a processor 1702, a memory 1704, a controller 1706, and a transceiver 1708.
  • the processor 1702, the memory 1704, the controller 1706, or the transceiver 1708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
  • the processor 1702, the memory 1704, the controller 1706, or the transceiver 1708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • the processor 1702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof) .
  • the processor 1702 may be configured to operate the memory 1704.
  • the memory 1704 may be integrated into the processor 1702.
  • the processor 1702 may be configured to execute computer-readable instructions stored in the memory 1704 to cause the NE 1700 to perform various functions of the present disclosure.
  • the memory 1704 may include volatile or non-volatile memory.
  • the memory 1704 may store computer-readable, computer-executable code including instructions when executed by the processor 1702 cause the NE 1700 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such the memory 1704 or another type of memory.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • the processor 1702 and the memory 1704 coupled with the processor 1702 may be configured to cause the NE 1700 to perform one or more of the network entity functions described herein (e.g., executing, by the processor 1702, instructions stored in the memory 1704) .
  • the processor 1702 may support wireless communication at the NE 1700 in accordance with examples as disclosed herein.
  • the NE 1700 may be configured to support a means for transmitting, to a UE, a request message for parameters and UE conditions for AI/ML positioning.
  • the parameters may include functionality-based LCM parameters, such as a list of one or more supported or applicable functionalities and UE conditions.
  • the NE 1700 may be configured to support a means for receiving a response message comprising a list of one or more supported or applicable functionalities and UE conditions. In some embodiments, the NE 1700 is configured to provision one or more UE supported or applicable functionalities in response to the response message.
  • the NE 1700 may be configured to support a means for determining a set of unified applicable functionalities based at least in part on the list of one or more supported or applicable functionalities and UE conditions.
  • the NE 1700 is configured to transmit, to an access network, a second request message for configuration parameters and network conditions for a list of TRPs, and to receive a second response message comprising a list of TRP and configuration parameters.
  • the NE 1700 may be further configured to determine (e.g., based on the received list of UE applicable functionalities, UE conditions, network conditions, or combinations thereof) the unified applicable functionality to be activated or configured and an associated identifier for the selected/determined unified applicable functionality.
  • the set of unified applicable functionalities comprises one or more functionalities to be activated or configured.
  • the NE 1700 is configured to transmit an activation or configuration message comprising an indication of the one or more functionalities to be activated or configured.
  • the network entity comprises a location server, an LMF, or base station (e.g., gNB, TRP, or NG-RAN node) supporting one or more positioning configuration capabilities or location computation capabilities.
  • a location server e.g., an LMF, or base station (e.g., gNB, TRP, or NG-RAN node) supporting one or more positioning configuration capabilities or location computation capabilities.
  • base station e.g., gNB, TRP, or NG-RAN node
  • the request message comprises a list of candidate parameters associated with the UE, and associated information for each candidate parameter.
  • the candidate parameters may include a supported functionality, a supported UE capability, an applicable functionality, or an applicable UE capability, or a combination thereof.
  • the associated information may include an identifier, or a prioritization assignment (e.g., an explicit priority indicator or an implicit priority indicator) , or a combination thereof.
  • the list of one or more supported or applicable functionalities and UE conditions may include a set of associated IDs.
  • each associated ID may be mapped to a UE supported functionality, a UE applicable functionality, a UE condition, or a network condition, or a combination thereof.
  • the NE 1700 is configured to receive, from the UE, an update message indicating an update to a parameter from an initial list of candidate parameters.
  • the updated parameter comprises one or more of: A) an updated supported functionality, B) an updated applicable functionality, C) an updated UE condition, D) an updated unified applicable functionality, E) an updated network condition, F) an updated network configuration, or a combination thereof.
  • a respective unified applicable functionality of the set of unified applicable functionalities comprises a combination of at least one received UE condition, at least one network condition, and at least one applicable AI/ML functionality.
  • each unified applicable functionality of the set of unified applicable functionalities is mapped to an associated ID.
  • the list of one or more supported or applicable functionalities and UE conditions may include at least one dynamic UE condition.
  • the at least one dynamic UE condition may include one or more of: A) a PRS processing capability, B) a measurement capability, C) a number of supported samples, D) a total number of subsamples, E) a mapping of measured quantity to reported quantity value associated to a k-value, F) an area information in which AI/ML training or AI/ML inference is performed, G) PRU information, H) a LOS or NLOS indication, I) a requested area for AI/ML inference, J) a requested time period for AI/ML inference, or combinations thereof.
  • the list of one or more supported or applicable functionalities and UE conditions comprises at least one static UE condition.
  • the at least one static UE condition may include one or more of: A) a set of supported direct AI/ML positioning techniques, B) a set of supported assisted AI/ML positioning techniques, C) a set of supported non-AI/ML positioning techniques, D) support of broadcast of AI/ML positioning assistance data, E) support of reception of TRP beam antenna information, F) a set of supported TRP beam antenna angles, or combinations thereof.
  • the controller 1706 may manage input and output signals for the NE 1700.
  • the controller 1706 may also manage peripherals not integrated into the NE 1700.
  • the controller 1706 may utilize an operating system such as or other operating systems.
  • the controller 1706 may be implemented as part of the processor 1702.
  • the NE 1700 may include at least one transceiver 1708. In some other implementations, the NE 1700 may have more than one transceiver 1708.
  • the transceiver 1708 may represent a wireless transceiver.
  • the transceiver 1708 may include one or more receiver chains 1710, one or more transmitter chains 1712, or a combination thereof.
  • a receiver chain 1710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receiver chain 1710 may include one or more antennas for receiving the signal over the air or wireless medium.
  • the receiver chain 1710 may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receiver chain 1710 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receiver chain 1710 may include at least one decoder for decoding/processing the demodulated signal to receive the transmitted data.
  • a transmitter chain 1712 may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmitter chain 1712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmitter chain 1712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmitter chain 1712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
  • Figure 18 depicts one embodiment of a method 1800 in accordance with aspects of the present disclosure.
  • the operations of the method 1800 may be implemented by a NE as described herein.
  • the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
  • the method 1800 may include transmitting, to a UE, a request message for parameters and UE conditions for AI/ML positioning.
  • the operations of step 1802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1802 may be performed by a NE, as described with reference to Figure 17.
  • the method 1800 may include receiving a response message comprising a list of one or more supported or applicable functionalities and UE conditions.
  • the operations of step 1804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1804 may be performed by a NE, as described with reference to Figure 17.
  • the method 1800 may include determining a set of unified applicable functionalities based at least in part on the list of one or more supported or applicable functionalities and UE conditions.
  • the operations of step 1806 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1806 may be performed by a NE, as described with reference to Figure 17.
  • Figure 19 depicts one embodiment of a method 1900 in accordance with aspects of the present disclosure.
  • the operations of the method 1900 may be implemented by a UE as described herein.
  • the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.
  • the method 1900 may include receiving, from a network entity, a request message for parameters and UE conditions for AI/ML positioning.
  • the operations of step 1902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1902 may be performed by a UE, as described with reference to Figure 15.
  • the method 1900 may include determining a list of one or more supported or applicable functionalities and UE conditions.
  • the operations of step 1904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1904 may be performed by a UE, as described with reference to Figure 15.
  • the method 1900 may include transmitting a response message comprising the list of one or more supported or applicable functionalities and UE conditions.
  • the operations of step 1906 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1906 may be performed by a UE, as described with reference to Figure 15.
  • the method 1900 may include receiving a message to activate or deactivate a functionality of a set of unified applicable functionalities based at least in part on the response message.
  • the operations of step 1908 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of step 1908 may be performed by a UE, as described with reference to Figure 15.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent la transmission d'un message de demande pour des paramètres et des conditions d'UE pour un positionnement par intelligence artificielle et apprentissage automatique (IA/ML), et la réception d'un message de réponse comprenant une liste d'une ou de plusieurs fonctionnalités et conditions d'UE prises en charge ou applicables. Des aspects de la présente divulgation peuvent concerner la détermination d'un ensemble de fonctionnalités applicables unifiées, au moins en partie sur la base de la liste d'une ou de plusieurs fonctionnalités et conditions d'UE prises en charge ou applicables.
PCT/CN2024/125795 2024-10-18 2024-10-18 Détermination d'un ensemble de fonctionnalités applicables unifiées Pending WO2025189755A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/125795 WO2025189755A1 (fr) 2024-10-18 2024-10-18 Détermination d'un ensemble de fonctionnalités applicables unifiées

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/125795 WO2025189755A1 (fr) 2024-10-18 2024-10-18 Détermination d'un ensemble de fonctionnalités applicables unifiées

Publications (1)

Publication Number Publication Date
WO2025189755A1 true WO2025189755A1 (fr) 2025-09-18

Family

ID=97062713

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/125795 Pending WO2025189755A1 (fr) 2024-10-18 2024-10-18 Détermination d'un ensemble de fonctionnalités applicables unifiées

Country Status (1)

Country Link
WO (1) WO2025189755A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230362625A1 (en) * 2022-05-09 2023-11-09 Qualcomm Incorporated Updated artificial intelligence or machine learning capabilities reporting
WO2024151069A1 (fr) * 2023-01-11 2024-07-18 삼성전자 주식회사 Procédé et dispositif de gestion d'informations pour une application ia/ml dans un système de communication sans fil
CN118614087A (zh) * 2022-02-04 2024-09-06 联想（新加坡）私人有限公司 用于基于人工智能的定位的测量和报告
WO2024207397A1 (fr) * 2023-04-07 2024-10-10 Qualcomm Incorporated Validation de fonctionnalités associées à des opérations côté équipement utilisateur

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118614087A (zh) * 2022-02-04 2024-09-06 联想（新加坡）私人有限公司 用于基于人工智能的定位的测量和报告
US20230362625A1 (en) * 2022-05-09 2023-11-09 Qualcomm Incorporated Updated artificial intelligence or machine learning capabilities reporting
WO2024151069A1 (fr) * 2023-01-11 2024-07-18 삼성전자 주식회사 Procédé et dispositif de gestion d'informations pour une application ia/ml dans un système de communication sans fil
WO2024207397A1 (fr) * 2023-04-07 2024-10-10 Qualcomm Incorporated Validation de fonctionnalités associées à des opérations côté équipement utilisateur

Similar Documents

Publication Publication Date Title
US20240361421A1 (en) Controlling repeated requests from a user equipment (ue) for positioning assistance in a wireless network
JP2024502311A (ja) ネットワークにおける測位に関する能力の記憶
KR20240150430A (ko) 무선 감지를 위한 볼륨 관련 정보 표시
KR20240067886A (ko) 공동 포지셔닝 세션들에 대한 불연속 수신 (drx) 기반 앵커 사용자 장비 (ue) 선택
AU2023358099A1 (en) Combined one-to-many and many-to-one sidelink positioning
WO2024253753A1 (fr) Sélection de cellule pour positionnement basé sur l'externalisation ouverte
WO2024069439A1 (fr) Planification et traitement de ressources pour positionnement de liaison latérale
US20250063576A1 (en) Sidelink positioning assistance
US20250317704A1 (en) Context-aware navigation
WO2025189755A1 (fr) Détermination d'un ensemble de fonctionnalités applicables unifiées
WO2024173086A1 (fr) Sélection de nœud assistée par carte pour le positionnement et la détection de radiofréquence
EP4649326A1 (fr) Procédés et systèmes de sélection efficace de point d'ancrage de positionnement
WO2024153362A1 (fr) Mappage de priorité de signal de référence de positionnement de liaison latérale dans un système de communication sans fil
KR20250044652A (ko) 2 파트 포지셔닝 기준 신호(prs)
WO2025251655A1 (fr) Informations de réalité de terrain pour une procédure d'apprentissage automatique (ml) d'intelligence artificielle (ia)
US20250224233A1 (en) Context-aware navigation
US12140449B2 (en) Usage of transformed map data with limited third party knowledge
US20240276419A1 (en) Map information signaling for positioning and radio frequency sensing
US20250317888A1 (en) Core network assistance information for radio resource control (rrc) state transitions
US20250274894A1 (en) Signaling for digital twin and location server interactions in cellular networks
US20240146486A1 (en) Processing gap requesting and/or error reporting
KR20250162547A (ko) 실내 대 실외 디바이스들을 위한 포지셔닝 성능 최적화
EP4623321A1 (fr) Procédés et systèmes pour un moteur de positionnement multi-technologie en nuage
AU2024326275A1 (en) Sidelink positioning assistance
EP4666529A1 (fr) Aide au positionnement de liaison latérale

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24929203

Country of ref document: EP

Kind code of ref document: A1