WO2024153362A1 - Mapping sidelink positioning reference signal priority in a wireless communication system - Google Patents

Mapping sidelink positioning reference signal priority in a wireless communication system Download PDF

Info

Publication number
WO2024153362A1
WO2024153362A1 PCT/EP2023/081361 EP2023081361W WO2024153362A1 WO 2024153362 A1 WO2024153362 A1 WO 2024153362A1 EP 2023081361 W EP2023081361 W EP 2023081361W WO 2024153362 A1 WO2024153362 A1 WO 2024153362A1
Authority
WO
WIPO (PCT)
Prior art keywords
positioning
prs
mapping
priority
processor
Prior art date
Application number
PCT/EP2023/081361
Other languages
French (fr)
Inventor
Robin Rajan THOMAS
Hyung-Nam Choi
Dimitrios Karampatsis
Original Assignee
Lenovo (Singapore) Pte. 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 (Singapore) Pte. Ltd. filed Critical Lenovo (Singapore) Pte. Ltd.
Publication of WO2024153362A1 publication Critical patent/WO2024153362A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • mapping sidelink (SL) positioning reference signal (PRS) priority in a wireless communication system.
  • This document defines a user equipment (UE) for wireless communication, a processor for wireless communication, a network entity for wireless communication, and methods in a user equipment, processor and network entity.
  • 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 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)).
  • SL Positioning is intended to be applied for a variety of use-cases such as vehicle-to-everything (V2X), public safety, industrial Internet of things (IIoT) and commercial use cases.
  • V2X vehicle-to-everything
  • IIoT industrial Internet of things
  • the aim of SL positioning is to determine the absolute/relative position of a UE by using SL positioning methods such as SL round trip time (RTT)-type methods including single-sided and double-sided RTT, SL-angle of arrival (AoA) and SL-time difference on arrival (TDOA).
  • SL positioning will be based on new SL-PRS/s that are transmitted over the PC5 interface and will be supported in all coverage scenarios (i.e., in-coverage, partial coverage and out-of-coverage scenarios) and for PC5 -only-based and joint PC5-Uu-based operation scenarios.
  • SLPP sidelink positioning protocol
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, 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. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.
  • a user equipment for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL-PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmit one or more SL-PRS according to the one or more SL-PRS configurations.
  • SL sidelink
  • QoS quality of service
  • a method in a UE comprising: determining one or more SL positioning QoS requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL PRS configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting, based on the mapping, SL-PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmitting one or more SL-PRS according to the one or more SL-PRS configurations.
  • a processor for wireless communication comprising: at least one controller coupled with at least one memory and configured to cause the processor to: input one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL-PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and output one or more SL- PRS according to the one or more SL-PRS configurations.
  • SL sidelink
  • QoS quality of service
  • PRS SL positioning reference signal
  • a method in a processor comprising: inputting one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and outputting one or more SL PRS according to the one or more SL PRS configurations.
  • SL sidelink
  • QoS quality of service
  • a network entity for wireless communication comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: determine a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values; and transmit the mapping (which may be in the form of mapping information) to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
  • SL sidelink
  • QoS Quality of Service
  • PRS SL positioning reference signal
  • the mapping/mapping information may further comprise of a table or index or vector of (pre-)defined SL PRS priority to SL positioning QoS parameters, or one or more enumerated index values corresponding to one or more (pre-)defined SL PRS priority to SL positioning QoS parameters.
  • a method in a network entity comprising: determining a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values; and transmitting the mapping to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
  • SL sidelink
  • QoS Quality of Service
  • PRS SL positioning reference signal
  • Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
  • Figure 2 illustrates an example of NR beam-based positioning in accordance with aspects of the present disclosure.
  • Figure 3 illustrates an example of absolute and relative positioning scenarios in accordance with aspects of the present disclosure.
  • Figure 4 illustrates an example of the Multi-Cell RTT procedure in accordance with aspects of the present disclosure.
  • Figure 5 illustrates an example of relative range estimation using the existing single gNB RTT positioning framework in accordance with aspects of the present disclosure.
  • Figure 6 illustrates an example of a procedure to enable a UE to obtain SL positioning/ranging location results, in accordance with aspects of the present disclosure.
  • Figure 7 illustrates an example of a procedure to estimate the relative locations or distances and/or directions between UEs, in accordance with aspects of the present disclosure.
  • Figure 8 illustrates an example of a procedure to estimate the relative locations or distances and/or directions between UEs, in accordance with aspects of the present disclosure.
  • Figure 9 illustrates an example of SL PRS priority mapping to SL positioning QoS procedures, in accordance with aspects of the present disclosure.
  • FIG. 10 illustrates an example of a user equipment (UE) 1000 in accordance with aspects of the present disclosure.
  • Figure 11 illustrates an example of a processor 1100 in accordance with aspects of the present disclosure.
  • Figure 12 illustrates an example of a network equipment (NE) 1200 in accordance with aspects of the present disclosure.
  • Figure 13 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.
  • Figure 14 illustrates a flowchart of a method performed by a processor in accordance with aspects of the present disclosure.
  • Figure 15 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.
  • Priority has been defined as a key parameter in SL communications as well as for exchanging SL Positioning messages in order to ascertain the urgency of which signals/packets to transmit from a particular UE.
  • Priority of a SL transmission also assists in limiting the congestion control of a SL resource pool, which is especially beneficial to manage the congest! on/traffic load of a SL Communication or Positioning resource pool.
  • the SL priority parameter is used throughout the SL communication stack including layer- 1, layer-2 and higher-layers (above layer-2) and is derived from the standardized PQI table, which is applicable for SL packet/data transmissions.
  • SL Positioning introduces the transmission of SL PRS for the purposes of determining a target-UE’s absolute/relative position/ranging for distance/ranging for direction.
  • An SL PRS resource is a pseudo-random sequence that is mapped to time-frequency resources (pairs of OFDM symbol, subcarrier) within a slot of a radio frame used for SL PRS transmission.
  • Multiple SL PRS resources can be configured within an SL BWP by means of a number of resource pools.
  • An SL PRS resource pool can be configured as a shared resource pool or as a dedicated resource pool.
  • a shared resource pool can be used for transmission of both SL PRS and PSSCH (SL data or SL-SCH data) whereas a dedicated resource pool can be used only for transmission of SL PRS.
  • PSSCH SL data or SL-SCH data
  • a dedicated resource pool can be used only for transmission of SL PRS.
  • resource allocation of SL PRS two schemes are supported depending on the coverage scenario.
  • Scheme 1 refers to network-controlled SL PRS resource allocation where the gNB manages and schedules the transmission of SL PRS resources.
  • a UE that requires to transmit SL PRS sends a request for specific SL PRS resource character! stic(s)/SL PRS resource configuration(s) to the gNB and receives an SL PRS resource allocation signaling from the gNB through a dynamic grant (provided via DCI), configured grant type 1 (provided via RRC) or configured grant type 2 (provided via PDCCH).
  • the request from the UE may be sent to gNB via L2 MAC CE or RRC message.
  • Scheme 2 refers to UE autonomous SL PRS resource allocation where the UE autonomously selects the SL PRS resources for transmission.
  • the UE firstly defines a selection window (consisting of number of slots) and identifies candidate SL PRS resources within the selection window. Afterwards, the UE senses the identified candidate SL PRS resources during a defined sensing window (consisting of number of slots) to determine which of the SL PRS resources are available. Finally, the UE selects randomly an SL PRS resource among the set of available SL PRS resources.
  • SL PRS transmission can be triggered either by the UE itself or a UE-A can request a UE-B to transmit SL PRS (either by LI SCI or L2 MAC CE).
  • the SL PRS priority will be taken as key parameter into account for selecting SL PRS resources. It has also been determined that 8 priority levels for SL PRS priority are to be defined, which is the same as the number of priority levels for SL-SCH (applicable for SL data transmissions). However, the problem of how to map these priority levels to SL Positioning QoS has not been addressed yet since the prior art assumes that the priority levels are defined based on the V2X/ProSe service type. In order to avoid UE implementations that assign arbitrarily high priorities to SL PRS transmissions, a standardized mapping of SL PRS priority levels to SL Positioning QoS associated to a Location Service (LCS) request is necessary.
  • LCS Location Service
  • the disclosure herein presents systems, apparatuses and methods for unifying the mapping between SL PRS priority and the desired SL Positioning QoS based on the received/triggered LCS request (e.g, SL-MT-LR or SL-MO- LR).
  • the embodiments presented herein aim to address the issue that currently presents itself with SL PRS transmission priority, wherein there is currently no mechanism that maps 8 levels of priority to a given SL Positioning QoS contained within an LCS request.
  • Such a mapping has to be configured or pre-configured to a UE in order for the UE to assign a specified priority for requesting or selecting a particular SL PRS transmission within a resource pool that is configured to transmit SL PRS.
  • This present disclosure details solutions for mapping the SL PRS priority as a function of the SL Positioning QoS according to different configuration scenarios.
  • Methods are provided to describe various mechanisms to map the SL PRS priority to different SL Positioning QoS parameters.
  • methods are provided to configure (i.e., preconfigure or configure) a consolidated SL PRS priority mapping table.
  • methods are provided to enable the procedures to map the SL PRS priority with the received SL Positioning QoS at the UE/device.
  • a positioning-related reference signal may be referred to as a reference signal used for positioning procedures/purposes in order to estimate a target-UE’s location, e.g., PRS, or based on existing reference signals such as CSLRS or SRS; a target-UE may be referred to as the device/entity to be localized/positioned.
  • PRS may refer to any signal such as a reference signal, which may or may not be used primarily for positioning.
  • any reference made to position/location information/estimates may refer to either an absolute position, relative position with respect to another node/entity, ranging in terms of distance, ranging in terms of direction or combination thereof.
  • the precision required for location services can be described using a range of values that indicate the typical level of accuracy required for a specific application, which in turn affects the SL PRS configuration required to achieve the said accuracy, e.g., in terms of comb-size including number of symbols and Resource element offset, bandwidth, and so forth.
  • Various services have distinct demands when it comes to positioning accuracy. This range can extend from several meters (for navigation services) to potentially several kilometers (for fleet management).
  • 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.
  • 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 NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network.
  • 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 radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (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 (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.
  • LoT Internet-of-Things
  • LoE 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., SI, 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, location services, 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)) or a control and user plane entity, e.g., Location Management Function (LMF), that is responsible for providing location services.
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • LMF Location Management 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 SI, 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 subcarrier spacing e.g., 15 kHz
  • 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 l 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., OFDM symbols).
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot may include 14 symbols.
  • 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 FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz).
  • FR1 410 MHz - 7.125 GHz
  • FR2 24.25 GHz - 52.6 GHz
  • FR3 7.125 GHz - 24.25 GHz
  • FR4 (52.6 GHz - 114.25 GHz
  • FR4a or FR4-1 52.6 GHz - 71 GHz
  • FR5 114.25 GHz - 300 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).
  • NR positioning based on NR Uu signals and SA architecture was first specified in 3GPP Rel-16.
  • the targeted use cases also included commercial and regulatory (emergency services) scenarios as in 3GPP Rel-15.
  • the performance requirements as discussed in the 3GPP TR 38.855 titled “Study on NR positioning support (Release 16) ”, are provided in Table 1.
  • 3 GPP Rel-17 Positioning has recently defined the positioning performance requirements for Commercial and IIoT use cases in 3GPP TR 38.857, titled “Study on NR Positioning Enhancements (Release 17) ” . These requirements are provided in Table 2.
  • FIG. 2 illustrates an example 200 of NR beam-based positioning in accordance with aspects of the present disclosure.
  • the example 200 shows a first gNB/TRP 210 illustrated as ‘gNB 1-TRP 1’.
  • the first gNB/TRP 210 is shown with a plurality of beams 211 having a Resource Set ID#0.
  • the first gNB/TRP 210 is shown with a plurality of beams 212 having a Resource Set ID#1.
  • Each beam in the pluralities of beams 211, 212 may represent DL-PRS resources.
  • a second gNB/TRP 220 is also shown, illustrated as ‘gNB 2-TRP 1’.
  • the second gNB/TRP 220 also comprises a plurality of beams 221 having a Resource Set ID#0 and a plurality of beams 222 having a Resource Set ID#1. Again, each beam in the plurality of beams 221, 222 may represent DL-PRS resources.
  • a third gNB/TRP 230 is also shown, illustrated as ‘Reference/serving gNB 3- TRP1’.
  • the third gNB/TRP 230 also comprises a plurality of beams 231 having a Resource Set ID#0 and a plurality of beams 232 having a Resource Set ID#1. Again, each beam in the plurality of beams 231, 232 may represent DL-PRS resources.
  • a location server/LMF 240 is also shown.
  • the first gNB/TRP 210, second gNB/TRP 220 and third gNB/TRP all interface with the location server/LMF 240 using NRPPa.
  • the PRS can be transmitted by different base stations (serving and neighboring) 210, 220, 230 using narrow beams 211, 212, 221, 222, 231, 232 over FR1 and FR2 as illustrated in Figure 2, which is relatively different when compared to LTE where the PRS was transmitted across the whole cell.
  • the PRS can be locally associated with a PRS Resource ID and Resource Set ID for a base station (TRP) 210, 220, 230.
  • UE positioning measurements such as Reference Signal Time Difference (RSTD) and PRS RSRP measurements are made between 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.
  • RSTD Reference Signal Time Difference
  • PRS RSRP measurements are made between 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.
  • RSTD Reference Signal Time Difference
  • PRS RSRP measurements are made between 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.
  • RSTD Reference Signal Time Difference
  • PRS RSRP measurements are made between 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.
  • RSTD Reference Signal Time Difference
  • RAT-dependent positioning techniques involve the 3 GPP RAT and core network entities to perform the position estimation of the UE, which are differentiated from RAT-independent positioning techniques which rely on GNSS, IMU sensor, WLAN and Bluetooth technologies for performing target device (UE) positioning.
  • Figure 3 illustrates an example 300 of absolute and relative positioning scenarios as defined in the system architectural (stage 1) study reported in 3 GPP TR 22.832, titled “Study on enhancements for cyber-physical control applications in vertical domains”.
  • the example 300 shows Relative Positioning, variable coordinate system 310; Relative Positioning, variable and moving coordinate system 320; and Absolute Positioning, fixed coordinate systems 330.
  • relative positioning may be performed between a UE 311 and 5G positioning nodes (i.e., gNB 1 312) within 10m of each other (see 3GPP TS 22.261). Furthermore, relative positioning may be performed between two UEs 313, 314 that are within 10m of each other (see 3 GPP TS 22.261). The vertical location of a UE3 315 is shown as being provided in terms of relative height/depth to local ground (see 3GPP TS 22.071).
  • the relative lateral position accuracy may be 0.1m between UEs supporting V2X application (see 3GPP TS 22.186).
  • the relative longitudinal position accuracy may be less than 0.5m for UEs supporting V2X application for platooning in proximity (see 3GPP TS 22.186).
  • the example 300 also shows an out of coverage scenario 340 wherein positioning information for a UE 341 that is out of coverage of the network is obtained relative to other UEs 342 that are in proximity or in coverage of the network (see 3GPP TS 22.104).
  • the DL-TDOA positioning method makes use of the DL RSTD (and optionally DL PRS RSRP) of downlink signals received from multiple TPs, at the UE.
  • the UE 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 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.
  • the UE 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 in relation to the neighboring TPs.
  • the Multi-RTT positioning method makes use of the UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs, measured by the UE and the measured gNB Rx-Tx measurements and UL SRS-RSRP at multiple TRPs of uplink signals transmitted from UE.
  • the UE 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 RTT at the positioning server which are used to estimate the location of the UE.
  • FIG. 4 illustrates an example 400 of the Multi-Cell RTT procedure in accordance with aspects of the present disclosure.
  • the example 400 shows UE Tx UL-SRS beginning at a time tO; gNB Rx UL-SRS beginning at a time tl; gNB Tx DL-PRS beginning at a time t2; and UE Rx DL-PRS beginning at a time t4.
  • the time period ‘A’ is shown as being equal to the difference between t3 and tO.
  • the time period ‘B’ is shown as being equal to the difference between t2 and tl.
  • the RTT is shown as being equal to A minus B.
  • FIG. 5 illustrates an example 500 of relative range estimation using the existing single gNB RTT positioning framework in accordance with aspects of the present disclosure.
  • the example 500 shows a target UE1 510, a target UE2 520, a target UE3 530, a gNB 540 and an LMF 550.
  • the UEs 510, 520, 530 communicate with the gNB 540 using DL-PRS and UL-SRS.
  • the LMF 550 determines the distance between the gNB 540 and UE 510, 520, 530, as being equal to the speed of light multiplied by half of the round trip time (RTT). Multi-RTT can be used to obtain an absolute location. Relative range may be calculated based on absolute positions.
  • the example 500 is an implementation-based approach to compute the relative distance between two UEs. This approach is high in latency and is not an efficient method in terms of procedures and signalling overhead.
  • Enhanced Cell ID (CID) positioning method the position of an UE is estimated with the knowledge of its serving ng-eNB, gNB and cell, and is based on LTE signals.
  • the information about the serving ng-eNB, gNB and cell may be obtained by paging, registration, or other methods.
  • NR Enhanced Cell ID (NR E-CID) positioning 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.
  • NR E-CID positioning may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE 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 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 UL RTOA (and optionally
  • the RPs measure the UL RTOA (and optionally UL SRS-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 estimate the location of the UE.
  • the UL AoA positioning method makes use of the measured azimuth and the zenith of arrival at multiple RPs of uplink signals transmitted from an UE.
  • the RPs measure A-AoA and 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.
  • FIG. 6 illustrates an example 600 of a procedure to enable a UE to obtain SL positioning/ranging location results using one or more other UEs with the assistance of an LMF in a serving PLMN for the UE, in accordance with aspects of the present disclosure.
  • the Ranging/SL Positioning location results referred to may include absolute locations, relative locations or distances and directions, depending on the service request.
  • the Target UE decides to initiate the SL-MO-LR procedure, it includes one or multiple SL reference UE(s) / Located UE (s) in the service request. See the 3 GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” for more information on how this generic procedure can be used.
  • the example 600 shows a UE1 630, a plurality of UEs UE2 640-UEn 645, an AMF 650, an LMF 660, a PCF 670, a GMLC 680 and a NEF/AF or LCS Client 690.
  • the various message flows 601-623 shown in the example 600 will now be described.
  • UE1 630 is in coverage and registered with a serving PLMN.
  • UEs 2 to n 640, 645 may or may not be in coverage and, if in coverage, may or may not be registered with the same serving PLMN as UE1 630.
  • a first step 601 the procedures and signalling specified in clause 6.2 of the 3 GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” may be used to provision the Ranging/SL positioning service authorization and policy/parameter provisioning to UEs 1 to n 630, 640, 645, when in coverage. This is shown as, Ranging/SL positioning service authorization and policy/parameter provisioning [0084] If indication of UE-only operation is received, procedures of Ranging/Sidelink Positioning control as defined in clause 6.8 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” is performed.
  • UE discovery is performed for Ranging/SL positioning as specified in clause 6.4 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” . This is shown as ‘UE discovery If UE1 630 is the target UE, UE1 630 discovers UEs 2 to n 640, 645.
  • the target UE i.e., one of the UEs 2 to n 640, 645
  • the target UE i.e., one of the UEs 2 to n 640, 645
  • a further step 603 secure groupcast and/or unicast links are established between UEs 1 to n 630, 640, 645 as defined in clause 5.3 of the 3 GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” .
  • This is to enable UE1 630 to exchange Ranging and Sidelink Positioning Protocol (RSPP) messages over PC5-U reference point with each of UEs 2 to n 640, 645 and possibly enabling UEs 2 to n 640, 645 to exchange RSPP over PC5-U between each other.
  • RSPP Ranging and Sidelink Positioning Protocol
  • UE1 630 and UEs 2 to n 640, 645 may communicate over PC5 for authorization of Ranging/SL positioning and receiving QoS parameters if needed.
  • Each of UEs 630, 640, 645 verifies that Ranging/SL positioning is permitted, including whether Ranging/SL positioning results may be transferred to an LCS Client or AF 690 if this is used, according to any service authorization and policy/parameter provisioning received at step 601.
  • QoS requirements for the Ranging/SL positioning may be also provided based on QoS requirements in the service request. This is shown as, ’notify and verify ranging/SL positioning
  • UE1 630 may obtain the Sidelink positioning capabilities of UEs 2 to n 640, 645 using the groupcast and/or unicast links established in step 603. This is shown as, ‘Capability Exchange [0089]
  • the steps 604 and 605 may be performed to transfer the information of UEs which are not served by the LMF 660. It should be noted that UE2-UEn 640, 645 is not assumed to be served by the same LMF 660 serving UE1 630.
  • the target UE determines SL-MO-LR is to be performed. If UE1 630 is the Located UE (i.e., when the target UE is one of UE2-UEn 640, 645, and does not have NAS connection), the target UE initiates a SL-MO-LR service request to UE1 630. This is shown as, ‘Determine SL-MO-LR
  • UE1 630 instigates a UE triggered Service Request in order to establish a signalling connection with the serving AMF 650 of UE1 630. This is shown as, ‘UE triggered service request’.
  • UE1 630 sends a supplementary services SL-MO-LR request to the serving AMF 650 in an UL NAS TRANSPORT message.
  • the SL-MO-LR request indicates the other UEs 2 to n 640, 645 (using application layer ID and/or GPSI), indicates any assistance data needed, indicates whether location calculation assistance is needed, and indicates whether location results should be transferred to an LCS client or AF 690.
  • the message shall include the identity of the LCS client or the AF 690 and may include the address of the GMLC 680 through which the LCS client or AF (via NEF) 690 should be accessed.
  • a Service Type indicates which MO-LR service of the LCS Client 690 is requested by the UE may be included.
  • the preferred type of Sidelink positioning/ranging location results e.g., absolute locations, relative locations or distances and directions between pairs of UEs 630, 640, 645) and the required QoS are included.
  • the supplementary services SL-MO-LR request includes an indication that one of UE2-UEn 640, 645 is the target UE instead of UE1 630. This is shown as, ‘UL NAS TRANSPORT (SL-MO-LR Request)
  • the serving AMF 650 selects an LMF 660 serving UE1 630 (e.g., an LMF ⁇ 660 that supports Sidelink positioning/ranging) and sends an Nlmf Location DetermineLocation service operation towards the LMF 660 with the information from the SL-MO-LR Request.
  • the service operation includes a LCS Correlation identifier. This is illustrated as, ‘Nlmf Location DetermineLocation Request’ .
  • the LMF 660 sends a request to UE1 630 for the capabilities of UEs 1 to n 630, 640, 645. It should be noted that UE2-UEn 640, 645 is not assumed to be served by the same LMF 660 serving UE1 630. This is illustrated as, ‘Capabilities Request for UEs 1 to n ’.
  • the UE1 630 returns its capabilities to the LMF 660.
  • UE1 630 may additionally return the capabilities of the UEs obtained at step 605 if requested by the LMF 660 at step 610. This is illustrated as, ‘Capabilities Response for UEs 1 to n ’.
  • UE1 630 may send a request for specific assistance data to the LMF 660. This is illustrated as, ‘sharing Assistance data for UEs ’.
  • LMF 660 sends the requested assistance data to UE1 630, and UE1 630 forwards the assistance data received from LMF 660 to UE2-UEn 640, 645.
  • the assistance data may assist UEs 1 to n 630, 640, 645 to obtain Sidelink location measurements at step 615 and/or may assist UE1 630 to calculate Sidelink positioning/ranging location results at step 616.
  • the step 613 is also illustrated as, ‘sharing Assistance data for UEs ’.
  • steps 610 and 611 can be omitted if UE1 630 includes a message containing the capabilities of UEs 1 to n 630, 640, 645 in the SL-MO-LR request at step 608.
  • Step 612 can be omitted if UE1 630 includes a message containing the request for specific assistance data in the SL-MO-LR request at step 608.
  • a further step 614 if the SL-MO-LR request at step 608 indicated location calculation assistance is needed and/or indicated transfer of Sidelink positioning/ranging location results to an LCS Client or AF 690, the LMF 660 sends a request for location information to UE1 630 and may also send a request for location information to UE2-UEn 640, 645 if it is served by the LMF 660. If LMF 660 determines to apply UE based SL Positioning, LMF 660 includes in the request the indication of UE based SL Positioning. LMF 660 may also provide the list of candidate Located UE(s), if absolute location is requested at step 608. If scheduled location time is received at step 614, LMF 660 may include a scheduled location time. This step 614 is shown as, ‘Request Location Information for UEs 1 to n ’.
  • UE1 630 instigates a Sidelink positioning/ranging procedure among UEs 1 to n 630, 640, 645 in which UEs 1 to n 630, 640, 645 obtain Sidelink location measurements and UEs 2 to n 640, 645 transfer their Sidelink location measurements to UE 1 630 and/or to the LMF 660 (depending on the assistance requested). If scheduled location time is received at step 614, Sidelink positioning/ranging is performed at the scheduled location time. This step 615 is shown as, ‘Sidelink positioning/ranging procedure ’.
  • Target UEs absolute location information is required at step 608 and if absolute location of Located UE(s) is not available, the Target UE sends a request to the Located UE(s) to trigger 5GC-MO-LR procedure to let the Located UE(s) acquire their own absolute location.
  • the QoS requirement received at step 608 is included in the request, which is used to derive the QoS for Located UE(s) positioning. This is shown as, ‘UE1... UEn 5GC-MO-LR procedures ’.
  • a further step 617 if LMF 660 determines to use UE based calculation, at least one of UEl-UEn 630, 640, 645 calculates Sidelink positioning/ranging location results based on the Sidelink location measurements obtained at step 615 and possibly using assistance data received at step 613.
  • the Sidelink positioning/ranging location results can include absolute locations, relative locations or ranges and directions related to the UEs 1 to n 630, 640, 645. This is shown as, ‘Calculate Location Results for UEs 1 to n ’.
  • UE1 630 if UE1 630 received a request for location information at step 614, UE1 630 sends a response to the LMF 660 and includes the Sidelink location measurements obtained at step 615, the Sidelink positioning/ranging location results obtained at step 617 if step 617 was performed, or Located UEs absolute location obtained at step 616. This is shown as, ‘Provide Location Information for UEs 1 to n ’.
  • LMF 660 can either retrieved the location of the Located UE(s) locally or triggers 5GC-MT-LR procedure to the GMLC 680 to acquire the absolute location of the Located UE(s) using Application Layer ID or GPSI of the Located UE(s).
  • LMF 660 includes the QoS requirement received at step 608 in the request, which is used to derive the QoS for Located UE(s) positioning. If scheduled location time is used, LMF 660 includes the scheduled location time in the request to GMLC 680. This is shown as, ‘UE1... UEn TGC-MT-LR procedures
  • the LMF 660 calculates Sidelink positioning/ranging location results for UEs 1 to n 630, 640, 645 from the Sidelink location measurements received at step 618 and absolute location of Located UE(s) at step 619.
  • the Sidelink positioning/ranging location results can include absolute locations, relative locations or ranges and directions related to the UEs 1 to n 630, 640, 645, depending on the location request received in step 608. This is illustrated as, ‘Calculate Location Results for UEs 1 to n
  • Nlmf Location DetermineLocation service operation response to the AMF 650 and includes the Sidelink positioning/ranging location results received at step 618 or calculated at step 620. This is shown as, ‘Nlmf Location DetermineLocation Response
  • a further step 622 if Sidelink positioning/ranging location results were received at step 621, the AMF 650 performs steps 607-612 of clause 6.2 of the 3GPP Technical Specification 23.273 titled “5G System (5GS) Location Services (LCS) Stage 2 (Release 18) ” to send the Sidelink positioning/ranging location results to the GMLC 680 and to an AF or LCS Client 690 if this was requested at step 608.
  • the Sidelink positioning/ranging location results include the identities for the respective UEs 1 to n 630, 640, 645 received at step 608. This is shown as, ‘Transfer Location Results to GMLC and optionally to AF or LCS Client
  • sending location results and global identities for UEs 1 to n 630, 640, 645 to an AF or LCS Client 690 may require privacy verification from UEs 1 to n 630, 640, 645 and/or from the HPLMNs of UEs 1 to n 630, 640, 645.
  • the LMF 660 returns a supplementary services SL-MO-LR response to UE1 630 in a DL NAS TRANSPORT message and includes any Sidelink positioning/ranging location results calculated at step 620 if step 620 was performed.
  • UE1 630 may transfer the Sidelink positioning/ranging location results to the target UE.
  • Figure 7 illustrates an example 700 of a procedure to estimate the relative locations or distances and/or directions between UEs, in accordance with aspects of the present disclosure.
  • the example 700 shows a UE1 730, a plurality of UEs denoted UE2-UEn 740, 745, an AMF 750, an NG-RAN 755, an LMF 760, a VGMLC 780, a HGMLC 785, a NEF/AF or LCS Client 790 and a UDM 795.
  • the example 700 shows a procedure to enable an LCS Client or AF 790 to obtain Ranging/Sidelink Positioning location results for a group of n UEs (n ⁇ 2), i.e., UE1, UE2, ..., UEn 730, 740, 745.
  • the Ranging/Sidelink Positioning location results may include absolute locations, relative locations or ranges and directions related to the UEs 730, 740, 745, based on the service request.
  • the procedure for periodic and triggered SL-MT-LR is defined in clause 6.20.4 of the 3GPP TS 23.273, titled “5G System (5GS) Location Services (LCS) ”, Stage 2 (Release 18).
  • the various message flows 701-720 will now be discussed. As a precondition, at least one of the n UEs 730, 740, 745 is in coverage and registered with a serving PLMN.
  • a first step 701 the LCS Client or the AF (via NEF) 790 sends an LCS service request to the (H)GMLC 785 for Ranging/Sidelink Positioning location results for the n UEs 730, 740, 745 which may each be identified by a GPSI or a SUPI.
  • the request may include the required QoS, the required location results (e.g., absolute locations, relative locations or distances and/or directions related to the UEs 730, 740, 745), the SL reference UE(s) in case of relative locations, distance, or direction.
  • the (H)GMLC 785 or NEF 790 authorizes the LCS Client or the AF 790 for the usage of the LCS service.
  • the authorization fails, the remaining steps are skipped and the (H)GMLC 785 or NEF 790 responds to the LCS Client or the AF 790 with the failure of the service authorization. This is shown as, ‘LCS Service Request’.
  • an Application Layer ID shall be included for each of the n UEs 730, 740, 745 to enable discovery of the UEs 730, 740, 745 at step 712.
  • the (H)GMLC 785 invokes a Nudm SDM Get service operation towards the UDM 795 of each of the n UEs 730, 740, 745 to get the privacy settings of the UE identified by its GPSI or SUPI.
  • the UDM 795 returns the UE Privacy setting of the UE.
  • the (H)GMLC 785 checks the UE LCS privacy profile. This is illustrated as, ‘Nudm SDM Get
  • the (H)GMLC 785 invokes a Nudm UECM Get service operation towards the UDM 795 of each of the n UEs 730, 740, 745 (for which GPSI or SUPI is available), one at a time, using the GPSI or SUPI of each UE 730, 740, 745.
  • the (H)GMLC 785 selects the UE 730, 740, 745 (e.g., which is treated as UE1 in following steps) that initiates the Ranging/SL Positioning and selects the corresponding serving AMF 750. This is illustrated as, ‘Nudm UECM Get’ .
  • the UDM 795 is aware of the serving AMF 750 address as UE registration on an AMF 750 as defined in clause 4.2.2.2.2 of 3GPP TS 23.502.
  • the UDM 795 is aware of a serving (V)GMLC 780 address at UE registration on an AMF 750 as defined in clause 4.2.2.2.2 of 3GPP TS 23.502.
  • the (H)GMLC 785 may receive an address of a (V)GMLC 780 (together with the network address of the current serving AMF 750) from the UDM 795 in step 703, otherwise, the (H)GMLC 785 may use the NRF service in the (H)PLMN to select an available (V)GMLC 780 in the (V)PLMN, based on the (V)PLMN identification contained in the AMF 750 address received in step 703.
  • the (H)GMLC 785 then sends the location request to the (V)GMLC 780 by invoking the Ngmlc Location ProvideLocation service operation towards the (V)GMLC 780.
  • the (H)GMLC 785 sends the location service request message to the serving AMF 750. In this case, step 704 is skipped.
  • the (H)-GMLC 785 also provides the LCS client type of AF 790, if received in step 701, or LCS client type of LCS client 790 and other attributes to be sent to AMF 750 in step 705.
  • the step 704 is shown as, ‘Ngmlc Location ProvideLocationRequest’.
  • the (V)GMLC 780 first authorizes that the location request is allowed from this (H)GMLC 785, PLMN or from this country. If not, an error response is returned.
  • the (H)GMLC 785 or (V)GMLC 780 invokes the Namf Location ProvidePositioninglnfo service operation towards the AMF 750 serving UE1 730 to request Sidelink positioning/ranging location results of the n UEs 730, 740, 745.
  • the service operation includes the SUPI of UE1 730, Application layer IDs of the UEs 730, 740, 745, the client type and may include the required LCS QoS, the required location results (e.g., relative locations or ranges and directions related to the UEs) and other attributes as received or determined in step 701. This is shown as, ‘Namf Location ProvidePositioninglnfo Request
  • a further step 706 if UE1 730 is in CM-IDLE state, the AMF 750 initiates a network triggered Service Request procedure to establish a signalling connection with UE1 730. This is shown as, ‘Network Triggered Service Request’.
  • step 707-708 if the indicator of privacy check indicates an action is needed, then same operation as that of step 707-708 of clause 6.1.2 of the 3GPP Technical Specification 23.273 titled “5G System (5GS) Location Services (LCS) Stage 2 (Release 18) ” is carried out.
  • 5GS 5G System
  • LCS Location Services
  • the serving AMF 750 selects an LMF 760 serving UE1 730 (e.g., an LMF 760 that supports Ranging/Sidelink Positioning) and sends an Nlmf Location DetermineLocation service operation towards the LMF 760 with the information received at step 705 e.g., required location results (e.g., relative locations or ranges and directions between pairs of UEs), SL reference UE(s) in case of relative locations, Application layer IDs of the UEs if received in step 705.
  • the service operation includes a LCS Correlation identifier. This is illustrated as, ‘Nlmf Location DetermineLocation Request
  • the LMF 760 sends an SL-MT-LR request to the serving AMF s750 as a supplementary services message, using the Namf_Communication_NlN2MessageTransfer service operation, and the session ID parameter is set to the LCS Correlation identifier. This is illustrated as,
  • the SL-MT-LR request may include the application layer IDs of the other UEs 2 to n 740, 745, the types of required location results (e.g., relative locations or distances and/or directions) and SL reference UE(s) in case of relative locations.
  • the serving AMF 750 forwards the SL-MT-LR request and a Routing identifier equal to the LCS Correlation identifier to UE1 730 using a DL NAS TRANSPORT message. This is illustrated as, ‘DL NAS TRANSPORT (SL-MT-LR Request, Routing ID)
  • UE1 730 attempts to discover the other UE 2 to n 740, 745 using their Application Layer IDs if not already discovered using procedure defined in clause 6.4 of the 3GPP Technical Specification 23.586 titled ‘Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” .
  • This step 712 is referred to as, ‘UE1 discovers UEs 2 to n ’.
  • the UE1 730 obtains the sidelink positioning capabilities of the discovered UEs via the SLPP if not already obtained. This is referred to as, ‘UE1 obtains capabilities for discovered UEs
  • the UE1 730 returns a supplementary services SL-MT-LR response to the serving AMF 750 in an UL NAS TRANSPORT message and includes the Routing identifier received in step 711. This is illustrated as, ‘UL NAS TRANSPORT (SL- MT-LR Response, Routing ID)
  • the SL-MT-LR response indicates which of UEs 2 to n 740, 745 have been discovered and the sidelink positioning capabilities of the discovered UEs.
  • the serving AMF 750 forwards the SL-MT-LR response to the LMF 760 indicated by the Routing identifier received at step 714 and includes a LCS Correlation identifier equal to the Routing identifier. This is shown as,
  • Ranging/Sidelink Positioning of UE1 730 and the other discovered UEs occurs as for an SL-MO-LR as described for steps 710-719 of Figure 6.20.1-1 of the 3GPP Technical Specification 23.273 titled “ 5G System (5GS) Location Services (LCS) Stage 2 (Release 18) ” with the difference that Ranging/Sidelink Positioning location measurement data or results are always returned to the LMF 760 and the LMF 760 indicates to UE1 730 at step 713 or step 714 whether the Ranging/Sidelink Positioning location results will be calculated by the LMF 760 (at step 719) or by UE1 730 (at step 717).
  • 5GS 5G System
  • LCS Location Services
  • the LMF 760 interacts with GMLC 780, 785 to initiate the 5GC -MT-LR procedure for UE2 to n 740, 745 to get their absolute locations, and calculates the relative locations or distances and/or directions related to the UEs. This is illustrated as, ‘Sidelink Positioning/Ranging of UEs 1 to n
  • the LMF 760 returns the Sidelink positioning/ranging location results to the LCS Client or AF 790 as in steps 713-715 and step 724 of clause 6.1.2 of the 3GPP Technical Specification 23.273 titled “ 5G System (5GS) Location Services (LCS) Stage 2 (Release 18) ” .
  • the results also include failure information of the UE(s) that was not discovered.
  • Figure 8 illustrates an example 800 of a procedure to estimate the relative locations or distances and/or directions between UEs, in accordance with aspects of the present disclosure. More specifically, Figure 8 shows procedures for Ranging/Sidelink Positioning control (UE-only operation). Shown are a SL Positioning Client UE 810, a SL Positioning Server UE 820, a UE1 830 and a UE2/. . ,/UEn 840. The various messaging flows 801-809 will now be described.
  • the UE1 830 may receive a Ranging/SL Positioning Service request from either of a SL Positioning client UE 810 (in accordance with step 801a) or a RSPP application layer (in accordance with step 801b).
  • the SL Positioning Client UE 810 provides the request over PC5 during procedures for Ranging/SL Positioning service exposure though PC5 as defined in clause 6.7.1.1 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18).
  • the service request includes the SL Positioning Client UEs user info and Target UEs user info, and required positioning QoS.
  • the service request includes the SL Positioning Client UEs user info, Target UEs user info, SL Reference UEs user info(UE2/.../UEn), and Ranging/SL Positioning QoS information.
  • This step is shown as, ‘Ranging/SL Positioning service request over PC5 ’.
  • the request is from the RSPP application layer.
  • the service request includes type of the result (i.e., absolute location, relative location or ranging information) and the required QoS. This is shown as, Ranging/SL Positioning service request from Application layer
  • UE1 830 discovers UE2/.../UEn 840 (i.e., SL Reference UEs/Located UEs) as defined in clause 6.4 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18), if needed. This is illustrated as, ‘Discovery ’ .
  • UE-only Operation is applied. This is illustrated as, ‘Determine UE-only Operation
  • Step 804 UE1 830 and UE2/.../UEn 840 perform capability exchange.
  • Step 804 may be performed during steps 805 and step 806 with coordination of SL Positioning Server UE 820. This step is shown as, ‘Capability Exchange
  • a SL Positioning Server UE (either co-located with a SL Reference UE/Located UE, or operated by a separate UE) is discovered (if not yet discovered in step 2) and selected.
  • UE1 830 discovers and selects the SL Positioning Server UE as described in clause 6.4 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) and requests SL Positioning Server UE 820 to participate in the Ranging/Sidelink positioning. This is illustrated as, ‘SL Positioning Server UE discover deselection
  • a further step 806 Sidelink Positioning assistance data is transferred among UE1 830/ .../UEn 840 and the SL Positioning Server UE 820. This is illustrated as, ‘Sidelink positioning assistance data transfer [0141]
  • SL PRS measurement is performed between UE1 830 and UE2/.../UEn 840 and possibly also amongst the UEs of UE2/.../UEn 840. This is illustrated as, ‘SL PRS measurement
  • SL PRS measurement data is transferred to the SL Positioning Server UE 820 or is transferred to UE1 830 if it supports SL Positioning Server functionalities, in order to perform result calculation.
  • absolute location, relative location or ranging information is calculated at the UE 830. This is illustrated as, ‘SL PRS measurement data transfer & result calculation
  • the Ranging/SL Positioning result is transferred to either: the SL Positioning Client UE 810 over PC5 (as shown in step 809a) during procedures for Ranging/SL Positioning service exposure though PC5 as defined in clause 6.7.1.1 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18f or the RSPP application layer (as shown in step 809b). These steps are shown as, Ranging/SL positioning response over PC 5 ’ and Ranging/SL positioning service response to Application layer ’, respectively.
  • Table 7 depicts the standardized PQI for transmitting SL ProSe communication messages as a function of different parameters, as provided in 3GPP TS 23.304 titled, “Proximity based Services (ProSe) in the 5G System (5GS) ” (Release 18). This serves as the transport QoS for ProSe services.
  • Table 8 depicts the standardized PQI for transmitting SL V2X communication messages as a function of different parameters, as provided in 3GPP TS 23.287 titled, “Architecture enhancements for 5G System (5GS) to support Vehicle-to-Every thing (V2X) services” (Release 18). This serves as the transport QoS for V2X services.
  • Example services for PQI value 24 include Mission Critical user plane Push To Talk voice (e.g. MCPTT).
  • Example services for PQI value 25 include Non-Mission-Critical user plane Push To Talk voice.
  • Example services for PQI value 26 include Mission Critical Video user plane.
  • Example services for PQI value 60 include Mission Critical delay sensitive signalling (e.g. MC-PTT signalling).
  • Example services for PQI value 61 include Mission Critical Data (e.g. example services are the same as 5QI 6/8/9 as specified in 3GPP TS 23.501.
  • Example services for PQI value 92 include Interactive service - consume VR content with high compression rate via tethered VR headset (as described in 3 GPP TS 22.261).
  • Example services for PQI value 93 include interactive service - consume VR content with low compression rate via tethered VR headset; Gaming or Interactive Data Exchanging (as described in 3GPP TS 22.261). It should be noted that GBR and Delay Critical GBR PQIs can only be used for unicast PC5 communications.
  • Example services for PQI value 21 include platooning between UEs - Higher degree of automation; Platooning between UE and RSU - Higher degree of automation.
  • Example services for PQI value 22 include sensor sharing - higher degree of automation.
  • Example services for PQI value 23 include information sharing for automated driving - between UEs or UE and RSU - higher degree of automation.
  • Example services for PQI value 55 include cooperative lane change - higher degree of automation.
  • Example services for PQI value 56 include platooning informative exchange - low degree of automation; and Platooning - information sharing with RSU.
  • Example services for PQI value 57 include cooperative lane change - lower degree of automation.
  • Example services for PQI value 58 include sensor information sharing - lower degree of automation.
  • Example services for PQI value 59 include platooning - reporting to an RSU.
  • Example services for PQI value 90 include Cooperative collision avoidance; sensor sharing - Higher degree of automation; and video sharing - higher degree of automation.
  • Example services for PQI value 91 include Emergency trajectory alignment; and sensor sharing. - higher degree of automation. It should be noted that, GBR and Delay Critical GBR PQIs can only be used for unicast PC5 communications.
  • Ranging/SL Positioning QoS requirements may be provided in the Ranging/SL Positioning service request generated at the application layer, and is provided from the application layer to the Ranging/SL Positioning layer.
  • Ranging/SL Positioning QoS requirement may be included in the Ranging/SL Positioning Service request from SL Positioning Client UE.
  • the Ranging/SL Positioning layer maps the Ranging/SL Positioning QoS requirement to the Ranging/SL Positioning QoS parameters and provides the Ranging/SL Positioning QoS parameters to the AS layer. If there is no received Ranging/SL Positioning QoS requirement from the application layer, the Ranging/SL Positioning layer determines the Ranging/SL Positioning QoS parameters based on the Ranging/SL positioning Policy/parameters as configured in the clause of 5.1 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18).
  • Ranging/SL Positioning QoS information contains attributes defined in clause 4. lb of the 3GPP TS 23.273, titled “5G System (5GS) Location Services (LCS) ”, Stage 2 (Release 18) with the following additions: the accuracy attribute also includes the relative horizontal accuracy, and the relative vertical accuracy for relative positioning, and the distance accuracy and direction accuracy for Ranging; and Range, which indicates the applicability of the QoS attributes in the Ranging/SL Positioning operation over PC5.
  • Ranging/SL Positioning QoS information is used for determination of Ranging/SL Positioning method.
  • the Ranging/SL Positioning methods are defined in the 3GPP TS 38.355 titled, “Sidelink Positioning Protocol (SLPP); Protocol specification” (Release 18).
  • the V2X/ProSe layer handles the RSPP traffic as the V2X/ProSe application data packets for the QoS treatment.
  • QoS handling mechanism of V2X as defined in clause 5.4 of the 3GPP TS 38.355 titled, “Sidelink Positioning Protocol (SLPP); Protocol specification” (Release 18), or QoS handling mechanism of 5G ProSe as defined in clause
  • LCS Quality of Service will also be briefly introduced. It is used to characterise the location request. It can either be determined by the operator or determined based on the negotiation with the LCS client or the AF. It is optional for LCS client or the AF to provide the LCS Quality of Service in the location request.
  • LCS Quality of Service information is characterised by 3 key attributes, which include: LCS QoS Class as defined below; Accuracy: i.e., Horizontal Accuracy (see clause
  • one or two QoS values for Horizontal Accuracy, Vertical Accuracy can be provided in the location request in addition to a preferred accuracy when LCS QoS Class is set to Multiple QoS Class.
  • the LCS QoS Class defines the degree of adherence by the Location Service to another quality of service parameter (Accuracy), if requested.
  • the 5G system shall attempt to satisfy the other quality of service parameter regardless of the use of QoS Class.
  • One class is the ‘Best Effort Class’. This class defines the least stringent requirement on the QoS achieved for a location request. If a location estimate obtained does not fulfil the other QoS requirements, it should still be returned but with an appropriate indication that the requested QoS was not met. If no location estimate is obtained, an appropriate error cause is sent.
  • Another class is the 'multiple QoS Class’. This class defines intermediate stringent requirements on the QoS achieved for a location request. If the obtained location estimate does not fulfil the most stringent (i.e., primary) other QoS requirements affected by the degree of adherence of the QoS class, then another location estimation may be triggered at LMF attempting less stringent other QoS requirements.
  • the process may be iterated until the least stringent (i.e. minimum) other QoS requirements are attempted. If the least stringent other QoS requirements cannot be fulfilled by a location estimate, then the location estimate shall be discarded, and an appropriate error cause shall be sent.
  • An AF may provide a location request with Multiple QoS Class via NEF.
  • NEF Network Equivalent Function
  • the multiple QoS Class can only be applied for Deferred 5GC-MT-LR Procedure in this release of the specification.
  • Another class is the ‘Assured Class’. This class defines the most stringent requirement on the accuracy achieved for a location request. If a location estimate obtained does not fulfil the other QoS requirements, then it shall be discarded, and an appropriate error cause shall be sent.
  • the LMF decides the positioning method is an implementation aspect not pre-determined by QoS criteria.
  • it may indicate accuracy defined in the 3GPP TS 29.572 titled, “Location Management Services; Stage 3 ” (Release 18), tables 6.1.6.3.2-1 and 6.1.6.3.5-1.
  • For AF it may either indicate the accuracy defined in the same 3GPP TS 29.572, table 6.1.6.3.2-1, or indicate a particular value e.g., PLMN ID defined in the table 5.3.2.4.7-1.
  • An initiator device is a device that initiates a SL positioning/ranging session.
  • the initiator device may be a network entity, (e.g., gNB, LMF) or UE/roadside unit (RSU).
  • gNB gNode B
  • RSU UE/roadside unit
  • a responder device is a device that responds to a SL positioning/ranging session from an initiator device.
  • the responder device may be a network entity, (e.g., gNB, LMF) or UE/roadside unit (RSU).
  • a target-UE may be referred to as a UE of interest whose position (absolute or relative) is to be obtained by the network or by the UE itself.
  • Sidelink positioning refers to positioning a UE using reference signals transmitted over SL, i.e., PC5 interface, to obtain absolute position, relative position, or ranging information.
  • Ranging is the determination of the distance and/or the direction between a UE and another entity, e.g., an anchor UE.
  • An anchor UE is a UE supporting positioning of a target UE, e.g., by transmitting and/or receiving reference signals for positioning, providing positioning- related information, etc., over the SL interface (also may be referred to as SL Reference UE).
  • An assistant UE is a UE supporting Ranging/Sidelink between a SL Reference UE and Target UE over PC5, when the direct Ranging/Sidelink positioning between the SL Reference UE/ Anchor UE and the Target UE cannot be supported.
  • the measurement/results of the Ranging/Sidelink Positioning between the Assistant UE and the SL Reference UE and that between the Assistant UE and the Target UE are determined and used to derive the Ranging/Sidelink Positioning results between Target UE and SL Reference UE.
  • a SL Positioning Server UE is a UE offering location calculation, for a SL Positioning and Ranging based service. It interacts with other UEs over PC5 as necessary in order to calculate the location of the Target UE.
  • the Target UE or SL Reference UE can act as a SL Positioning server UE if location calculation is supported.
  • a SL Positioning Client UE is a third-party UE, other than SL Reference UE and Target UE, which initiates a Ranging/Sidelink positioning service request on behalf of the application residing on it.
  • the SL Positioning Client UE does not have to support Ranging/Sidelink positioning capability, but a communication between the SL Positioning Client UE and SL Reference UE/Target UE has to be established, either via PC5 or via 5GC, for the transmission of the service request and the result.
  • a SL positioning node may refer to a network entity and/or device/UE participating in a SL positioning session, e.g., LMF (location server), gNB, UE, RSU, anchor UE, Initiator and/or Responder device.
  • LMF location server
  • a Configuration entity is a network node or device/UE capable of configuring time-frequency resources and related SL positioning configurations.
  • a SL Positioning Server UE may serve as a configuration entity.
  • Some embodiments provide SL PRS to SL Positioning QoS Mapping. More specifically a direct one-to-one mapping between SL PRS priority and SL Positioning QoS parameters is provided. This one-to-one mapping may be configured (i.e., preconfigured) to the UE that is enabled to transmit SL PRS. Such a UE may comprise one of an anchor UE, target-UE or server UE. In other implementations a Located UE, Client UE, Assistant UE are also not precluded from transmitting SL PRS based on an assigned priority based on the SL Positioning QoS parameters. The SL Positioning QoS may also be based on accuracy according to one or more LCS requests.
  • LCS requests can include: Absolute Location; Absolute Horizontal Location Accuracy; Absolute Vertical Location Accuracy; Relative Location; Relative Horizontal Location Accuracy; Relative Vertical Location Accuracy; Ranging for Distance; Horizontal Distance Location Accuracy; Vertical Distance Location Accuracy; Ranging for Direction; Azimuth Angle of Arrival Direction Accuracy; Zenith Angle of Arrival Direction Accuracy.
  • Table 9 is an exemplary illustration of the one-to-one mapping between SL PRS priority and SL Positioning QoS based on absolute horizontal location accuracy only, where the highest to lowest priority is arranged based on descending order (lowest SL PRS Priority value maps to highest priority positioning/ranging service based on accuracy, while the highest SL PRS priority value maps to the lowest priority SL positioning/ranging service based on accuracy).
  • exemplary Table 9 may also be separately applied to relative horizontal location accuracy.
  • the horizontal accuracy values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
  • Table 10 is an exemplary illustration of the one-to-one mapping between SL PRS priority and SL Positioning QoS based on absolute vertical location accuracy only.
  • exemplary Table 10 may also be separately applied to relative vertical location accuracy.
  • the vertical accuracy values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
  • Table 11 is an exemplary illustration of the one-to- one mapping between SL PRS priority and SL Positioning QoS based on ranging for horizontal distance accuracy only.
  • exemplary Table 11 may also be separately applied to relative distance accuracy.
  • the distance accuracy values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
  • Table 12 is an exemplary illustration of the one-to- one mapping between SL PRS priority and SL Positioning QoS based on ranging for direction accuracy only.
  • the direction accuracy values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
  • Table 12 provides exemplary mapping of SL PRS Priority and SL Positioning QoS using either Ranging for azimuth direction or zenith direction accuracy or a singular overall direction accuracy or any combination thereof.
  • Table 13 is an exemplary illustration of the one-to-one mapping between SL PRS priority and SL Positioning QoS based on the positioning response time/positioning latency (i.e., end-to-end positioning latency) only.
  • the positioning response time/positioning latency values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
  • the SL PRS priority may be mapped to a pre-defined SL PRS delay budget or SL Positioning delay budget or Packet delay budget or Positioning Delay budget or Location delay budget given by exemplary values indicated in Table 13.
  • SL PRS priorities ⁇ 1-3 ⁇ may be mapped to a “no delay” category, i.e., the SL PRS should be transmitted with no delay and the measurement measuring and responding UE should immediately return any location estimate or dispatchable location that it has measured based on the transmitted SL PRS.
  • SL PRS priorities ⁇ 4-6 ⁇ may be mapped to a “low delay” category, i.e., fulfilment of the response time requirement takes precedence over fulfilment of the accuracy requirement.
  • SL PRS priorities ⁇ 7-8 ⁇ may be mapped to a “delay tolerant” category, i.e., fulfilment of the accuracy requirement takes precedence over fulfilment of the response time requirement. It may be further up to UE implementation, whether to select and assign a SL PRS priority/priorities based in each subset of SL PRS priorities according to the given/received SL Positioning. QoS requirements. Table 14 shows SL PRS priority mapping table based on the different categories.
  • the one or more SL PRS priorities may be based on one or more of the mapping tables described above.
  • the 8-levels of SL PRS priority may be a function of the mobility state of the UE based on either: Absolute/relative horizontal speed/velocity estimates (where velocity may also include heading); and/or Absolute/relative vertical speed/velocity estimates (where velocity may also include heading) or high level mobility values comprising stationary, low mobility, medium mobility or high mobility.
  • the SL PRS priority may comprise of a one or more combination of SL Positioning QoS accuracy parameters given by absolute/relative horizontal accuracy, absolute/relative vertical accuracy, ranging for distance accuracy, ranging for direction accuracy and/or response times.
  • This can enable configuration of a single table that encompasses all SL Positioning QoS accuracy parameters and may provide a standardized or unified SL PRS mapping table.
  • Table 15 shows the complete consolidated SL PRS priority mapping table based on different described SL Positioning QoS parameters.
  • Table 15 [0186] In another implementation, the SL PRS priorities shown in Table 15 may be further associated with a category described in Table 14.
  • SL Positioning LCS QoS Classes may be defined to consolidate the one or more SL Positioning QoS Parameters and thereafter be mapped in a one-to-one manner with the SL-RS priority.
  • the SPLQCs may be defined in descending order, where the stringent SL Positioning QoS parameters are assigned with the lowest number, e.g., SPLQC 1, while the most relaxed requirements are assigned with the highest number, e.g., SPLQC 8.
  • the SPLQCs may be arranged in ascending order, where the stringent SL Positioning QoS parameters are assigned with the highest number, e.g., SPLQC 8, while the relaxed requirements are assigned with the lowest number, e.g., SPLQC 1.
  • Table 16 shows an example of how an SPLQC may be defined in descending order:
  • Table 16 [0188] The complete consolidated SL PRS priority mapping shown in Table 15 can be transformed as shown in Table 17.
  • the definitions of the SPLQC may be standardized and defined in either the Ranging/SL Positioning Application, the Ranging SL Positioning layer or the SL Positioning Protocol (SLPP) layer.
  • the guidelines for defining each SPLQC may be based on one or more combination of absolute/relative horizontal accuracy value ranges, absolute/relative vertical accuracy value ranges, SL positioning response times/end-to-end latencies, and absolute/relative horizontal/vertical speed/velocity estimate value ranges.
  • Table 16 also captures the trade-off between positioning accuracies and the positioning response times, for example higher accuracies require longer durations, while lower accuracies can be fulfilled in a shorter period.
  • the manner in which the SPLQC is defined may be based on UE implementation.
  • the SL PRS priority to SPLQC mapping table may lower the overall signaling overhead in terms not considering each of the SL value ranges of each SL Positioning QoS parameter.
  • the disclosure herein also relates to procedures for SL PRS priority mapping to SL positioning QoS requirements/parameters. According to some embodiments, the procedures in the protocol stack for mapping the SL PRS priority to the SL Positioning QoS are described.
  • Figure 9 illustrates an example 900 of SL PRS priority mapping to SL positioning QoS procedures, in accordance with aspects of the present disclosure. More specifically, Figure 9 illustrates exemplary mechanisms in UE-only based SL positioning operation and in-coverage and out-of-coverage scenarios in which the SL Positioning QoS may be mapped to each of the SL PRS priority levels.
  • Figure 9 shows a first UE 910 denoted ‘UE-A’ and a second UE 920 denoted ‘UE-B’.
  • Each UE 910, 920 is shown as comprising SLPP, ProSe/V2x, SDAP, PDCP, RLC, MAC and PHY.
  • a ranging/SL positioning layer 912 and ranging/SL positioning application 914 for the first UE 910.
  • a ranging/SL positioning layer 922 and ranging/SL positioning application 924 for the second UE 920.
  • the first UE 910 communicates with the ranging/SL positioning layer 912, with the ranging/SL positioning layer 912 shown communicating with the ranging/SL positioning application 914.
  • a similar arrangement is shown for the second UE 920, layer 922 and application 924.
  • the various SLPP, ProSe/V2X, SDAP, PDCP, RLC, MAC and PHY aspects of the first and second UEs 910, 920, are shown in communication with each other.
  • a first step 901 is shown, wherein the Ranging/SL Positioning Application/LCS Client 914, 924 generates the required SL Positioning QoS associated to a requested location estimate, which may comprise of one or more of absolute horizontal location estimate, absolute vertical location estimate, relative horizontal location estimate, relative vertical location estimate, ranging for distance estimate, ranging for direction estimate, absolute velocity estimate, or relative velocity estimate.
  • This step is shown as, ‘The ranging/SL positioning QoS is generated at application level
  • a second step 902 is shown, wherein the Ranging/SL Positioning layer 912, 922 is responsible for mapping the Application Positioning QoS requirements to the Ranging/SL Positioning QoS Parameters and provides the Ranging/SL Positioning QoS parameters to the AS layer. If there is no received Ranging/SL Positioning QoS requirement from the application layer, the Ranging/SL Positioning layer 912, 922 determines the Ranging/SL Positioning QoS parameters based on the Ranging/SL positioning Policy/parameters as configured and provision to the UE .
  • step 903 is shown, wherein the SL PRS priority is mapped according to the SL Positioning QoS based on the following options.
  • One option is provided in step 903a wherein the SL PRS priority mapping to SL Positioning QoS is performed within the Ranging/SL Positioning layer 912, 922 according to the embodiments and mapping tables described herein.
  • the SPLQC may also be defined here.
  • Step 903a is referred to in Figure 9 as, ‘SL PRS priority mapping to SL positioning QoS including SP LQC definition ’.
  • step 903b Another option is provided by step 903b, wherein the positioning method is selected and a recommended SL PRS configuration to meet the received SL Positioning QoS is generated.
  • the SL PRS configuration may include at least one of comb-size including number of symbols and resource element offset, transmission bandwidth and SL PRS priority.
  • the SL PRS priority mapping to SL Positioning QoS is performed within the SLPP layer according to the embodiments and mapping tables described herein.
  • Step 903b is referred to in Figure 9 as, ‘SL PRS priority mapping to SL positioning QoS’.
  • a further option is provided by step 903 c, wherein in the case of the unavailability of the SL Positioning QoS, the SL PRS priority mapping is performed within the ProSe/V2X layer according to the standardized PQIs described in Table 7 and Table 8. This implies that the SL PRS will be mapped according to the default priority values according to the appropriate V2X/ProSe service requirements.
  • a Ranging/SL Positioning service requirement may be defined as part of the standardized PQIs, which may cover SLPP messages and/or SL PRS.
  • the step 903c is referred to in Figure 9 as, ‘SL PRS priority mapping to SL positioning QoS including SP LQC based on transport QoS if 903a or 903b is not available or fulfilled’.
  • the SL PRS priority is then passed down to the MAC and physical layer for the transmission of SL PRS.
  • Multiple SL PRS priorities may be provided to the MAC and physical layer corresponding to the different location service requests each associated with a particular SL Positioning QoS class/set of parameters either from the same or different application within the UE 910, 920 or received from an external network entity. This step is illustrated as, ‘SL PRS priority used by MAC and physical layer ’.
  • the ranging/SL positioning applications 914, 924 trigger ranging/SL positioning upon request from an internal LCS client or external client UE.
  • ranging/SL positioning layers 912, 922, control UE discovery and selection provide the Application Layer IDs, and Source/Destination Layer-2 IDs, etc.
  • the SL PRS priority/priorities is/are signaled in a 1 st , e.g., SCI format 1-B or 2nd stage SCI, e.g., SCI format 2-D, to UE-B 920 and is used by UE-B 920 to perform autonomous resource selection (also known as Mode 2 or Scheme 2 resource allocation for sidelink).
  • a 1 st e.g., SCI format 1-B or 2nd stage SCI, e.g., SCI format 2-D
  • autonomous resource selection also known as Mode 2 or Scheme 2 resource allocation for sidelink.
  • the SL PRS priority/priorities is/are signaled according to the following scenarios.
  • UE A 910 is a target UE and is configured to perform UL type SL-TDOA based on SL-RTOA measurements, where UE-B 920 and/or any additional UEs may perform SL-RTOA measurements.
  • UE-A 910 may signal a one or more SL PRS priorities based on the SL Pos. QoS parameters associated with the one or more SL PRS transmissions to UE-B 920 and/or any additional UEs.
  • UE B 920 may measure the SL PRS and perform the requested SL positioning measurement(s), i.e., in this case SL-RTOA, based on the associated received SL PRS priority.
  • UE A 910 is a target UE and is configured to perform single or double-sided SL-RTT based on UE-Rx-Tx time difference measurements, where UE-A 910 may perform SL- UE-Rx-Tx time difference measurements.
  • UE-A 910 may signal a request to UE-B 920 including one or more SL PRS priorities based on the SL Pos. QoS parameters associated with the one or more requested SL PRS transmissions to be transmitted to UE-A 910 from UE-B 920.
  • Target UE A 910 may measure the SL PRS received from UE-B 920 and perform the requested SL positioning measurement(s), i.e., in this case UE Rx-Tx time difference measurement, based on the associated received SL PRS priority.
  • the SL-PRS priority may be signalled using lower layer signalling such as 1 st , e.g., SCI format 1-B or 2nd stage SCI, e.g., SCI format 2-D, a new SL MAC CE or higher-layer signalling such as PC5 RRC, or SLPP.
  • SL PRS priorities may be further used to control the congestion within a dedicated SL PRS resource pool or a shared resource pool (comprising of SL PRS and SL-SCH data (SL communication data)).
  • the SL PRS priority mapping is performed at UE A 910 (SL PRS transmitting UE, e.g. an anchor UE with server UE functionalities).
  • the mapping profile/table may be provided to UE-B 920 (SL PRS receiving UE, e.g. a target UE) in case of unicast SL PRS transmissions or other sets of UEs (in case of groupcast SL PRS transmissions) via UE-specific signalling, e.g., 1st or 2nd stage SCI, SL MAC CE, SLPP signalling, e.g., SLPP ProvideAssistanceData message.
  • UE-specific signalling e.g., 1st or 2nd stage SCI, SL MAC CE, SLPP signalling, e.g., SLPP ProvideAssistanceData message.
  • SL PRS priority to SL Positioning QoS Mapping is performed entirely in the AS (Access Stratum) layer.
  • AS Access Stratum
  • SL PRS priority to SL Positioning QoS mapping may be performed in the Service Data Adaptation Protocol (SDAP) layer, or Packet Data Convergence protocol (PDCP) layer, or Radio Link Control (RLC) layer or Medium Access Control (MAC) layer.
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • the SL PRS priority to SL Positioning QoS Mapping may also be performed in the physical (PHY) layer. This implies that the SLPP layer and ProSe/V2X layer and are transparent to this mapping.
  • the SLPP/Prose V2X layer provide the LCS QoS of an associated LCS request and the AS layer determines the SL PRS priority based on the received LCS QoS.
  • the mapping may be performed by the network, e.g., gNB or LMF and may be able to provision the SL PRS priority to SL Positioning QoS mapping table to UE-A 910 and UE-B 920 via appropriate broadcast signalling, using SIB or posSIB signalling.
  • UE-specific signalling such DL MAC CE, RRC, SLPP or LPP signalling, e.g., LPP ProvideAssistanceData message may be used.
  • Embodiments of the disclosure herein also relate to the mapping of SL PRS priority to SL positioning QoS based on logical channel prioritization and resource availability. More specifically, the SL PRS priority, which has been mapped based on SL positioning QoS, may correspond to a percentage/ratio of freely available time-frequency resources, e.g., slots, subframes, frames, etc that can be used for transmitting SL PRS.
  • This percentage of freely available slots may extend to: a SL PRS dedicated resource pool, where time-frequency resources, e.g., SL PRS resources, slots are allocated for sidelink control and associated SL PRS transmissions; or a Shared/common resource pool, where time-frequency resources, e.g., SL slots are allocated for sidelink control and associated SL PRS and SL-SCH (SL data) transmissions.
  • time-frequency resources e.g., SL PRS resources
  • SL-SCH SL data
  • the logical channel prioritization (LCP) mechanism within the MAC layer comprising of 8 levels of priority may be mapped in a one-to-one manner to the SL PRS priority such that the highest priority associated with the lowest logical channel priority, e.g., 0 may be mapped to set of resources within a dedicated or shared/common pool where the percentage of available resources over the total number of resources in a serving cell is higher than a configured threshold M, which reflects a higher percentage of available SL resources.
  • LCP logical channel prioritization
  • Table 18 is an exemplary illustration of the SL PRS priority mapping to the percentage of freely available slots.
  • Table 18 shows example mapping of SL PRS priority as a function of LCP and percentage of freely available slots.
  • the aforementioned freely available SL resource(s) may be described in terms of available SL PRS resource(s) associated with a frequency and time domain configuration, available slots, available subframes, available frames, or available hyper frames. Furthermore, the type of SL PRS priority resource mapping may be applicable to both Mode 1/Schemel or Mode 2/Scheme 2 SL positioning resource allocation procedures.
  • the UE Upon receiving a sidelink resource grant either from a base station, e.g., gNB or location server or based on sensing and resource selection procedure, the UE determines which logical channel(s) will carry the SL PRS transmissions(s) based on the one of the following criteria: LCP - the UE addresses the logical channels in which to transmit SL PRS in a descending order of priority based on the SL PRS priority and SL Positioning QoS; SL PRS delay budget - this may be applied to the SL PRS to establish which SL PRS may be transmitted in the highest priority logical channels; Resource Availability - the UE selects logical channels that can be accommodated to transmit SL PRS within the available percentage of sidelink resources based on M as shown in Table 18.
  • LCP the UE addresses the logical channels in which to transmit SL PRS in a descending order of priority based on the SL PRS priority and SL Positioning QoS
  • SL PRS delay budget this may
  • the UE With the chosen logical channels, the UE then transmits SL PRS to the other UE(s) based on the above criteria.
  • a default SL PRS priority may be mapped to a default logical channel in the case that any of the SL positioning QoS or resource availability or transport QoS including packet delay budget or SL PRS delay budget is unavailable.
  • the logical channel prioritization for SL PRS is designed to ensure that the most important logical channels are served first based on the SL PRS priority, which is based on the SL positioning QoS described in the embodiments and mapping tables provided herein.
  • the above embodiment described in Table 18, may also be implemented in a manner that is decoupled from the logical channel priority, i.e., the SL PRS priority may be directly mapped to the available percentage of freely available resources.
  • other metrics to express the amount of freely available SL positioning resources may also be used, e.g., ratio of available resources to occupied resources or ratio of symbols in a slot/slots in a subframe for SL PRS to SL-SCH data and so forth. This can be extended to any quantitative metric which can express the amount of freely available sidelink resources to perform SL positioning.
  • a user equipment for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmit one or more SL PRS according to the one or more SL PRS configurations.
  • SL sidelink
  • QoS quality of service
  • PRS SL
  • the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
  • the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
  • the latency category can be no delay; low delay; and delay tolerant.
  • the SL positioning QoS parameters comprise a mobility state of the UE.
  • the mobility state can be based on an absolute velocity or a relative velocity, or absolute speed or relative speed, optionally in vertical or horizontal, or may comprise one or more high-level mobility state indicators such as stationary, low mobility, medium mobility, high mobility or alternatively mobile UE.
  • the latter can enable SL PRS priority differentiation based on high-level indicators as opposed to speed/velocity values.
  • the at least one processor is configured to cause the UE to determine the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services (LCS) QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
  • LCS SL positioning location services
  • the at least one processor is configured to cause the UE to determine the mapping in either of: a ranging/SL positioning communication layer; a SL positioning protocol (‘SLPP) layer; a vehicle-to-everything (V2X)/ProSe layer; or an access stratum (AS) layer.
  • SLPP SL positioning protocol
  • V2X vehicle-to-everything
  • AS access stratum
  • the at least one processor is configured to cause the UE to determine the one or more SL positioning QoS requirements by: receiving the one or more SL positioning QoS requirements from either of: a SL positioning application; or an LCS client.
  • the at least one processor is further configured to cause the UE to: transmit, to at least one other UE, the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
  • the transmission may be via UE-specific signalling, broadcast, or groupcast.
  • the at least one processor is further configured to cause the UE to determine the mapping to correspond to a percentage or ratio of available SL positioning resources.
  • the SL positioning resources may be part of a dedicated resource pool or a shared/common resource pool. Examples of resources include slots, subframes, that can be used for transmitting SL PRS.
  • the at least one processor is configured to cause the UE to determine the mapping to correspond to a percentage or ratio of available SL positioning resources by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority, which corresponds to a different percentage or ratio of available SL positioning resources.
  • the at least one processor is configured to cause the UE to apply the percentage or ratio of available SL positioning resources to: a SL PRS dedicated resource pool; and/or a SL PRS shared or common resource pool.
  • the mapping between logical channel and available SL positioning resources can be a direct mapping.
  • the at least one processor is configured to cause the UE to determine the mapping by: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables, from a network entity of a wireless communication network.
  • the network entity is a gNB or LMF.
  • the UE is a UE selected from the list of UEs consisting of an anchor UE; the target UE; a server UE; a located UE; a client UE; and an assistant UE.
  • a method in an UE comprising: determining one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmitting one or more SL PRS according to the one or more SL PRS configurations.
  • SL sidelink
  • QoS quality of service
  • the configuration may also comprise a comb-size including a number of symbols and resource element offsets, transmission bandwidth, etc.
  • the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
  • the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
  • the latency category can be no delay; low delay; and delay tolerant.
  • the SL positioning QoS parameters comprise a mobility state of the UE.
  • the mobility state can be based on an absolute velocity or a relative velocity, or absolute speed or relative speed, optionally in vertical or horizontal, or may comprise one or more high-level mobility state indicators such as stationary, low mobility, medium mobility, high mobility or alternatively mobile UE.
  • the latter can enable SL PRS priority differentiation based on high-level indicators as opposed to speed/velocity values.
  • the determining the mapping comprises determining the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services (LCS) QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
  • LCS SL positioning location services
  • the determining the mapping comprising determining the mapping in either of: a ranging/SL positioning communication layer; a SL positioning protocol(‘SLPP) layer; a vehicle-to-everything (V2X)/ProSe layer; or an access stratum (AS) layer.
  • SLPP SL positioning protocol
  • V2X vehicle-to-everything
  • AS access stratum
  • the determining the one or more SL positioning QoS requirements comprises determining the one or more SL positioning QoS requirements by: receiving the one or more SL positioning QoS requirements from either of: a SL positioning application; or an LCS client.
  • Some embodiments further comprise transmitting, to at least one other UE, the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
  • the transmission may be via UE-specific signalling, broadcast, or groupcast.
  • the determining the mapping comprises determining the mapping to correspond to a percentage or ratio of available SL positioning resources.
  • the SL positioning resources may be part of a dedicated resource pool or a shared/common resource pool. Examples of resources include slots, subframes, that can be used for transmitting SL PRS.
  • the determining the mapping comprises determining the mapping to correspond to a percentage or ratio of available SL positioning resources by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority, which corresponds to a different percentage or ratio of available SL positioning resources.
  • Some embodiments comprise applying the percentage or ratio of available SL positioning resources to: a SL PRS dedicated resource pool; and/or a SL PRS shared or common resource pool.
  • mapping between logical channel and available SL positioning resources can be a direct mapping.
  • the determining the mapping comprises: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables, from a network entity of a wireless communication network.
  • the network entity is a gNB or LMF.
  • the UE is a UE selected from the list of UEs consisting of: an anchor UE; the target UE; a server UE; a located UE; a client UE; and an assistant UE.
  • a processor for wireless communication comprising: at least one controller coupled with at least one memory and configured to cause the processor to: input one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL PRS
  • the configuration may also comprise a comb-size including a number of symbols and resource element offsets, transmission bandwidth, etc.
  • the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
  • the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
  • the latency category can be no delay; low delay; and delay tolerant.
  • the SL positioning QoS parameters comprise a mobility state of a UE.
  • the mobility state can be based on an absolute velocity or a relative velocity, or absolute speed or relative speed, optionally in vertical or horizontal.
  • the at least one controller is configured to cause the processor to determine the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services (LCS) QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
  • LCS SL positioning location services
  • the at least one controller is configured to cause the processor to determine the mapping in either of a ranging/SL positioning communication layer; a SL positioning protocol (SLPP) layer; a vehicle-to-everything (V2X)/ProSe layer; or an access stratum (AS) layer.
  • SLPP SL positioning protocol
  • V2X vehicle-to-everything
  • AS access stratum
  • the at least one controller is configured to cause the processor to determine the one or more SL positioning QoS requirements by: inputting the one or more SL positioning QoS requirements from either of: a SL positioning application; or a LCS client.
  • the at least one controller is further configured to cause the processor to: output the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
  • the at least one controller is further configured to cause the processor to determine the mapping to correspond to a percentage or ratio of available SL positioning resources, preferably by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority which corresponds to a different percentage or ratio of available SL positioning resources.
  • the SL positioning resources may be part of a dedicated resource pool or a shared/common resource pool. Examples of resources include slots, subframes, that can be used for transmitting SL PRS.
  • the at least one controller is configured to cause the processor to determine the mapping by: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables from a network entity of a wireless communication network.
  • the network entity is a gNB or LMF.
  • a method in a processor for wireless communication comprising: inputting one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and outputting one or more SL PRS according to the one or more SL PRS configurations.
  • SL sidelink
  • QoS quality of service
  • the configuration may also comprise a comb-size including a number of symbols and resource element offsets, transmission bandwidth, etc.
  • the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
  • the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
  • the latency category can be no delay; low delay; and delay tolerant.
  • the SL positioning QoS parameters comprise a mobility state of a UE.
  • the mobility state can be based on an absolute velocity or a relative velocity, or absolute speed or relative speed, optionally in vertical or horizontal.
  • the method comprises determining the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services (LCS) QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
  • LCS SL positioning location services
  • the method comprises determining the mapping in either of: a ranging/SL positioning communication layer; a SL positioning protocol (SLPP) layer; a vehicle-to-everything (V2X)/ProSe layer; or an access stratum (AS) layer.
  • SLPP SL positioning protocol
  • V2X vehicle-to-everything
  • AS access stratum
  • the method comprises determining the one or more SL positioning QoS requirements by: inputting the one or more SL positioning QoS requirements from either of: a SL positioning application; or a LCS client.
  • the method further comprises: outputting the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
  • the method comprises determining the mapping to correspond to a percentage or ratio of available SL positioning resources, preferably by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority which corresponds to a different percentage or ratio of available SL positioning resources.
  • the SL positioning resources may be part of a dedicated resource pool or a shared/common resource pool. Examples of resources include slots, subframes, that can be used for transmitting SL PRS. [0285] In some embodiments, there are 8 logical channels. The mapping between logical channel and available SL positioning resources can be a direct mapping.
  • the method comprises determining the mapping by: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables from a network entity of a wireless communication network.
  • the network entity is a gNB or LMF.
  • a network entity for wireless communication comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: determine a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values; transmit the mapping to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
  • SL sidelink
  • QoS Quality of Service
  • PRS SL positioning reference signal
  • a method in a network entity comprising: determining a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values; transmitting the mapping to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
  • SL sidelink
  • QoS Quality of Service
  • PRS SL positioning reference signal
  • SL Positioning techniques may be utilised to obtain good SL Positioning performance in terms of the received SL Positioning QoS, e.g., high accuracy or low latency positioning. This enables the computation of absolute location, relative location, distance, direction, velocity estimates for a single UE or amongst multiple UEs.
  • SL PRS priority has been defined for the transmission of SL PRS, which assists in resource allocation and congestion control in SL, however a key open issue is the mechanism of how the SL PRS priority is mapped to the SL Positioning QoS.
  • the disclosure herein describes methods to enable SL PRS priority to be mapped to different individual SL positioning QoS parameters, including absolute/relative horizontal/vertical accuracies, distance accuracy, direction accuracy, and mobility states.
  • the disclosure herein also describes a consolidated method of mapping the SL PRS priority with all of the aforementioned SL positioning QoS parameters, considering the accuracy and positioning latency trade-off.
  • the disclosure herein also describes the procedures of the communication stack, wherein the SL PRS priority is mapped to the SL Positioning QoS parameters and transferred to the lower layers, which assists in the transmission of SL PRS from one to another UE or other sets of UEs.
  • the disclosure herein provides a method to describe various mechanisms to map the SL PRS priority to different SL Pos. QoS parameters are detailed.
  • the disclosure herein provides a method to configure (i.e., pre-configure) a consolidated SL PRS priority mapping table, in addition a definition of a SL Positioning LCS Qos Class is further described.
  • the disclosure herein provides a method to enable the procedures to map the SL PRS priority with the received SL Positioning QoS at the UE/device.
  • the disclosure herein provides a method in a wireless UE/device wherein: a first communication device receives SL Positioning QoS requirements associated to a location request from an LCS client/ Application and maps the requirements to SL Positioning QoS parameters; the first communication device selects a positioning method and an associated plurality of recommended SL PRS configuration parameters based on the received SL Positioning requirements; the recommended SL PRS configuration parameters comprising at least SL PRS priority; the first communication device determines an association/mapping amongst a set of SL PRS priorities according to the received SL Positioning QoS requirements; the first communication device selects a SL PRS priority according to the received SL Positioning QoS requirements; the first communication device transmits SL PRS to one or more other UE/devices according to the SL PRS priority and recommended SL PRS configuration.
  • the SL PRS priority values are mapped to SL positioning QoS parameters comprising absolute horizontal location accuracy, relative horizontal location accuracy, absolute vertical location accuracy, relative vertical location accuracy, horizontal distance, vertical distance, Azimuth direction accuracy or Zenith direction accuracy or combination thereof.
  • the SL PRS priority values are mapped according to SL positioning QoS parameters comprising a positioning response time/positioning latency defined as part of a received SL positioning location request.
  • the SL PRS priority values are mapped according to SL positioning QoS parameters, which are based on a category comprising of no delay, low delay or delay tolerant.
  • the SL PRS priority values are mapped according to SL positioning QoS parameters comprising the mobility state of the UE.
  • the SL PRS priority values are mapped according to all SL Positioning QoS parameters in a consolidated manner.
  • a SL Positioning LCS QoS Classes may be defined to consolidate the one or more SL Positioning QoS Parameters and thereafter be mapped in a one-to-one manner with the SL-RS priority.
  • the SL PRS priority to SL Positioning QoS mapping may be performed in the Ranging/SL positioning communication layer, Sidelink positioning protocol layer or V2X/ProSe layer.
  • the first communication device transmits the SL PRS priority mapping table/profile to a second communication device using UE-specific signalling or broadcast or groupcast signalling.
  • the disclosure herein also provides a method in a network apparatus, wherein the network apparatus performs the SL PRS priority to SL Positioning QoS mapping and transmits the mapping table/profile to the SL PRS transmitting UE and one or more receiving UEs using UE-specific signalling or broadcast signalling.
  • FIG. 10 illustrates an example of a UE 1000 in accordance with aspects of the present disclosure.
  • the UE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008.
  • the processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, 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 1002, the memory 1004, the controller 1006, or the transceiver 1008, 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 1002 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1002 may be configured to operate the memory 1004. In some other implementations, the memory 1004 may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the UE 1000 to perform various functions of the present disclosure.
  • an intelligent hardware device e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof.
  • the processor 1002 may be configured to operate the memory 1004. In some other implementations, the memory 1004 may be integrated into the processor 1002.
  • the processor 1002 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the UE 1000 to perform various functions of the present disclosure.
  • the memory 1004 may include volatile or non-volatile memory.
  • the memory 1004 may store computer-readable, computer-executable code including instructions when executed by the processor 1002 cause the UE 1000 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such the memory 1004 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 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause the UE 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004).
  • the processor 1002 may support wireless communication at the UE 1000 in accordance with examples as disclosed herein.
  • the UE 1000 may be configured according to the various embodiments of a UE as described herein and/or to support a means for performing the methods described herein.
  • the controller 1006 may manage input and output signals for the UE 1000.
  • the controller 1006 may also manage peripherals not integrated into the UE 1000.
  • the controller 1006 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems.
  • the controller 1006 may be implemented as part of the processor 1002.
  • the UE 1000 may include at least one transceiver 1008. In some other implementations, the UE 1000 may have more than one transceiver 1008.
  • the transceiver 1008 may represent a wireless transceiver.
  • the transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.
  • a receiver chain 1010 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receiver chain 1010 may include one or more antennas for receive the signal over the air or wireless medium.
  • the receiver chain 1010 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal.
  • the receiver chain 1010 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receiver chain 1010 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • a transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, packets).
  • the transmitter chain 1012 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 1012 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 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
  • FIG. 11 illustrates an example of a processor 1100 in accordance with aspects of the present disclosure.
  • the processor 1100 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1100 may include a controller 1102 configured to perform various operations in accordance with examples as described herein.
  • the processor 1100 may optionally include at least one memory 1104, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 1100 may optionally include one or more arithmetic-logic units (ALUs) 1106.
  • ALUs arithmetic-logic units
  • One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
  • the processor 1100 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 1100) 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
  • flash memory phase change memory
  • PCM phase change memory
  • the controller 1102 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 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein.
  • the controller 1102 may operate as a control unit of the processor 1100, generating control signals that manage the operation of various components of the processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1104 and determine subsequent instruction(s) to be executed to cause the processor 1100 to support various operations in accordance with examples as described herein.
  • the controller 1102 may be configured to track memory address of instructions associated with the memory 1104.
  • the controller 1102 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1102 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein.
  • the controller 1102 may be configured to manage flow of data within the processor 1100.
  • the controller 1102 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1100.
  • ALUs arithmetic logic units
  • the memory 1104 may include one or more caches (e.g., memory local to or included in the processor 1100 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 1104 may reside within or on a processor chipset (e.g., local to the processor 1100). In some other implementations, the memory 1104 may reside external to the processor chipset (e.g., remote to the processor 1100).
  • the memory 1104 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1100, cause the processor 1100 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 1102 and/or the processor 1100 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the processor 1100 to perform various functions.
  • the processor 1100 and/or the controller 1102 may be coupled with or to the memory 1104, the processor 1100, the controller 1102, and the memory 1104 may be configured to perform various functions described herein.
  • the processor 1100 may include multiple processors and the memory 1104 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 1106 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 1106 may reside within or on a processor chipset (e.g., the processor 1100).
  • the one or more ALUs 1106 may reside external to the processor chipset (e.g., the processor 1100).
  • One or more ALUs 1106 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 1106 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 1106 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 1106 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1106 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND)
  • the processor 1100 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 1100 may be configured according to the various embodiments of a processor described herein and/or to or operable to support a means for performing the methods described herein.
  • FIG. 12 illustrates an example of a NE 1200 in accordance with aspects of the present disclosure.
  • the NE 1200 may include a processor 1202, a memory 1204, a controller 1206, and a transceiver 1208.
  • the processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, 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 1202, the memory 1204, the controller 1206, or the transceiver 1208, 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 1202 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1202 may be configured to operate the memory 1204. In some other implementations, the memory 1204 may be integrated into the processor 1202. The processor 1202 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the NE 1200 to perform various functions of the present disclosure.
  • an intelligent hardware device e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof.
  • the processor 1202 may be configured to operate the memory 1204. In some other implementations, the memory 1204 may be integrated into the processor 1202.
  • the processor 1202 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the NE 1200 to perform various functions of the present disclosure.
  • the memory 1204 may include volatile or non-volatile memory.
  • the memory 1204 may store computer-readable, computer-executable code including instructions when executed by the processor 1202 cause the NE 1200 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such the memory 1204 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 1202 and the memory 1204 coupled with the processor 1202 may be configured to cause the NE 1200 to perform one or more of the functions described herein (e.g., executing, by the processor 1202, instructions stored in the memory 1204).
  • the processor 1202 may support wireless communication at the NE 1200 in accordance with examples as disclosed herein.
  • the NE 1200 may be configured according to the various embodiments of network entities described herein and/or to support a means for performing the methods described herein.
  • the controller 1206 may manage input and output signals for the NE 1200.
  • the controller 1206 may also manage peripherals not integrated into the NE 1200.
  • the controller 1206 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems.
  • the controller 1206 may be implemented as part of the processor 1202.
  • the NE 1200 may include at least one transceiver 1208. In some other implementations, the NE 1200 may have more than one transceiver 1208.
  • the transceiver 1208 may represent a wireless transceiver.
  • the transceiver 1208 may include one or more receiver chains 1210, one or more transmitter chains 1212, or a combination thereof.
  • a receiver chain 1210 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receiver chain 1210 may include one or more antennas for receive the signal over the air or wireless medium.
  • the receiver chain 1210 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal.
  • the receiver chain 1210 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receiver chain 1210 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • a transmitter chain 1212 may be configured to generate and transmit signals (e.g., control information, data, packets).
  • the transmitter chain 1212 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 1212 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 1212 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
  • Figure 13 illustrates a flowchart of a method in accordance with aspects of the present disclosure.
  • the operations of the method 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 may include determining one or more SL positioning QoS requirements associated with a request for SL positioning of a target UE.
  • the operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a UE as described with reference to Figure 10.
  • the method may include determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL PRS configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter.
  • the operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a UE as described with reference to Figure 10.
  • the method may include determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements.
  • the operations of 1306 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1306 may be performed a UE as described with reference to Figure 10.
  • the method may include determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values.
  • the operations of 1308 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1308 may be performed by a UE as described with reference to Figure 10.
  • the method may include selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations.
  • the operations of 1310 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1310 may be performed by a UE as described with reference to Figure 10.
  • the method may include transmitting one or more SL PRS according to the one or more SL PRS configurations.
  • the operations of 1312 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1312 may be performed by a UE as described with reference to Figure 10.
  • Figure 14 illustrates a flowchart of a method in accordance with aspects of the present disclosure.
  • the operations of the method may be implemented by a processor as described herein.
  • the processor may execute a set of instructions to control the function elements of the processor to perform the described functions.
  • the method may include inputting one or more SL positioning QoS requirements associated with a request for SL positioning of a target UE.
  • the operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a processor as described with reference to Figure 11.
  • the method may include determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL PRS configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter.
  • the operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a processor as described with reference to Figure 11.
  • the method may include determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements.
  • the operations of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1406 may be performed a processor as described with reference to Figure 11.
  • the method may include determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values.
  • the operations of 1408 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1408 may be performed by a processor as described with reference to Figure 11.
  • the method may include selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations.
  • the operations of 1410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1410 may be performed by a processor as described with reference to Figure 11.
  • the method may include outputting one or more SL PRS according to the one or more SL PRS configurations.
  • the operations of 1412 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1412 may be performed by a processor as described with reference to Figure 11.
  • Figure 15 illustrates a flowchart of a method in accordance with aspects of the present disclosure.
  • the operations of the method 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 may include determining a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values.
  • SL sidelink
  • QoS Quality of Service
  • PRS SL positioning reference signal
  • the method may include transmitting the mapping to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
  • UE user equipment
  • the operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a NE as described with reference to Figure 12.
  • ADR Accumulated Delta-Range
  • a GNSS Assisted GNSS
  • AP Access Point
  • AoD Angle-of-Departure
  • AoA Angle-of-Arrival
  • ARFCN Absolute Radio Frequency Channel Number
  • ARP Antenna Reference Point
  • BFD Beam failure detection
  • BSSID Basic Service Set Identifier
  • BTS Base Transceiver Station (GERAN);
  • BWP Bandwidth Part
  • CBR Channel Busy Ratio
  • CG Configured Grant
  • CID Cell-ID (positioning method); CRS, Cell-specific Reference Signals; CSI, Channel State Information; CSI-RS, Channel State Information Reference Signal; DCI, Downlink Control Information; DL, Downlink; DL-AoD, Downlink Angle-of-Departure; DL-TDOA, Downlink Time Difference Of Arrival; DM-RS, DeModulation Reference Signal; DS-TWR, Double-sided Two Way Ranging; ECEF, Earth-Centered, Earth
  • URA User Range Accuracy
  • UTC Coordinated Universal Time
  • WGS 84 World Geodetic System 1984
  • WLAN Wireless Local Area Network

Landscapes

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

Abstract

Various aspects of the present disclosure relate to a method in a UE, the method comprising: determining one or more SL positioning QoS requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL PRS configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmitting one or more SL PRS according to the one or more SL PRS configurations.

Description

MAPPING SIDELINK POSITIONING REFERENCE SIGNAL PRIORITY IN A WIRELESS COMMUNICATION SYSTEM
TECHNICAL FIELD
[0001] The subject matter disclosed herein relates generally to the field of implementing mapping sidelink (SL) positioning reference signal (PRS) priority in a wireless communication system. This document defines a user equipment (UE) for wireless communication, a processor for wireless communication, a network entity for wireless communication, and methods in a user equipment, processor and network entity.
BACKGROUND
[0002] 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). Additionally, the wireless communications system may support wireless communications across various radio access technologies 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)).
[0003] The introduction of the SL Positioning framework was approved in the 3rd Generation Partnership Project (3GPP) Work Item Description RP-231460, titled “Revised WID on Expanded and Improved NR Positioning”, in order to support the varying target positioning requirements across different use cases listed in Section 2.1.3 thereof. SL positioning is intended to be applied for a variety of use-cases such as vehicle-to-everything (V2X), public safety, industrial Internet of things (IIoT) and commercial use cases. The aim of SL positioning is to determine the absolute/relative position of a UE by using SL positioning methods such as SL round trip time (RTT)-type methods including single-sided and double-sided RTT, SL-angle of arrival (AoA) and SL-time difference on arrival (TDOA). SL positioning will be based on new SL-PRS/s that are transmitted over the PC5 interface and will be supported in all coverage scenarios (i.e., in-coverage, partial coverage and out-of-coverage scenarios) and for PC5 -only-based and joint PC5-Uu-based operation scenarios. And for exchanging the SL positioning related information between UEs over the PC5 interface, a new protocol denoted as sidelink positioning protocol (SLPP) will be introduced.
SUMMARY
[0004] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, 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. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.
[0005] There is provided a user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL-PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmit one or more SL-PRS according to the one or more SL-PRS configurations.
[0006] There is further provided a method in a UE, the method comprising: determining one or more SL positioning QoS requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL PRS configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting, based on the mapping, SL-PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmitting one or more SL-PRS according to the one or more SL-PRS configurations.
[0007] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: input one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL-PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and output one or more SL- PRS according to the one or more SL-PRS configurations.
[0008] There is further provided a method in a processor, comprising: inputting one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and outputting one or more SL PRS according to the one or more SL PRS configurations.
[0009] There is further provided, a network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: determine a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values; and transmit the mapping (which may be in the form of mapping information) to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS. The mapping/mapping information may further comprise of a table or index or vector of (pre-)defined SL PRS priority to SL positioning QoS parameters, or one or more enumerated index values corresponding to one or more (pre-)defined SL PRS priority to SL positioning QoS parameters.
[0010] There is further provided, a method in a network entity, the method comprising: determining a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values; and transmitting the mapping to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure. [0012] Figure 2 illustrates an example of NR beam-based positioning in accordance with aspects of the present disclosure.
[0013] Figure 3 illustrates an example of absolute and relative positioning scenarios in accordance with aspects of the present disclosure.
[0014] Figure 4 illustrates an example of the Multi-Cell RTT procedure in accordance with aspects of the present disclosure.
[0015] Figure 5 illustrates an example of relative range estimation using the existing single gNB RTT positioning framework in accordance with aspects of the present disclosure.
[0016] Figure 6 illustrates an example of a procedure to enable a UE to obtain SL positioning/ranging location results, in accordance with aspects of the present disclosure.
[0017] Figure 7 illustrates an example of a procedure to estimate the relative locations or distances and/or directions between UEs, in accordance with aspects of the present disclosure.
[0018] Figure 8 illustrates an example of a procedure to estimate the relative locations or distances and/or directions between UEs, in accordance with aspects of the present disclosure.
[0019] Figure 9 illustrates an example of SL PRS priority mapping to SL positioning QoS procedures, in accordance with aspects of the present disclosure.
[0020] Figure 10 illustrates an example of a user equipment (UE) 1000 in accordance with aspects of the present disclosure.
[0021] Figure 11 illustrates an example of a processor 1100 in accordance with aspects of the present disclosure.
[0022] Figure 12 illustrates an example of a network equipment (NE) 1200 in accordance with aspects of the present disclosure.
[0023] Figure 13 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure. [0024] Figure 14 illustrates a flowchart of a method performed by a processor in accordance with aspects of the present disclosure.
[0025] Figure 15 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.
DETAILED DESCRIPTION
[0026] Priority has been defined as a key parameter in SL communications as well as for exchanging SL Positioning messages in order to ascertain the urgency of which signals/packets to transmit from a particular UE. Priority of a SL transmission also assists in limiting the congestion control of a SL resource pool, which is especially beneficial to manage the congest! on/traffic load of a SL Communication or Positioning resource pool. The SL priority parameter is used throughout the SL communication stack including layer- 1, layer-2 and higher-layers (above layer-2) and is derived from the standardized PQI table, which is applicable for SL packet/data transmissions.
[0027] However, SL Positioning introduces the transmission of SL PRS for the purposes of determining a target-UE’s absolute/relative position/ranging for distance/ranging for direction. An SL PRS resource is a pseudo-random sequence that is mapped to time-frequency resources (pairs of OFDM symbol, subcarrier) within a slot of a radio frame used for SL PRS transmission. Multiple SL PRS resources can be configured within an SL BWP by means of a number of resource pools. An SL PRS resource pool can be configured as a shared resource pool or as a dedicated resource pool. A shared resource pool can be used for transmission of both SL PRS and PSSCH (SL data or SL-SCH data) whereas a dedicated resource pool can be used only for transmission of SL PRS. With regards to resource allocation of SL PRS, two schemes are supported depending on the coverage scenario.
[0028] Scheme 1 refers to network-controlled SL PRS resource allocation where the gNB manages and schedules the transmission of SL PRS resources. According to this scheme a UE that requires to transmit SL PRS sends a request for specific SL PRS resource character! stic(s)/SL PRS resource configuration(s) to the gNB and receives an SL PRS resource allocation signaling from the gNB through a dynamic grant (provided via DCI), configured grant type 1 (provided via RRC) or configured grant type 2 (provided via PDCCH). The request from the UE may be sent to gNB via L2 MAC CE or RRC message.
[0029] Scheme 2 refers to UE autonomous SL PRS resource allocation where the UE autonomously selects the SL PRS resources for transmission. According to this scheme the UE firstly defines a selection window (consisting of number of slots) and identifies candidate SL PRS resources within the selection window. Afterwards, the UE senses the identified candidate SL PRS resources during a defined sensing window (consisting of number of slots) to determine which of the SL PRS resources are available. Finally, the UE selects randomly an SL PRS resource among the set of available SL PRS resources. SL PRS transmission can be triggered either by the UE itself or a UE-A can request a UE-B to transmit SL PRS (either by LI SCI or L2 MAC CE).
[0030] In both resource allocation schemes the SL PRS priority will be taken as key parameter into account for selecting SL PRS resources. It has also been determined that 8 priority levels for SL PRS priority are to be defined, which is the same as the number of priority levels for SL-SCH (applicable for SL data transmissions). However, the problem of how to map these priority levels to SL Positioning QoS has not been addressed yet since the prior art assumes that the priority levels are defined based on the V2X/ProSe service type. In order to avoid UE implementations that assign arbitrarily high priorities to SL PRS transmissions, a standardized mapping of SL PRS priority levels to SL Positioning QoS associated to a Location Service (LCS) request is necessary.
[0031] In view of these problems, the disclosure herein presents systems, apparatuses and methods for unifying the mapping between SL PRS priority and the desired SL Positioning QoS based on the received/triggered LCS request (e.g, SL-MT-LR or SL-MO- LR). The embodiments presented herein aim to address the issue that currently presents itself with SL PRS transmission priority, wherein there is currently no mechanism that maps 8 levels of priority to a given SL Positioning QoS contained within an LCS request. Such a mapping has to be configured or pre-configured to a UE in order for the UE to assign a specified priority for requesting or selecting a particular SL PRS transmission within a resource pool that is configured to transmit SL PRS. [0032] This present disclosure details solutions for mapping the SL PRS priority as a function of the SL Positioning QoS according to different configuration scenarios. Methods are provided to describe various mechanisms to map the SL PRS priority to different SL Positioning QoS parameters. Furthermore, methods are provided to configure (i.e., preconfigure or configure) a consolidated SL PRS priority mapping table. In addition, methods are provided to enable the procedures to map the SL PRS priority with the received SL Positioning QoS at the UE/device.
[0033] The embodiments described herein may be implemented in combination with each other to support SL positioning assistance data delivery without and with location server involvement.
[0034] For the purposes of this disclosure, a positioning-related reference signal may be referred to as a reference signal used for positioning procedures/purposes in order to estimate a target-UE’s location, e.g., PRS, or based on existing reference signals such as CSLRS or SRS; a target-UE may be referred to as the device/entity to be localized/positioned. In various embodiments, the term ‘PRS’ may refer to any signal such as a reference signal, which may or may not be used primarily for positioning.
[0035] For the purposes of this disclosure any reference made to position/location information/estimates may refer to either an absolute position, relative position with respect to another node/entity, ranging in terms of distance, ranging in terms of direction or combination thereof.
[0036] The consideration of accuracy can be separate when evaluating horizontal and vertical position estimates. While certain location services may demand a certain precision in both dimensions, other services might necessitate accuracy in only one dimension, i.e., horizontal or vertical, or in other cases demand a higher precision in one dimension while accepting a lower degree of accuracy in the other.
[0037] The precision required for location services can be described using a range of values that indicate the typical level of accuracy required for a specific application, which in turn affects the SL PRS configuration required to achieve the said accuracy, e.g., in terms of comb-size including number of symbols and Resource element offset, bandwidth, and so forth. Various services have distinct demands when it comes to positioning accuracy. This range can extend from several meters (for navigation services) to potentially several kilometers (for fleet management).
[0038] Aspects of the present disclosure are described in the context of a wireless communications system.
[0039] Figure 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. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, 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. 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.
[0040] 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 radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (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. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface. [0041] 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. For example, 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. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, 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.
[0042] 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. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.
[0043] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0044] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, 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).
[0045] The CN 106 may support user authentication, access authorization, tracking, connectivity, location services, 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)) or a control and user plane entity, e.g., Location Management Function (LMF), that is responsible for providing location services. In some implementations, the 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.
[0046] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, 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).
[0047] In the wireless communications system 100, 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). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, 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.
[0048] 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 numerology (e.g., /t=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., /t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., //=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., /t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0049] A time interval of a resource (e.g., a communication 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. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a l ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0050] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, 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. For instance, the first, second, third, fourth, and fifth numerologies (i.e., /t=0, /t=l, =2, jtz=3, =4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0051] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, 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). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0052] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., //=1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., g=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /t=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /z=3), which includes 120 kHz subcarrier spacing.
[0053] NR positioning based on NR Uu signals and SA architecture (e.g., beam-based transmissions) was first specified in 3GPP Rel-16. The targeted use cases also included commercial and regulatory (emergency services) scenarios as in 3GPP Rel-15. The performance requirements, as discussed in the 3GPP TR 38.855 titled “Study on NR positioning support (Release 16) ”, are provided in Table 1.
Figure imgf000016_0001
Table 1
[0054] 3 GPP Rel-17 Positioning has recently defined the positioning performance requirements for Commercial and IIoT use cases in 3GPP TR 38.857, titled “Study on NR Positioning Enhancements (Release 17) ” . These requirements are provided in Table 2.
Figure imgf000016_0002
Table 2 [0055] In the case of SL Positioning, various requirements were defined capturing a variety of use cases in 3GPP TR 38.859 titled, “Study on expanded and improved NR positioning” . These requirements are provided in Table 3.
Figure imgf000017_0001
Figure imgf000017_0002
Table 3 [0056] The supported positioning techniques as of 3GPP Rel-16 are discussed in 3GPP TS 38.305 titled, “Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN”, and are provided in Table 4.
Figure imgf000018_0001
Table 4
[0057] Separate positioning techniques as indicated in Table 4 can be currently configured and performed based on the requirements of the LMF and UE capabilities. The transmission of Uu (uplink and downlink) Positioning Reference Signals (PRS) enable the UE to perform UE positioning-related measurements to enable the computation of a UE’s absolute location estimate and are configured per Transmission Reception Point (TRP), where a TRP may include a set of one or more beams. A conceptual overview is illustrated in Figure 2.
[0058] Figure 2 illustrates an example 200 of NR beam-based positioning in accordance with aspects of the present disclosure. [0059] The example 200 shows a first gNB/TRP 210 illustrated as ‘gNB 1-TRP 1’. The first gNB/TRP 210 is shown with a plurality of beams 211 having a Resource Set ID#0. The first gNB/TRP 210 is shown with a plurality of beams 212 having a Resource Set ID#1. Each beam in the pluralities of beams 211, 212 may represent DL-PRS resources.
[0060] A second gNB/TRP 220 is also shown, illustrated as ‘gNB 2-TRP 1’. The second gNB/TRP 220 also comprises a plurality of beams 221 having a Resource Set ID#0 and a plurality of beams 222 having a Resource Set ID#1. Again, each beam in the plurality of beams 221, 222 may represent DL-PRS resources.
[0061] A third gNB/TRP 230 is also shown, illustrated as ‘Reference/serving gNB 3- TRP1’. The third gNB/TRP 230 also comprises a plurality of beams 231 having a Resource Set ID#0 and a plurality of beams 232 having a Resource Set ID#1. Again, each beam in the plurality of beams 231, 232 may represent DL-PRS resources.
[0062] A location server/LMF 240 is also shown. The first gNB/TRP 210, second gNB/TRP 220 and third gNB/TRP all interface with the location server/LMF 240 using NRPPa.
[0063] According to 3GPP Rel-16, the PRS can be transmitted by different base stations (serving and neighboring) 210, 220, 230 using narrow beams 211, 212, 221, 222, 231, 232 over FR1 and FR2 as illustrated in Figure 2, which is relatively different when compared to LTE where the PRS was transmitted across the whole cell. The PRS can be locally associated with a PRS Resource ID and Resource Set ID for a base station (TRP) 210, 220, 230. Similarly, UE positioning measurements such as Reference Signal Time Difference (RSTD) and PRS RSRP measurements are made between 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. In addition, there are additional UL positioning methods for the network to exploit in order to compute the target UE’s location. Table 5 and Table 6 show the reference signal to measurements mapping required for each of the supported RAT- dependent positioning techniques at the UE and gNB, respectively. The measurements mapping is further detailed in 3GPP TS 38.215- titled, “Physical-layer Measurements” . [0064] RAT-dependent positioning techniques involve the 3 GPP RAT and core network entities to perform the position estimation of the UE, which are differentiated from RAT-independent positioning techniques which rely on GNSS, IMU sensor, WLAN and Bluetooth technologies for performing target device (UE) positioning.
Figure imgf000020_0001
Table 5
Figure imgf000020_0002
Table 6 [0065] Figure 3 illustrates an example 300 of absolute and relative positioning scenarios as defined in the system architectural (stage 1) study reported in 3 GPP TR 22.832, titled “Study on enhancements for cyber-physical control applications in vertical domains”. The example 300 shows Relative Positioning, variable coordinate system 310; Relative Positioning, variable and moving coordinate system 320; and Absolute Positioning, fixed coordinate systems 330.
[0066] In the Relative Positioning, variable coordinate system 310 scenario, relative positioning may be performed between a UE 311 and 5G positioning nodes (i.e., gNB 1 312) within 10m of each other (see 3GPP TS 22.261). Furthermore, relative positioning may be performed between two UEs 313, 314 that are within 10m of each other (see 3 GPP TS 22.261). The vertical location of a UE3 315 is shown as being provided in terms of relative height/depth to local ground (see 3GPP TS 22.071).
[0067] In the Relative Positioning, variable and moving coordinate system scenario 320, the relative lateral position accuracy may be 0.1m between UEs supporting V2X application (see 3GPP TS 22.186). The relative longitudinal position accuracy may be less than 0.5m for UEs supporting V2X application for platooning in proximity (see 3GPP TS 22.186).
[0068] In the absolute positioning, fixed coordinate system scenario 330, three fixed gNBs 331, 332, 333 are shown in addition to a UE 334. Positioning is performed between the gNBs 331, 332, 333 and the UE 334.
[0069] The example 300 also shows an out of coverage scenario 340 wherein positioning information for a UE 341 that is out of coverage of the network is obtained relative to other UEs 342 that are in proximity or in coverage of the network (see 3GPP TS 22.104).
[0070] A number of RAT-dependent positioning techniques are supported in 3 GPP Rel-
16 and 3GPP Rel-17. These are discussed in 3GPP TS 38.305 titled, “Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN” . A brief description of these positioning techniques is provided below. [0071] The DL-TDOA positioning method makes use of the DL RSTD (and optionally DL PRS RSRP) of downlink signals received from multiple TPs, at the UE. The UE 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 in relation to the neighboring TPs.
[0072] The DL AoD positioning method makes use of the measured DL PRS RSRP of downlink signals received from multiple TPs, at the UE. The UE 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 in relation to the neighboring TPs.
[0073] The Multi-RTT positioning method makes use of the UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs, measured by the UE and the measured gNB Rx-Tx measurements and UL SRS-RSRP at multiple TRPs of uplink signals transmitted from UE. The UE 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 RTT at the positioning server which are used to estimate the location of the UE. Multi-RTT is only supported for UE- assisted/NG-RAN assisted positioning techniques. Figure 4 illustrates an example 400 of the Multi-Cell RTT procedure in accordance with aspects of the present disclosure. The example 400 shows UE Tx UL-SRS beginning at a time tO; gNB Rx UL-SRS beginning at a time tl; gNB Tx DL-PRS beginning at a time t2; and UE Rx DL-PRS beginning at a time t4. The time period ‘A’ is shown as being equal to the difference between t3 and tO. The time period ‘B’ is shown as being equal to the difference between t2 and tl. The RTT is shown as being equal to A minus B.
[0074] Figure 5 illustrates an example 500 of relative range estimation using the existing single gNB RTT positioning framework in accordance with aspects of the present disclosure. The example 500 shows a target UE1 510, a target UE2 520, a target UE3 530, a gNB 540 and an LMF 550. The UEs 510, 520, 530 communicate with the gNB 540 using DL-PRS and UL-SRS. The LMF 550 determines the distance between the gNB 540 and UE 510, 520, 530, as being equal to the speed of light multiplied by half of the round trip time (RTT). Multi-RTT can be used to obtain an absolute location. Relative range may be calculated based on absolute positions. The example 500 is an implementation-based approach to compute the relative distance between two UEs. This approach is high in latency and is not an efficient method in terms of procedures and signalling overhead.
[0075] Further RAT-dependent positioning techniques supported in 3 GPP Rel-16 and 3GPP Rel-17, will now be discussed.
[0076] In the Enhanced Cell ID (CID) positioning method, the position of an UE is estimated with the knowledge of its serving ng-eNB, gNB and cell, and is based on LTE signals. The information about the serving ng-eNB, gNB and cell may be obtained by paging, registration, or other methods. NR Enhanced Cell ID (NR E-CID) positioning 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. Although NR E-CID positioning may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE 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 reports the measurements that it has available rather than being required to take additional measurement actions.
[0077] The UL TDOA positioning method makes use of the UL RTOA (and optionally
UL SRS-RSRP) at multiple RPs of uplink signals transmitted from UE. The RPs measure the UL RTOA (and optionally UL SRS-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 estimate the location of the UE.
[0078] The UL AoA positioning method makes use of the measured azimuth and the zenith of arrival at multiple RPs of uplink signals transmitted from an UE. The RPs measure A-AoA and 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.
[0079] Certain SL positioning procedures will now be described that are provided in 3GPP TS 23.273, titled “5G System (5GS) Location Services (LCS) ”, Stage 2 (Release 18), and in 3GPP TS 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning” , Release 18.
[0080] In the first instance the procedures of SL-MO-LR involving the LMF will be briefly described. Figure 6 illustrates an example 600 of a procedure to enable a UE to obtain SL positioning/ranging location results using one or more other UEs with the assistance of an LMF in a serving PLMN for the UE, in accordance with aspects of the present disclosure. The Ranging/SL Positioning location results referred to may include absolute locations, relative locations or distances and directions, depending on the service request. If the Target UE decides to initiate the SL-MO-LR procedure, it includes one or multiple SL reference UE(s) / Located UE (s) in the service request. See the 3 GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” for more information on how this generic procedure can be used.
[0081] The example 600 shows a UE1 630, a plurality of UEs UE2 640-UEn 645, an AMF 650, an LMF 660, a PCF 670, a GMLC 680 and a NEF/AF or LCS Client 690. The various message flows 601-623 shown in the example 600 will now be described.
[0082] As a precondition for the example 600, UE1 630 is in coverage and registered with a serving PLMN. UEs 2 to n 640, 645 may or may not be in coverage and, if in coverage, may or may not be registered with the same serving PLMN as UE1 630.
[0083] In a first step 601, the procedures and signalling specified in clause 6.2 of the 3 GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” may be used to provision the Ranging/SL positioning service authorization and policy/parameter provisioning to UEs 1 to n 630, 640, 645, when in coverage. This is shown as, Ranging/SL positioning service authorization and policy/parameter provisioning [0084] If indication of UE-only operation is received, procedures of Ranging/Sidelink Positioning control as defined in clause 6.8 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” is performed.
[0085] In a further step 602, based on a trigger of service request (e.g., received from the application layer), which includes UEl/.../UEn 630, 640, 645, UE discovery is performed for Ranging/SL positioning as specified in clause 6.4 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” . This is shown as ‘UE discovery If UE1 630 is the target UE, UE1 630 discovers UEs 2 to n 640, 645. If UE1 630 is the Located UE, the target UE (i.e., one of the UEs 2 to n 640, 645) discovers UE1 630 (and other Located UEs in the set of UEs 2 to n 640, 645).
[0086] In a further step 603, secure groupcast and/or unicast links are established between UEs 1 to n 630, 640, 645 as defined in clause 5.3 of the 3 GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” . This is to enable UE1 630 to exchange Ranging and Sidelink Positioning Protocol (RSPP) messages over PC5-U reference point with each of UEs 2 to n 640, 645 and possibly enabling UEs 2 to n 640, 645 to exchange RSPP over PC5-U between each other. This is shown as, ‘establish secure links
[0087] In a further step 604, UE1 630 and UEs 2 to n 640, 645 may communicate over PC5 for authorization of Ranging/SL positioning and receiving QoS parameters if needed. Each of UEs 630, 640, 645 verifies that Ranging/SL positioning is permitted, including whether Ranging/SL positioning results may be transferred to an LCS Client or AF 690 if this is used, according to any service authorization and policy/parameter provisioning received at step 601. QoS requirements for the Ranging/SL positioning may be also provided based on QoS requirements in the service request. This is shown as, ’notify and verify ranging/SL positioning
[0088] In a further step 605, UE1 630 may obtain the Sidelink positioning capabilities of UEs 2 to n 640, 645 using the groupcast and/or unicast links established in step 603. This is shown as, ‘Capability Exchange [0089] The steps 604 and 605 may be performed to transfer the information of UEs which are not served by the LMF 660. It should be noted that UE2-UEn 640, 645 is not assumed to be served by the same LMF 660 serving UE1 630.
[0090] In a further step 606, based on the Sidelink positioning capabilities of UEl-UEn 630, 640, 645, the target UE determines SL-MO-LR is to be performed. If UE1 630 is the Located UE (i.e., when the target UE is one of UE2-UEn 640, 645, and does not have NAS connection), the target UE initiates a SL-MO-LR service request to UE1 630. This is shown as, ‘Determine SL-MO-LR
[0091] In a further step 607, if UE1 630 is in CM-IDLE state, UE1 630 instigates a UE triggered Service Request in order to establish a signalling connection with the serving AMF 650 of UE1 630. This is shown as, ‘UE triggered service request’.
[0092] In a further step 608, if UE1 630 sends a supplementary services SL-MO-LR request to the serving AMF 650 in an UL NAS TRANSPORT message. The SL-MO-LR request indicates the other UEs 2 to n 640, 645 (using application layer ID and/or GPSI), indicates any assistance data needed, indicates whether location calculation assistance is needed, and indicates whether location results should be transferred to an LCS client or AF 690. The message shall include the identity of the LCS client or the AF 690 and may include the address of the GMLC 680 through which the LCS client or AF (via NEF) 690 should be accessed. In addition, a Service Type indicates which MO-LR service of the LCS Client 690 is requested by the UE may be included. For location calculation assistance from the LMF 660, the preferred type of Sidelink positioning/ranging location results (e.g., absolute locations, relative locations or distances and directions between pairs of UEs 630, 640, 645) and the required QoS are included. If UE1 630 is a Located UE and one of UE2- UEn 640, 645 is the target UE that does not have NAS connection, the supplementary services SL-MO-LR request includes an indication that one of UE2-UEn 640, 645 is the target UE instead of UE1 630. This is shown as, ‘UL NAS TRANSPORT (SL-MO-LR Request)
[0093] In a further step 609, the serving AMF 650 selects an LMF 660 serving UE1 630 (e.g., an LMF \660 that supports Sidelink positioning/ranging) and sends an Nlmf Location DetermineLocation service operation towards the LMF 660 with the information from the SL-MO-LR Request. The service operation includes a LCS Correlation identifier. This is illustrated as, ‘Nlmf Location DetermineLocation Request’ .
[0094] In a further step 610, the LMF 660 sends a request to UE1 630 for the capabilities of UEs 1 to n 630, 640, 645. It should be noted that UE2-UEn 640, 645 is not assumed to be served by the same LMF 660 serving UE1 630. This is illustrated as, ‘Capabilities Request for UEs 1 to n ’.
[0095] In a further step 611, the UE1 630 returns its capabilities to the LMF 660. UE1 630 may additionally return the capabilities of the UEs obtained at step 605 if requested by the LMF 660 at step 610. This is illustrated as, ‘Capabilities Response for UEs 1 to n ’.
[0096] In a further step 612, UE1 630 may send a request for specific assistance data to the LMF 660. This is illustrated as, ‘sharing Assistance data for UEs ’.
[0097] In a further step 613, LMF 660 sends the requested assistance data to UE1 630, and UE1 630 forwards the assistance data received from LMF 660 to UE2-UEn 640, 645. The assistance data may assist UEs 1 to n 630, 640, 645 to obtain Sidelink location measurements at step 615 and/or may assist UE1 630 to calculate Sidelink positioning/ranging location results at step 616. The step 613 is also illustrated as, ‘sharing Assistance data for UEs ’.
[0098] It should be noted that steps 610 and 611 can be omitted if UE1 630 includes a message containing the capabilities of UEs 1 to n 630, 640, 645 in the SL-MO-LR request at step 608. Step 612 can be omitted if UE1 630 includes a message containing the request for specific assistance data in the SL-MO-LR request at step 608.
[0099] In a further step 614, if the SL-MO-LR request at step 608 indicated location calculation assistance is needed and/or indicated transfer of Sidelink positioning/ranging location results to an LCS Client or AF 690, the LMF 660 sends a request for location information to UE1 630 and may also send a request for location information to UE2-UEn 640, 645 if it is served by the LMF 660. If LMF 660 determines to apply UE based SL Positioning, LMF 660 includes in the request the indication of UE based SL Positioning. LMF 660 may also provide the list of candidate Located UE(s), if absolute location is requested at step 608. If scheduled location time is received at step 614, LMF 660 may include a scheduled location time. This step 614 is shown as, ‘Request Location Information for UEs 1 to n ’.
[0100] In a further step 615, UE1 630 instigates a Sidelink positioning/ranging procedure among UEs 1 to n 630, 640, 645 in which UEs 1 to n 630, 640, 645 obtain Sidelink location measurements and UEs 2 to n 640, 645 transfer their Sidelink location measurements to UE 1 630 and/or to the LMF 660 (depending on the assistance requested). If scheduled location time is received at step 614, Sidelink positioning/ranging is performed at the scheduled location time. This step 615 is shown as, ‘Sidelink positioning/ranging procedure ’.
[0101] In a further step 616, if Target UEs absolute location information is required at step 608 and if absolute location of Located UE(s) is not available, the Target UE sends a request to the Located UE(s) to trigger 5GC-MO-LR procedure to let the Located UE(s) acquire their own absolute location. The QoS requirement received at step 608 is included in the request, which is used to derive the QoS for Located UE(s) positioning. This is shown as, ‘UE1... UEn 5GC-MO-LR procedures ’.
[0102] In a further step 617, if LMF 660 determines to use UE based calculation, at least one of UEl-UEn 630, 640, 645 calculates Sidelink positioning/ranging location results based on the Sidelink location measurements obtained at step 615 and possibly using assistance data received at step 613. The Sidelink positioning/ranging location results can include absolute locations, relative locations or ranges and directions related to the UEs 1 to n 630, 640, 645. This is shown as, ‘Calculate Location Results for UEs 1 to n ’.
[0103] In a further step 618, if UE1 630 received a request for location information at step 614, UE1 630 sends a response to the LMF 660 and includes the Sidelink location measurements obtained at step 615, the Sidelink positioning/ranging location results obtained at step 617 if step 617 was performed, or Located UEs absolute location obtained at step 616. This is shown as, ‘Provide Location Information for UEs 1 to n ’.
[0104] In a further step 619, if Target UEs absolute location information is required at step 608 and if absolute location of Located UE(s) is not received at step 618, LMF 660 can either retrieved the location of the Located UE(s) locally or triggers 5GC-MT-LR procedure to the GMLC 680 to acquire the absolute location of the Located UE(s) using Application Layer ID or GPSI of the Located UE(s). LMF 660 includes the QoS requirement received at step 608 in the request, which is used to derive the QoS for Located UE(s) positioning. If scheduled location time is used, LMF 660 includes the scheduled location time in the request to GMLC 680. This is shown as, ‘UE1... UEn TGC-MT-LR procedures
[0105] In a further step 620, the LMF 660 calculates Sidelink positioning/ranging location results for UEs 1 to n 630, 640, 645 from the Sidelink location measurements received at step 618 and absolute location of Located UE(s) at step 619. The Sidelink positioning/ranging location results can include absolute locations, relative locations or ranges and directions related to the UEs 1 to n 630, 640, 645, depending on the location request received in step 608. This is illustrated as, ‘Calculate Location Results for UEs 1 to n
[0106] In a further step 621, the LMF 660 returns an
Nlmf Location DetermineLocation service operation response to the AMF 650 and includes the Sidelink positioning/ranging location results received at step 618 or calculated at step 620. This is shown as, ‘Nlmf Location DetermineLocation Response
[0107] In a further step 622, if Sidelink positioning/ranging location results were received at step 621, the AMF 650 performs steps 607-612 of clause 6.2 of the 3GPP Technical Specification 23.273 titled “5G System (5GS) Location Services (LCS) Stage 2 (Release 18) ” to send the Sidelink positioning/ranging location results to the GMLC 680 and to an AF or LCS Client 690 if this was requested at step 608. The Sidelink positioning/ranging location results include the identities for the respective UEs 1 to n 630, 640, 645 received at step 608. This is shown as, ‘Transfer Location Results to GMLC and optionally to AF or LCS Client
[0108] It should be noted that sending location results and global identities for UEs 1 to n 630, 640, 645 to an AF or LCS Client 690 may require privacy verification from UEs 1 to n 630, 640, 645 and/or from the HPLMNs of UEs 1 to n 630, 640, 645. [0109] In a further step 623, the LMF 660 returns a supplementary services SL-MO-LR response to UE1 630 in a DL NAS TRANSPORT message and includes any Sidelink positioning/ranging location results calculated at step 620 if step 620 was performed. If UE1 630 is a Located UE, and the target UE is one of the UEs 2 to n 640, 645 and does not have NAS connection, then UE1 630 may transfer the Sidelink positioning/ranging location results to the target UE.
[0110] The procedures of SL-MT-LR involving the LMF will be briefly described. Figure 7 illustrates an example 700 of a procedure to estimate the relative locations or distances and/or directions between UEs, in accordance with aspects of the present disclosure. The example 700 shows a UE1 730, a plurality of UEs denoted UE2-UEn 740, 745, an AMF 750, an NG-RAN 755, an LMF 760, a VGMLC 780, a HGMLC 785, a NEF/AF or LCS Client 790 and a UDM 795. More specifically, the example 700 shows a procedure to enable an LCS Client or AF 790 to obtain Ranging/Sidelink Positioning location results for a group of n UEs (n^2), i.e., UE1, UE2, ..., UEn 730, 740, 745. In the procedure, the GMLC 4780, 785 determines a UE among the n UEs to be designated UE1 (i.e. Target UE in the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” and one or more other UEs designated UE2, UE3, ..., UEn (n 5=2) (i.e. Reference/Located UEs in the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ”). The Ranging/Sidelink Positioning location results may include absolute locations, relative locations or ranges and directions related to the UEs 730, 740, 745, based on the service request. The procedure for periodic and triggered SL-MT-LR is defined in clause 6.20.4 of the 3GPP TS 23.273, titled “5G System (5GS) Location Services (LCS) ”, Stage 2 (Release 18). The various message flows 701-720 will now be discussed. As a precondition, at least one of the n UEs 730, 740, 745 is in coverage and registered with a serving PLMN.
[0111] In a first step 701, the LCS Client or the AF (via NEF) 790 sends an LCS service request to the (H)GMLC 785 for Ranging/Sidelink Positioning location results for the n UEs 730, 740, 745 which may each be identified by a GPSI or a SUPI. The request may include the required QoS, the required location results (e.g., absolute locations, relative locations or distances and/or directions related to the UEs 730, 740, 745), the SL reference UE(s) in case of relative locations, distance, or direction. The (H)GMLC 785 or NEF 790 authorizes the LCS Client or the AF 790 for the usage of the LCS service. If the authorization fails, the remaining steps are skipped and the (H)GMLC 785 or NEF 790 responds to the LCS Client or the AF 790 with the failure of the service authorization. This is shown as, ‘LCS Service Request’. In addition, an Application Layer ID shall be included for each of the n UEs 730, 740, 745 to enable discovery of the UEs 730, 740, 745 at step 712.
[0112] In a further step 702, the (H)GMLC 785 invokes a Nudm SDM Get service operation towards the UDM 795 of each of the n UEs 730, 740, 745 to get the privacy settings of the UE identified by its GPSI or SUPI. The UDM 795 returns the UE Privacy setting of the UE. The (H)GMLC 785 checks the UE LCS privacy profile. This is illustrated as, ‘Nudm SDM Get
[0113] In a further step 703, the (H)GMLC 785 invokes a Nudm UECM Get service operation towards the UDM 795 of each of the n UEs 730, 740, 745 (for which GPSI or SUPI is available), one at a time, using the GPSI or SUPI of each UE 730, 740, 745. The (H)GMLC 785 selects the UE 730, 740, 745 (e.g., which is treated as UE1 in following steps) that initiates the Ranging/SL Positioning and selects the corresponding serving AMF 750. This is illustrated as, ‘Nudm UECM Get’ .
[0114] The UDM 795 is aware of the serving AMF 750 address as UE registration on an AMF 750 as defined in clause 4.2.2.2.2 of 3GPP TS 23.502. The UDM 795 is aware of a serving (V)GMLC 780 address at UE registration on an AMF 750 as defined in clause 4.2.2.2.2 of 3GPP TS 23.502.
[0115] In a further step 704, for a non-roaming case, this step is skipped. In the case of roaming, the (H)GMLC 785 may receive an address of a (V)GMLC 780 (together with the network address of the current serving AMF 750) from the UDM 795 in step 703, otherwise, the (H)GMLC 785 may use the NRF service in the (H)PLMN to select an available (V)GMLC 780 in the (V)PLMN, based on the (V)PLMN identification contained in the AMF 750 address received in step 703. The (H)GMLC 785 then sends the location request to the (V)GMLC 780 by invoking the Ngmlc Location ProvideLocation service operation towards the (V)GMLC 780. In the cases when the (H)GMLC 785 did not receive the address of the (V)GMLC 780, or when the (V)GMLC 780 address is the same as the (H)GMLC 785 address, or when both PLMN operators agree, the (H)GMLC 785 sends the location service request message to the serving AMF 750. In this case, step 704 is skipped. The (H)-GMLC 785 also provides the LCS client type of AF 790, if received in step 701, or LCS client type of LCS client 790 and other attributes to be sent to AMF 750 in step 705. The step 704 is shown as, ‘Ngmlc Location ProvideLocationRequest’.
[0116] In a further step 705, in the case of roaming, the (V)GMLC 780 first authorizes that the location request is allowed from this (H)GMLC 785, PLMN or from this country. If not, an error response is returned. The (H)GMLC 785 or (V)GMLC 780 invokes the Namf Location ProvidePositioninglnfo service operation towards the AMF 750 serving UE1 730 to request Sidelink positioning/ranging location results of the n UEs 730, 740, 745. The service operation includes the SUPI of UE1 730, Application layer IDs of the UEs 730, 740, 745, the client type and may include the required LCS QoS, the required location results (e.g., relative locations or ranges and directions related to the UEs) and other attributes as received or determined in step 701. This is shown as, ‘Namf Location ProvidePositioninglnfo Request
[0117] In a further step 706, if UE1 730 is in CM-IDLE state, the AMF 750 initiates a network triggered Service Request procedure to establish a signalling connection with UE1 730. This is shown as, ‘Network Triggered Service Request’.
[0118] It should be noted that if signalling connection establishment fails, steps 707- 717 are skipped.
[0119] In further steps 707-708, if the indicator of privacy check indicates an action is needed, then same operation as that of step 707-708 of clause 6.1.2 of the 3GPP Technical Specification 23.273 titled “5G System (5GS) Location Services (LCS) Stage 2 (Release 18) ” is carried out. These steps are shown as, ‘NAS Location Notification Invoke Request ’ and NAS Location Notification Return Result
[0120] In a further step 709, the serving AMF 750 selects an LMF 760 serving UE1 730 (e.g., an LMF 760 that supports Ranging/Sidelink Positioning) and sends an Nlmf Location DetermineLocation service operation towards the LMF 760 with the information received at step 705 e.g., required location results (e.g., relative locations or ranges and directions between pairs of UEs), SL reference UE(s) in case of relative locations, Application layer IDs of the UEs if received in step 705. The service operation includes a LCS Correlation identifier. This is illustrated as, ‘Nlmf Location DetermineLocation Request
[0121] In a further step 710, the LMF 760 sends an SL-MT-LR request to the serving AMF s750 as a supplementary services message, using the Namf_Communication_NlN2MessageTransfer service operation, and the session ID parameter is set to the LCS Correlation identifier. This is illustrated as,
‘ Namf Communication N !N2MessageTransfer (SL-MT-LR Request, Correlation ID
[0122] The SL-MT-LR request may include the application layer IDs of the other UEs 2 to n 740, 745, the types of required location results (e.g., relative locations or distances and/or directions) and SL reference UE(s) in case of relative locations.
[0123] In the further step 711, the serving AMF 750 forwards the SL-MT-LR request and a Routing identifier equal to the LCS Correlation identifier to UE1 730 using a DL NAS TRANSPORT message. This is illustrated as, ‘DL NAS TRANSPORT (SL-MT-LR Request, Routing ID)
[0124] In a further step 712, UE1 730 attempts to discover the other UE 2 to n 740, 745 using their Application Layer IDs if not already discovered using procedure defined in clause 6.4 of the 3GPP Technical Specification 23.586 titled ‘Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ” . This step 712 is referred to as, ‘UE1 discovers UEs 2 to n ’.
[0125] In a further step 713, the UE1 730 obtains the sidelink positioning capabilities of the discovered UEs via the SLPP if not already obtained. This is referred to as, ‘UE1 obtains capabilities for discovered UEs
[0126] In a further step 714, the UE1 730 returns a supplementary services SL-MT-LR response to the serving AMF 750 in an UL NAS TRANSPORT message and includes the Routing identifier received in step 711. This is illustrated as, ‘UL NAS TRANSPORT (SL- MT-LR Response, Routing ID) The SL-MT-LR response indicates which of UEs 2 to n 740, 745 have been discovered and the sidelink positioning capabilities of the discovered UEs.
[0127] In a further step 715, the serving AMF 750 forwards the SL-MT-LR response to the LMF 760 indicated by the Routing identifier received at step 714 and includes a LCS Correlation identifier equal to the Routing identifier. This is shown as,
‘Namj Communication N IMessageNotify (SL-MT-LR Response, Correlation ID)
[0128] In a further step 716, Ranging/Sidelink Positioning of UE1 730 and the other discovered UEs occurs as for an SL-MO-LR as described for steps 710-719 of Figure 6.20.1-1 of the 3GPP Technical Specification 23.273 titled “ 5G System (5GS) Location Services (LCS) Stage 2 (Release 18) ” with the difference that Ranging/Sidelink Positioning location measurement data or results are always returned to the LMF 760 and the LMF 760 indicates to UE1 730 at step 713 or step 714 whether the Ranging/Sidelink Positioning location results will be calculated by the LMF 760 (at step 719) or by UE1 730 (at step 717). For some undiscovered UEs among the other UEs 2 to n 740, 745, the LMF 760 interacts with GMLC 780, 785 to initiate the 5GC -MT-LR procedure for UE2 to n 740, 745 to get their absolute locations, and calculates the relative locations or distances and/or directions related to the UEs. This is illustrated as, ‘Sidelink Positioning/Ranging of UEs 1 to n
[0129] In further steps 717-720, the LMF 760 returns the Sidelink positioning/ranging location results to the LCS Client or AF 790 as in steps 713-715 and step 724 of clause 6.1.2 of the 3GPP Technical Specification 23.273 titled “ 5G System (5GS) Location Services (LCS) Stage 2 (Release 18) ” . The results also include failure information of the UE(s) that was not discovered. These respective steps are shown as,
‘Nlmf Location DetermineLocation Response ’, ‘Namf Location ProvidePositioninglnfo Response ’, ‘Ngmlc Location ProvideLocation Response ’, and, ‘LCS Service Request'.
[0130] The procedures of ranging/ sidelink positioning control will now be briefly described. Either UE-only Operation or Network-based Operation is applied in the Ranging/Sidelink Positioning control procedures. UE-only Operation as specified in this clause is applied for the following cases: Neither Target UE nor SL Reference UE is served by NG-RAN; Network-based Operation is not supported by the 5GC network; SL-MO-LR request is rejected by the network.
[0131] When Network-based Operation is not supported by the 5GC network, indication on whether the UE is allowed to use UE-only operation to perform Ranging/ SL Positioning is included in the Policy /Parameter provisioned to UE as defined in clause 5.1.1.2 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) ”, and is provisioned to the UE as defined in clause 5.1.1.1 of the 3 GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) The Target UE will take it into account to initiate a UE-only operation procedure, or any other cases, Network-based Operation as specified in clauses 6.20 of the 3GPP TS 23.273, titled “5G System (5GS) Location Services (LCS) ”, Stage 2 (Release 18) is applied.
[0132] Figure 8 illustrates an example 800 of a procedure to estimate the relative locations or distances and/or directions between UEs, in accordance with aspects of the present disclosure. More specifically, Figure 8 shows procedures for Ranging/Sidelink Positioning control (UE-only operation). Shown are a SL Positioning Client UE 810, a SL Positioning Server UE 820, a UE1 830 and a UE2/. . ,/UEn 840. The various messaging flows 801-809 will now be described.
[0133] In a first step 801, the UE1 830 (i.e., Target UE) may receive a Ranging/SL Positioning Service request from either of a SL Positioning client UE 810 (in accordance with step 801a) or a RSPP application layer (in accordance with step 801b).
[0134] In the step 801a, the SL Positioning Client UE 810 provides the request over PC5 during procedures for Ranging/SL Positioning service exposure though PC5 as defined in clause 6.7.1.1 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18). For absolute location, the service request includes the SL Positioning Client UEs user info and Target UEs user info, and required positioning QoS. For relative location or ranging information, the service request includes the SL Positioning Client UEs user info, Target UEs user info, SL Reference UEs user info(UE2/.../UEn), and Ranging/SL Positioning QoS information. This step is shown as, ‘Ranging/SL Positioning service request over PC5 ’.
[0135] In the step 801b, the request is from the RSPP application layer. The service request includes type of the result (i.e., absolute location, relative location or ranging information) and the required QoS. This is shown as, Ranging/SL Positioning service request from Application layer
[0136] In a further step 802, UE1 830 discovers UE2/.../UEn 840 (i.e., SL Reference UEs/Located UEs) as defined in clause 6.4 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18), if needed. This is illustrated as, ‘Discovery ’ .
[0137] In a further step 803, if none of UEl/.../UEn 840 are served by an NG-RAN or the serving network does not support Ranging/SL Positioning, UE-only Operation is applied. This is illustrated as, ‘Determine UE-only Operation
[0138] In a further step 804, UE1 830 and UE2/.../UEn 840 perform capability exchange. Step 804 may be performed during steps 805 and step 806 with coordination of SL Positioning Server UE 820. This step is shown as, ‘Capability Exchange
[0139] In a further step 805, if UE1 830 does not support SL Positioning Server functionalities, a SL Positioning Server UE (either co-located with a SL Reference UE/Located UE, or operated by a separate UE) is discovered (if not yet discovered in step 2) and selected. If a SL Positioning Server UE that is co-located with a SL Reference UE/Located UE or operated by a separate UE, UE1 830 discovers and selects the SL Positioning Server UE as described in clause 6.4 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18) and requests SL Positioning Server UE 820 to participate in the Ranging/Sidelink positioning. This is illustrated as, ‘SL Positioning Server UE discover deselection
[0140] In a further step 806, Sidelink Positioning assistance data is transferred among UE1 830/ .../UEn 840 and the SL Positioning Server UE 820. This is illustrated as, ‘Sidelink positioning assistance data transfer [0141] In a further step 807, SL PRS measurement is performed between UE1 830 and UE2/.../UEn 840 and possibly also amongst the UEs of UE2/.../UEn 840. This is illustrated as, ‘SL PRS measurement
[0142] In a further step 808, SL PRS measurement data is transferred to the SL Positioning Server UE 820 or is transferred to UE1 830 if it supports SL Positioning Server functionalities, in order to perform result calculation. Based on the type of the result received in step 801, absolute location, relative location or ranging information is calculated at the UE 830. This is illustrated as, ‘SL PRS measurement data transfer & result calculation
[0143] In a further step 809, the Ranging/SL Positioning result is transferred to either: the SL Positioning Client UE 810 over PC5 (as shown in step 809a) during procedures for Ranging/SL Positioning service exposure though PC5 as defined in clause 6.7.1.1 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18f or the RSPP application layer (as shown in step 809b). These steps are shown as, Ranging/SL positioning response over PC 5 ’ and Ranging/SL positioning service response to Application layer ’, respectively.
[0144] SL communication PQIs will now be introduced using Tables 7 and 8. More specifically, Table 7 depicts the standardized PQI for transmitting SL ProSe communication messages as a function of different parameters, as provided in 3GPP TS 23.304 titled, “Proximity based Services (ProSe) in the 5G System (5GS) ” (Release 18). This serves as the transport QoS for ProSe services. Table 8 depicts the standardized PQI for transmitting SL V2X communication messages as a function of different parameters, as provided in 3GPP TS 23.287 titled, “Architecture enhancements for 5G System (5GS) to support Vehicle-to-Every thing (V2X) services” (Release 18). This serves as the transport QoS for V2X services.
Figure imgf000038_0001
Table 7
[0145] Example services for PQI value 24 include Mission Critical user plane Push To Talk voice (e.g. MCPTT). Example services for PQI value 25 include Non-Mission-Critical user plane Push To Talk voice. Example services for PQI value 26 include Mission Critical Video user plane. Example services for PQI value 60 include Mission Critical delay sensitive signalling (e.g. MC-PTT signalling). Example services for PQI value 61 include Mission Critical Data (e.g. example services are the same as 5QI 6/8/9 as specified in 3GPP TS 23.501. Example services for PQI value 92 include Interactive service - consume VR content with high compression rate via tethered VR headset (as described in 3 GPP TS 22.261). Example services for PQI value 93 include interactive service - consume VR content with low compression rate via tethered VR headset; Gaming or Interactive Data Exchanging (as described in 3GPP TS 22.261). It should be noted that GBR and Delay Critical GBR PQIs can only be used for unicast PC5 communications.
Figure imgf000039_0001
Table 8
[0146] Example services for PQI value 21 include platooning between UEs - Higher degree of automation; Platooning between UE and RSU - Higher degree of automation. Example services for PQI value 22 include sensor sharing - higher degree of automation. Example services for PQI value 23 include information sharing for automated driving - between UEs or UE and RSU - higher degree of automation. Example services for PQI value 55 include cooperative lane change - higher degree of automation. Example services for PQI value 56 include platooning informative exchange - low degree of automation; and Platooning - information sharing with RSU. Example services for PQI value 57 include cooperative lane change - lower degree of automation. Example services for PQI value 58 include sensor information sharing - lower degree of automation. Example services for PQI value 59 include platooning - reporting to an RSU. Example services for PQI value 90 include Cooperative collision avoidance; sensor sharing - Higher degree of automation; and video sharing - higher degree of automation. Example services for PQI value 91 include Emergency trajectory alignment; and sensor sharing. - higher degree of automation. It should be noted that, GBR and Delay Critical GBR PQIs can only be used for unicast PC5 communications.
[0147] QoS handling will now be introduced in respect of handling of ranging/SL positioning QoS; and handling of RSPP transport QoS.
[0148] Ranging/SL Positioning QoS requirements may be provided in the Ranging/SL Positioning service request generated at the application layer, and is provided from the application layer to the Ranging/SL Positioning layer. Ranging/SL Positioning QoS requirement may be included in the Ranging/SL Positioning Service request from SL Positioning Client UE.
[0149] The Ranging/SL Positioning layer maps the Ranging/SL Positioning QoS requirement to the Ranging/SL Positioning QoS parameters and provides the Ranging/SL Positioning QoS parameters to the AS layer. If there is no received Ranging/SL Positioning QoS requirement from the application layer, the Ranging/SL Positioning layer determines the Ranging/SL Positioning QoS parameters based on the Ranging/SL positioning Policy/parameters as configured in the clause of 5.1 of the 3GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18).
[0150] Ranging/SL Positioning QoS information contains attributes defined in clause 4. lb of the 3GPP TS 23.273, titled “5G System (5GS) Location Services (LCS) ”, Stage 2 (Release 18) with the following additions: the accuracy attribute also includes the relative horizontal accuracy, and the relative vertical accuracy for relative positioning, and the distance accuracy and direction accuracy for Ranging; and Range, which indicates the applicability of the QoS attributes in the Ranging/SL Positioning operation over PC5. Ranging/SL Positioning QoS information is used for determination of Ranging/SL Positioning method. The Ranging/SL Positioning methods are defined in the 3GPP TS 38.355 titled, “Sidelink Positioning Protocol (SLPP); Protocol specification” (Release 18).
[0151] The V2X/ProSe layer handles the RSPP traffic as the V2X/ProSe application data packets for the QoS treatment. QoS handling mechanism of V2X as defined in clause 5.4 of the 3GPP TS 38.355 titled, “Sidelink Positioning Protocol (SLPP); Protocol specification” (Release 18), or QoS handling mechanism of 5G ProSe as defined in clause
5.6.1 of the 3GPP TS 23.304 titled, “Proximity based Services (ProSe) in the 5G System (5GS) ” (Release 18). is reused. PQI values as defined in 3GPP TS 23.287 titled, “Architecture enhancements for 5G System (5GS) to support Vehicle -to-Every thing (V2X) services” (Release 18). and 3GPP TS 23.304 titled, “Proximity based Services (ProSe) in the 5G System (5GS) ” (Release 18). may be reused for RSPP transport QoS.
[0152] LCS Quality of Service will also be briefly introduced. It is used to characterise the location request. It can either be determined by the operator or determined based on the negotiation with the LCS client or the AF. It is optional for LCS client or the AF to provide the LCS Quality of Service in the location request.
[0153] LCS Quality of Service information is characterised by 3 key attributes, which include: LCS QoS Class as defined below; Accuracy: i.e., Horizontal Accuracy (see clause
4.3.1 of the 3GPP TS 22.071 titled, “Location Services (LCSfService description; Stage 1 ” (Release 17)) and Vertical Accuracy (see clause 4.3.2 of the 3GPP TS 22.071 titled, “Location Services (LCS); Service description; Stage 1 ”); and Response Time (e.g., no delay, low delay or delay tolerant as described in clause 4.3.3 of the 3GPP TS 22.071 titled, “Location Services (LCSfService description; Stage 1 ” ).
[0154] It should be noted that, one or two QoS values for Horizontal Accuracy, Vertical Accuracy, can be provided in the location request in addition to a preferred accuracy when LCS QoS Class is set to Multiple QoS Class.
[0155] The LCS QoS Class defines the degree of adherence by the Location Service to another quality of service parameter (Accuracy), if requested. The 5G system shall attempt to satisfy the other quality of service parameter regardless of the use of QoS Class. There are 3 LCS QoS Classes.
[0156] One class is the ‘Best Effort Class’. This class defines the least stringent requirement on the QoS achieved for a location request. If a location estimate obtained does not fulfil the other QoS requirements, it should still be returned but with an appropriate indication that the requested QoS was not met. If no location estimate is obtained, an appropriate error cause is sent. [0157] Another class is the 'multiple QoS Class’. This class defines intermediate stringent requirements on the QoS achieved for a location request. If the obtained location estimate does not fulfil the most stringent (i.e., primary) other QoS requirements affected by the degree of adherence of the QoS class, then another location estimation may be triggered at LMF attempting less stringent other QoS requirements. The process may be iterated until the least stringent (i.e. minimum) other QoS requirements are attempted. If the least stringent other QoS requirements cannot be fulfilled by a location estimate, then the location estimate shall be discarded, and an appropriate error cause shall be sent.
[0158] An AF may provide a location request with Multiple QoS Class via NEF. For an LCS client to provide a location request with Multiple QoS Class an Le interface implementation supporting Multiple QoS Class may be required. The multiple QoS Class can only be applied for Deferred 5GC-MT-LR Procedure in this release of the specification.
[0159] Another class is the ‘Assured Class’. This class defines the most stringent requirement on the accuracy achieved for a location request. If a location estimate obtained does not fulfil the other QoS requirements, then it shall be discarded, and an appropriate error cause shall be sent.
[0160] How the LMF decides the positioning method is an implementation aspect not pre-determined by QoS criteria. For an LCS client, it may indicate accuracy defined in the 3GPP TS 29.572 titled, “Location Management Services; Stage 3 ” (Release 18), tables 6.1.6.3.2-1 and 6.1.6.3.5-1. For AF, it may either indicate the accuracy defined in the same 3GPP TS 29.572, table 6.1.6.3.2-1, or indicate a particular value e.g., PLMN ID defined in the table 5.3.2.4.7-1.
[0161] Certain terminologies will now be briefly introduced and discussed to aid the understanding of the disclosure herein.
[0162] An initiator device is a device that initiates a SL positioning/ranging session. The initiator device may be a network entity, (e.g., gNB, LMF) or UE/roadside unit (RSU).
[0163] A responder device is a device that responds to a SL positioning/ranging session from an initiator device. The responder device may be a network entity, (e.g., gNB, LMF) or UE/roadside unit (RSU). [0164] A target-UE may be referred to as a UE of interest whose position (absolute or relative) is to be obtained by the network or by the UE itself.
[0165] Sidelink positioning refers to positioning a UE using reference signals transmitted over SL, i.e., PC5 interface, to obtain absolute position, relative position, or ranging information.
[0166] Ranging is the determination of the distance and/or the direction between a UE and another entity, e.g., an anchor UE.
[0167] An anchor UE is a UE supporting positioning of a target UE, e.g., by transmitting and/or receiving reference signals for positioning, providing positioning- related information, etc., over the SL interface (also may be referred to as SL Reference UE).
[0168] An assistant UE is a UE supporting Ranging/Sidelink between a SL Reference UE and Target UE over PC5, when the direct Ranging/Sidelink positioning between the SL Reference UE/ Anchor UE and the Target UE cannot be supported. The measurement/results of the Ranging/Sidelink Positioning between the Assistant UE and the SL Reference UE and that between the Assistant UE and the Target UE are determined and used to derive the Ranging/Sidelink Positioning results between Target UE and SL Reference UE.
[0169] A SL Positioning Server UE is a UE offering location calculation, for a SL Positioning and Ranging based service. It interacts with other UEs over PC5 as necessary in order to calculate the location of the Target UE. The Target UE or SL Reference UE can act as a SL Positioning server UE if location calculation is supported.
[0170] A SL Positioning Client UE is a third-party UE, other than SL Reference UE and Target UE, which initiates a Ranging/Sidelink positioning service request on behalf of the application residing on it.
[0171] It should be noted that the SL Positioning Client UE does not have to support Ranging/Sidelink positioning capability, but a communication between the SL Positioning Client UE and SL Reference UE/Target UE has to be established, either via PC5 or via 5GC, for the transmission of the service request and the result.
[0172] A SL positioning node may refer to a network entity and/or device/UE participating in a SL positioning session, e.g., LMF (location server), gNB, UE, RSU, anchor UE, Initiator and/or Responder device.
[0173] A Configuration entity is a network node or device/UE capable of configuring time-frequency resources and related SL positioning configurations. A SL Positioning Server UE may serve as a configuration entity.
[0174] The present disclosure details solutions for mapping the SL PRS priority as a function of the SL Positioning QoS requirements/parameters according to different configuration scenarios. These will now be described with reference to the accompanying figures.
[0175] Some embodiments provide SL PRS to SL Positioning QoS Mapping. More specifically a direct one-to-one mapping between SL PRS priority and SL Positioning QoS parameters is provided. This one-to-one mapping may be configured (i.e., preconfigured) to the UE that is enabled to transmit SL PRS. Such a UE may comprise one of an anchor UE, target-UE or server UE. In other implementations a Located UE, Client UE, Assistant UE are also not precluded from transmitting SL PRS based on an assigned priority based on the SL Positioning QoS parameters. The SL Positioning QoS may also be based on accuracy according to one or more LCS requests. These LCS requests can include: Absolute Location; Absolute Horizontal Location Accuracy; Absolute Vertical Location Accuracy; Relative Location; Relative Horizontal Location Accuracy; Relative Vertical Location Accuracy; Ranging for Distance; Horizontal Distance Location Accuracy; Vertical Distance Location Accuracy; Ranging for Direction; Azimuth Angle of Arrival Direction Accuracy; Zenith Angle of Arrival Direction Accuracy.
[0176] A principle of some embodiments disclosed herein is based on the fact that higher-accuracy services will get a higher SL PRS priority. Table 9 is an exemplary illustration of the one-to-one mapping between SL PRS priority and SL Positioning QoS based on absolute horizontal location accuracy only, where the highest to lowest priority is arranged based on descending order (lowest SL PRS Priority value maps to highest priority positioning/ranging service based on accuracy, while the highest SL PRS priority value maps to the lowest priority SL positioning/ranging service based on accuracy). In another implementation, exemplary Table 9 may also be separately applied to relative horizontal location accuracy. In other implementations, the horizontal accuracy values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
Figure imgf000045_0001
Table 9
[0177] Similarly, Table 10 is an exemplary illustration of the one-to-one mapping between SL PRS priority and SL Positioning QoS based on absolute vertical location accuracy only. In another implementation, exemplary Table 10 may also be separately applied to relative vertical location accuracy. In other implementations, the vertical accuracy values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
Figure imgf000046_0001
Table 10
[0178] In another implementation, Table 11 is an exemplary illustration of the one-to- one mapping between SL PRS priority and SL Positioning QoS based on ranging for horizontal distance accuracy only. In other implementations, exemplary Table 11 may also be separately applied to relative distance accuracy. In other implementations, the distance accuracy values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
Figure imgf000046_0002
Table 11
[0179] In another implementation, Table 12 is an exemplary illustration of the one-to- one mapping between SL PRS priority and SL Positioning QoS based on ranging for direction accuracy only. In other implementations, the direction accuracy values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded. More specifically, Table 12 provides exemplary mapping of SL PRS Priority and SL Positioning QoS using either Ranging for azimuth direction or zenith direction accuracy or a singular overall direction accuracy or any combination thereof.
Figure imgf000047_0001
Table 12
[0180] Various location-based applications or service may require different degrees of response times, which may have an accuracy trade-off depending on the given positioning requirements. Table 13 is an exemplary illustration of the one-to-one mapping between SL PRS priority and SL Positioning QoS based on the positioning response time/positioning latency (i.e., end-to-end positioning latency) only. In other implementations, the positioning response time/positioning latency values may be fixed as opposed to a value range or in alternative implementations some values may be upper bounded or lower bounded.
Figure imgf000047_0002
Table 13 [0181] In other implementations, the SL PRS priority may be mapped to a pre-defined SL PRS delay budget or SL Positioning delay budget or Packet delay budget or Positioning Delay budget or Location delay budget given by exemplary values indicated in Table 13.
[0182] In alternative implementations, a subset of SL PRS priorities may be mapped to response time/SL positioning latency categories. For example, SL PRS priorities { 1-3} may be mapped to a “no delay” category, i.e., the SL PRS should be transmitted with no delay and the measurement measuring and responding UE should immediately return any location estimate or dispatchable location that it has measured based on the transmitted SL PRS. Similarly, SL PRS priorities {4-6} may be mapped to a “low delay” category, i.e., fulfilment of the response time requirement takes precedence over fulfilment of the accuracy requirement. SL PRS priorities {7-8} may be mapped to a “delay tolerant” category, i.e., fulfilment of the accuracy requirement takes precedence over fulfilment of the response time requirement. It may be further up to UE implementation, whether to select and assign a SL PRS priority/priorities based in each subset of SL PRS priorities according to the given/received SL Positioning. QoS requirements. Table 14 shows SL PRS priority mapping table based on the different categories.
Figure imgf000048_0001
Table 14
[0183] Since multiple SL PRS priorities are allowed in a dedicated and shared/common resource pool, the one or more SL PRS priorities may be based on one or more of the mapping tables described above. [0184] In other implementations, the 8-levels of SL PRS priority may be a function of the mobility state of the UE based on either: Absolute/relative horizontal speed/velocity estimates (where velocity may also include heading); and/or Absolute/relative vertical speed/velocity estimates (where velocity may also include heading) or high level mobility values comprising stationary, low mobility, medium mobility or high mobility.
[0185] Other embodiments described herein relate to consolidated SL PRS priority to SL positioning QoS mapping tables. More specifically, the SL PRS priority may comprise of a one or more combination of SL Positioning QoS accuracy parameters given by absolute/relative horizontal accuracy, absolute/relative vertical accuracy, ranging for distance accuracy, ranging for direction accuracy and/or response times. This can enable configuration of a single table that encompasses all SL Positioning QoS accuracy parameters and may provide a standardized or unified SL PRS mapping table. Table 15 shows the complete consolidated SL PRS priority mapping table based on different described SL Positioning QoS parameters.
Figure imgf000049_0001
Table 15 [0186] In another implementation, the SL PRS priorities shown in Table 15 may be further associated with a category described in Table 14.
[0187] In another implementation, SL Positioning LCS QoS Classes (SPLQC) may be defined to consolidate the one or more SL Positioning QoS Parameters and thereafter be mapped in a one-to-one manner with the SL-RS priority. The SPLQCs may be defined in descending order, where the stringent SL Positioning QoS parameters are assigned with the lowest number, e.g., SPLQC 1, while the most relaxed requirements are assigned with the highest number, e.g., SPLQC 8. In other implementations, the SPLQCs may be arranged in ascending order, where the stringent SL Positioning QoS parameters are assigned with the highest number, e.g., SPLQC 8, while the relaxed requirements are assigned with the lowest number, e.g., SPLQC 1. Table 16 shows an example of how an SPLQC may be defined in descending order:
Figure imgf000050_0001
Table 16 [0188] The complete consolidated SL PRS priority mapping shown in Table 15 can be transformed as shown in Table 17.
Figure imgf000051_0001
Table 17
[0189] The definitions of the SPLQC may be standardized and defined in either the Ranging/SL Positioning Application, the Ranging SL Positioning layer or the SL Positioning Protocol (SLPP) layer. The guidelines for defining each SPLQC may be based on one or more combination of absolute/relative horizontal accuracy value ranges, absolute/relative vertical accuracy value ranges, SL positioning response times/end-to-end latencies, and absolute/relative horizontal/vertical speed/velocity estimate value ranges. Table 16 also captures the trade-off between positioning accuracies and the positioning response times, for example higher accuracies require longer durations, while lower accuracies can be fulfilled in a shorter period.
[0190] Alternatively, the manner in which the SPLQC is defined may be based on UE implementation. The SL PRS priority to SPLQC mapping table may lower the overall signaling overhead in terms not considering each of the SL value ranges of each SL Positioning QoS parameter.
[0191] The disclosure herein also relates to procedures for SL PRS priority mapping to SL positioning QoS requirements/parameters. According to some embodiments, the procedures in the protocol stack for mapping the SL PRS priority to the SL Positioning QoS are described. Figure 9 illustrates an example 900 of SL PRS priority mapping to SL positioning QoS procedures, in accordance with aspects of the present disclosure. More specifically, Figure 9 illustrates exemplary mechanisms in UE-only based SL positioning operation and in-coverage and out-of-coverage scenarios in which the SL Positioning QoS may be mapped to each of the SL PRS priority levels.
[0192] Figure 9 shows a first UE 910 denoted ‘UE-A’ and a second UE 920 denoted ‘UE-B’. Each UE 910, 920 is shown as comprising SLPP, ProSe/V2x, SDAP, PDCP, RLC, MAC and PHY. Also shown in Figure 9 are a ranging/SL positioning layer 912 and ranging/SL positioning application 914 for the first UE 910. Further shown in Figure 9 are a ranging/SL positioning layer 922 and ranging/SL positioning application 924 for the second UE 920. The first UE 910 communicates with the ranging/SL positioning layer 912, with the ranging/SL positioning layer 912 shown communicating with the ranging/SL positioning application 914. A similar arrangement is shown for the second UE 920, layer 922 and application 924. The various SLPP, ProSe/V2X, SDAP, PDCP, RLC, MAC and PHY aspects of the first and second UEs 910, 920, are shown in communication with each other.
[0193] A first step 901 is shown, wherein the Ranging/SL Positioning Application/LCS Client 914, 924 generates the required SL Positioning QoS associated to a requested location estimate, which may comprise of one or more of absolute horizontal location estimate, absolute vertical location estimate, relative horizontal location estimate, relative vertical location estimate, ranging for distance estimate, ranging for direction estimate, absolute velocity estimate, or relative velocity estimate. This step is shown as, ‘The ranging/SL positioning QoS is generated at application level
[0194] A second step 902 is shown, wherein the Ranging/SL Positioning layer 912, 922 is responsible for mapping the Application Positioning QoS requirements to the Ranging/SL Positioning QoS Parameters and provides the Ranging/SL Positioning QoS parameters to the AS layer. If there is no received Ranging/SL Positioning QoS requirement from the application layer, the Ranging/SL Positioning layer 912, 922 determines the Ranging/SL Positioning QoS parameters based on the Ranging/SL positioning Policy/parameters as configured and provision to the UE . This step is shown as, ‘Mapping of the ranging/SL positioning requirements to ranging/SL positioning QoS parameters [0195] A further step 903 is shown, wherein the SL PRS priority is mapped according to the SL Positioning QoS based on the following options. One option is provided in step 903a wherein the SL PRS priority mapping to SL Positioning QoS is performed within the Ranging/SL Positioning layer 912, 922 according to the embodiments and mapping tables described herein. Furthermore, the SPLQC may also be defined here. Step 903a is referred to in Figure 9 as, ‘SL PRS priority mapping to SL positioning QoS including SP LQC definition ’. Another option is provided by step 903b, wherein the positioning method is selected and a recommended SL PRS configuration to meet the received SL Positioning QoS is generated. The SL PRS configuration may include at least one of comb-size including number of symbols and resource element offset, transmission bandwidth and SL PRS priority. The SL PRS priority mapping to SL Positioning QoS is performed within the SLPP layer according to the embodiments and mapping tables described herein.
Furthermore, the SPLQC may also be defined here. Step 903b is referred to in Figure 9 as, ‘SL PRS priority mapping to SL positioning QoS’. A further option is provided by step 903 c, wherein in the case of the unavailability of the SL Positioning QoS, the SL PRS priority mapping is performed within the ProSe/V2X layer according to the standardized PQIs described in Table 7 and Table 8. This implies that the SL PRS will be mapped according to the default priority values according to the appropriate V2X/ProSe service requirements. In other implementations, a Ranging/SL Positioning service requirement may be defined as part of the standardized PQIs, which may cover SLPP messages and/or SL PRS. The step 903c is referred to in Figure 9 as, ‘SL PRS priority mapping to SL positioning QoS including SP LQC based on transport QoS if 903a or 903b is not available or fulfilled’.
[0196] In a further step 904, the SL PRS priority is then passed down to the MAC and physical layer for the transmission of SL PRS. Multiple SL PRS priorities may be provided to the MAC and physical layer corresponding to the different location service requests each associated with a particular SL Positioning QoS class/set of parameters either from the same or different application within the UE 910, 920 or received from an external network entity. This step is illustrated as, ‘SL PRS priority used by MAC and physical layer ’. [0197] Also indicated in Figure 9 are that the ranging/SL positioning applications 914, 924, trigger ranging/SL positioning upon request from an internal LCS client or external client UE. Furthermore, ranging/SL positioning layers 912, 922, control UE discovery and selection, provide the Application Layer IDs, and Source/Destination Layer-2 IDs, etc.
[0198] The SL PRS priority/priorities is/are signaled in a 1st, e.g., SCI format 1-B or 2nd stage SCI, e.g., SCI format 2-D, to UE-B 920 and is used by UE-B 920 to perform autonomous resource selection (also known as Mode 2 or Scheme 2 resource allocation for sidelink). In other/additional implementations, the SL PRS priority/priorities is/are signaled according to the following scenarios.
[0199] In a first scenario, referred to as ‘ Scenario 1 ’, UE A 910 is a target UE and is configured to perform UL type SL-TDOA based on SL-RTOA measurements, where UE-B 920 and/or any additional UEs may perform SL-RTOA measurements. UE-A 910 may signal a one or more SL PRS priorities based on the SL Pos. QoS parameters associated with the one or more SL PRS transmissions to UE-B 920 and/or any additional UEs. UE B 920 may measure the SL PRS and perform the requested SL positioning measurement(s), i.e., in this case SL-RTOA, based on the associated received SL PRS priority.
[0200] In a second scenario, referred to as ‘Scenario 2’, UE A 910 is a target UE and is configured to perform single or double-sided SL-RTT based on UE-Rx-Tx time difference measurements, where UE-A 910 may perform SL- UE-Rx-Tx time difference measurements. UE-A 910 may signal a request to UE-B 920 including one or more SL PRS priorities based on the SL Pos. QoS parameters associated with the one or more requested SL PRS transmissions to be transmitted to UE-A 910 from UE-B 920. Target UE A 910 may measure the SL PRS received from UE-B 920 and perform the requested SL positioning measurement(s), i.e., in this case UE Rx-Tx time difference measurement, based on the associated received SL PRS priority. In both Scenario 1 and Scenario 2, the SL-PRS priority may be signalled using lower layer signalling such as 1st, e.g., SCI format 1-B or 2nd stage SCI, e.g., SCI format 2-D, a new SL MAC CE or higher-layer signalling such as PC5 RRC, or SLPP.
[0201] It should be noted that multiple priorities may be associated to different SL PRS transmissions within a dedicated or shared resource pool. [0202] Furthermore, the SL PRS priorities may be further used to control the congestion within a dedicated SL PRS resource pool or a shared resource pool (comprising of SL PRS and SL-SCH data (SL communication data)).
[0203] According to Figure 9, the SL PRS priority mapping is performed at UE A 910 (SL PRS transmitting UE, e.g. an anchor UE with server UE functionalities). In such a case, after the mapping has been performed, the mapping profile/table may be provided to UE-B 920 (SL PRS receiving UE, e.g. a target UE) in case of unicast SL PRS transmissions or other sets of UEs (in case of groupcast SL PRS transmissions) via UE-specific signalling, e.g., 1st or 2nd stage SCI, SL MAC CE, SLPP signalling, e.g., SLPP ProvideAssistanceData message.
[0204] According to another implementation of this embodiment, SL PRS priority to SL Positioning QoS Mapping is performed entirely in the AS (Access Stratum) layer. This implies that such a SL PRS priority to SL Positioning QoS mapping may be performed in the Service Data Adaptation Protocol (SDAP) layer, or Packet Data Convergence protocol (PDCP) layer, or Radio Link Control (RLC) layer or Medium Access Control (MAC) layer. In another implementation, the SL PRS priority to SL Positioning QoS Mapping may also be performed in the physical (PHY) layer. This implies that the SLPP layer and ProSe/V2X layer and are transparent to this mapping. The SLPP/Prose V2X layer provide the LCS QoS of an associated LCS request and the AS layer determines the SL PRS priority based on the received LCS QoS.
[0205] In other implementations, e.g., in network based SL positioning operation and in-coverage scenarios the mapping may be performed by the network, e.g., gNB or LMF and may be able to provision the SL PRS priority to SL Positioning QoS mapping table to UE-A 910 and UE-B 920 via appropriate broadcast signalling, using SIB or posSIB signalling. Alternatively, UE-specific signalling such DL MAC CE, RRC, SLPP or LPP signalling, e.g., LPP ProvideAssistanceData message may be used.
[0206] Embodiments of the disclosure herein also relate to the mapping of SL PRS priority to SL positioning QoS based on logical channel prioritization and resource availability. More specifically, the SL PRS priority, which has been mapped based on SL positioning QoS, may correspond to a percentage/ratio of freely available time-frequency resources, e.g., slots, subframes, frames, etc that can be used for transmitting SL PRS. This percentage of freely available slots may extend to: a SL PRS dedicated resource pool, where time-frequency resources, e.g., SL PRS resources, slots are allocated for sidelink control and associated SL PRS transmissions; or a Shared/common resource pool, where time-frequency resources, e.g., SL slots are allocated for sidelink control and associated SL PRS and SL-SCH (SL data) transmissions.
[0207] The logical channel prioritization (LCP) mechanism within the MAC layer comprising of 8 levels of priority may be mapped in a one-to-one manner to the SL PRS priority such that the highest priority associated with the lowest logical channel priority, e.g., 0 may be mapped to set of resources within a dedicated or shared/common pool where the percentage of available resources over the total number of resources in a serving cell is higher than a configured threshold M, which reflects a higher percentage of available SL resources. For example, a SL PRS with a priority of 1 may be mapped to an LCP 1 (the lowest number may be 0 in a range from 0 to 7, in other implementations the lowest number may be 1 if one is the lowest number in range from 1-8), which in turn may be mapped to a set of resources where the percentage of available resources is > M=90%. This implies that a higher accuracy may be achieved based on the number of freely available resources. The lower the percentage of available slots, the lower the SL PRS priority, which may correspond to a lower accuracy as described in the mapping tables herein. Table 18 is an exemplary illustration of the SL PRS priority mapping to the percentage of freely available slots. Moreover, Table 18 shows example mapping of SL PRS priority as a function of LCP and percentage of freely available slots.
Figure imgf000057_0001
Table 18
[0208] The aforementioned freely available SL resource(s) may be described in terms of available SL PRS resource(s) associated with a frequency and time domain configuration, available slots, available subframes, available frames, or available hyper frames. Furthermore, the type of SL PRS priority resource mapping may be applicable to both Mode 1/Schemel or Mode 2/Scheme 2 SL positioning resource allocation procedures.
[0209] The procedure for logical channel prioritization for transmitting SL PRS, which is based on 8 levels of logical channel priority, will be briefly described.
[0210] Upon receiving a sidelink resource grant either from a base station, e.g., gNB or location server or based on sensing and resource selection procedure, the UE determines which logical channel(s) will carry the SL PRS transmissions(s) based on the one of the following criteria: LCP - the UE addresses the logical channels in which to transmit SL PRS in a descending order of priority based on the SL PRS priority and SL Positioning QoS; SL PRS delay budget - this may be applied to the SL PRS to establish which SL PRS may be transmitted in the highest priority logical channels; Resource Availability - the UE selects logical channels that can be accommodated to transmit SL PRS within the available percentage of sidelink resources based on M as shown in Table 18.
[0211] With the chosen logical channels, the UE then transmits SL PRS to the other UE(s) based on the above criteria. [0212] In addition, a default SL PRS priority may be mapped to a default logical channel in the case that any of the SL positioning QoS or resource availability or transport QoS including packet delay budget or SL PRS delay budget is unavailable.
[0213] According to aspects of this embodiment, the logical channel prioritization for SL PRS is designed to ensure that the most important logical channels are served first based on the SL PRS priority, which is based on the SL positioning QoS described in the embodiments and mapping tables provided herein.
[0214] The above embodiment described in Table 18, may also be implemented in a manner that is decoupled from the logical channel priority, i.e., the SL PRS priority may be directly mapped to the available percentage of freely available resources.
[0215] In another implementation, other metrics to express the amount of freely available SL positioning resources may also be used, e.g., ratio of available resources to occupied resources or ratio of symbols in a slot/slots in a subframe for SL PRS to SL-SCH data and so forth. This can be extended to any quantitative metric which can express the amount of freely available sidelink resources to perform SL positioning.
[0216] According to the disclosure herein, there is provided a user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmit one or more SL PRS according to the one or more SL PRS configurations. [0217] In some embodiments, the configuration may also comprise a comb-size including a number of symbols and resource element offsets, transmission bandwidth, etc.
[0218] In some embodiments, the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
[0219] In some embodiments, the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
[0220] In some embodiments, the latency category can be no delay; low delay; and delay tolerant.
[0221] In some embodiments, the SL positioning QoS parameters comprise a mobility state of the UE.
[0222] In some embodiments, the mobility state can be based on an absolute velocity or a relative velocity, or absolute speed or relative speed, optionally in vertical or horizontal, or may comprise one or more high-level mobility state indicators such as stationary, low mobility, medium mobility, high mobility or alternatively mobile UE. The latter can enable SL PRS priority differentiation based on high-level indicators as opposed to speed/velocity values.
[0223] In some embodiments, the at least one processor is configured to cause the UE to determine the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services (LCS) QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters. [0224] In some embodiments, the at least one processor is configured to cause the UE to determine the mapping in either of: a ranging/SL positioning communication layer; a SL positioning protocol (‘SLPP) layer; a vehicle-to-everything (V2X)/ProSe layer; or an access stratum (AS) layer.
[0225] In some embodiments, the at least one processor is configured to cause the UE to determine the one or more SL positioning QoS requirements by: receiving the one or more SL positioning QoS requirements from either of: a SL positioning application; or an LCS client.
[0226] In some embodiments, the at least one processor is further configured to cause the UE to: transmit, to at least one other UE, the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
[0227] In some embodiments, the transmission may be via UE-specific signalling, broadcast, or groupcast.
[0228] In some embodiments, the at least one processor is further configured to cause the UE to determine the mapping to correspond to a percentage or ratio of available SL positioning resources.
[0229] In some embodiments, the SL positioning resources may be part of a dedicated resource pool or a shared/common resource pool. Examples of resources include slots, subframes, that can be used for transmitting SL PRS.
[0230] In some embodiments, the at least one processor is configured to cause the UE to determine the mapping to correspond to a percentage or ratio of available SL positioning resources by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority, which corresponds to a different percentage or ratio of available SL positioning resources.
[0231] In some embodiments, the at least one processor is configured to cause the UE to apply the percentage or ratio of available SL positioning resources to: a SL PRS dedicated resource pool; and/or a SL PRS shared or common resource pool. [0232] In some embodiments, there are 8 logical channels. The mapping between logical channel and available SL positioning resources can be a direct mapping.
[0233] In some embodiments, the at least one processor is configured to cause the UE to determine the mapping by: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables, from a network entity of a wireless communication network.
[0234] In some embodiments, the network entity is a gNB or LMF.
[0235] In some embodiments, the UE is a UE selected from the list of UEs consisting of an anchor UE; the target UE; a server UE; a located UE; a client UE; and an assistant UE.
[0236] According to the disclosure herein, there is further provided a method in an UE, comprising: determining one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmitting one or more SL PRS according to the one or more SL PRS configurations.
[0237] In some embodiments, the configuration may also comprise a comb-size including a number of symbols and resource element offsets, transmission bandwidth, etc.
[0238] In some embodiments, the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy. [0239] In some embodiments, the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
[0240] In some embodiments, the latency category can be no delay; low delay; and delay tolerant.
[0241] In some embodiments, the SL positioning QoS parameters comprise a mobility state of the UE.
[0242] In some embodiments, the mobility state can be based on an absolute velocity or a relative velocity, or absolute speed or relative speed, optionally in vertical or horizontal, or may comprise one or more high-level mobility state indicators such as stationary, low mobility, medium mobility, high mobility or alternatively mobile UE. The latter can enable SL PRS priority differentiation based on high-level indicators as opposed to speed/velocity values.
[0243] In some embodiments, the determining the mapping comprises determining the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services (LCS) QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
[0244] In some embodiments, the determining the mapping comprising determining the mapping in either of: a ranging/SL positioning communication layer; a SL positioning protocol(‘SLPP) layer; a vehicle-to-everything (V2X)/ProSe layer; or an access stratum (AS) layer.
[0245] In some embodiments, the determining the one or more SL positioning QoS requirements comprises determining the one or more SL positioning QoS requirements by: receiving the one or more SL positioning QoS requirements from either of: a SL positioning application; or an LCS client. [0246] Some embodiments, further comprise transmitting, to at least one other UE, the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
[0247] In some embodiments, the transmission may be via UE-specific signalling, broadcast, or groupcast.
[0248] In some embodiments, the determining the mapping comprises determining the mapping to correspond to a percentage or ratio of available SL positioning resources.
[0249] In some embodiments, the SL positioning resources may be part of a dedicated resource pool or a shared/common resource pool. Examples of resources include slots, subframes, that can be used for transmitting SL PRS.
[0250] In some embodiments, the determining the mapping comprises determining the mapping to correspond to a percentage or ratio of available SL positioning resources by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority, which corresponds to a different percentage or ratio of available SL positioning resources.
[0251] Some embodiments comprise applying the percentage or ratio of available SL positioning resources to: a SL PRS dedicated resource pool; and/or a SL PRS shared or common resource pool.
[0252] In some embodiments, there are 8 logical channels. The mapping between logical channel and available SL positioning resources can be a direct mapping.
[0253] In some embodiments, the determining the mapping comprises: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables, from a network entity of a wireless communication network.
[0254] In some embodiments, the network entity is a gNB or LMF.
[0255] In some embodiments, the UE is a UE selected from the list of UEs consisting of: an anchor UE; the target UE; a server UE; a located UE; a client UE; and an assistant UE. [0256] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: input one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and output one or more SL PRS according to the one or more SL PRS configurations.
[0257] In some embodiments, the configuration may also comprise a comb-size including a number of symbols and resource element offsets, transmission bandwidth, etc.
[0258] In some embodiments, the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
[0259] In some embodiments, the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
[0260] In some embodiments, the latency category can be no delay; low delay; and delay tolerant.
[0261] In some embodiments, the SL positioning QoS parameters comprise a mobility state of a UE.
[0262] In some embodiments, the mobility state can be based on an absolute velocity or a relative velocity, or absolute speed or relative speed, optionally in vertical or horizontal. [0263] In some embodiments, the at least one controller is configured to cause the processor to determine the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services (LCS) QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
[0264] In some embodiments, the at least one controller is configured to cause the processor to determine the mapping in either of a ranging/SL positioning communication layer; a SL positioning protocol (SLPP) layer; a vehicle-to-everything (V2X)/ProSe layer; or an access stratum (AS) layer.
[0265] In some embodiments the at least one controller is configured to cause the processor to determine the one or more SL positioning QoS requirements by: inputting the one or more SL positioning QoS requirements from either of: a SL positioning application; or a LCS client.
[0266] In some embodiments, the at least one controller is further configured to cause the processor to: output the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
[0267] In some embodiments, the at least one controller is further configured to cause the processor to determine the mapping to correspond to a percentage or ratio of available SL positioning resources, preferably by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority which corresponds to a different percentage or ratio of available SL positioning resources.
[0268] In some embodiments, the SL positioning resources may be part of a dedicated resource pool or a shared/common resource pool. Examples of resources include slots, subframes, that can be used for transmitting SL PRS.
[0269] In some embodiments, there are 8 logical channels. The mapping between logical channel and available SL positioning resources can be a direct mapping. [0270] In some embodiments, the at least one controller is configured to cause the processor to determine the mapping by: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables from a network entity of a wireless communication network.
[0271] In some embodiments, the network entity is a gNB or LMF.
[0272] There is further provided a method in a processor for wireless communication, comprising: inputting one or more sidelink (SL) positioning quality of service (QoS) requirements associated with a request for SL positioning of a target UE; determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal (PRS) configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and outputting one or more SL PRS according to the one or more SL PRS configurations.
[0273] In some embodiments, the configuration may also comprise a comb-size including a number of symbols and resource element offsets, transmission bandwidth, etc.
[0274] In some embodiments, the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
[0275] In some embodiments, the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
[0276] In some embodiments, the latency category can be no delay; low delay; and delay tolerant. [0277] In some embodiments, the SL positioning QoS parameters comprise a mobility state of a UE.
[0278] In some embodiments, the mobility state can be based on an absolute velocity or a relative velocity, or absolute speed or relative speed, optionally in vertical or horizontal.
[0279] In some embodiments, the method comprises determining the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services (LCS) QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
[0280] In some embodiments, the method comprises determining the mapping in either of: a ranging/SL positioning communication layer; a SL positioning protocol (SLPP) layer; a vehicle-to-everything (V2X)/ProSe layer; or an access stratum (AS) layer.
[0281] In some embodiments the method comprises determining the one or more SL positioning QoS requirements by: inputting the one or more SL positioning QoS requirements from either of: a SL positioning application; or a LCS client.
[0282] In some embodiments, the method further comprises: outputting the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
[0283] In some embodiments, the method comprises determining the mapping to correspond to a percentage or ratio of available SL positioning resources, preferably by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority which corresponds to a different percentage or ratio of available SL positioning resources.
[0284] In some embodiments, the SL positioning resources may be part of a dedicated resource pool or a shared/common resource pool. Examples of resources include slots, subframes, that can be used for transmitting SL PRS. [0285] In some embodiments, there are 8 logical channels. The mapping between logical channel and available SL positioning resources can be a direct mapping.
[0286] In some embodiments, the method comprises determining the mapping by: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables from a network entity of a wireless communication network.
[0287] In some embodiments, the network entity is a gNB or LMF.
[0288] There is further provided, a network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: determine a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values; transmit the mapping to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
[0289] There is further provided, a method in a network entity, comprising: determining a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values; transmitting the mapping to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
[0290] In the context of SL positioning, a variety of SL Positioning techniques may be utilised to obtain good SL Positioning performance in terms of the received SL Positioning QoS, e.g., high accuracy or low latency positioning. This enables the computation of absolute location, relative location, distance, direction, velocity estimates for a single UE or amongst multiple UEs. SL PRS priority has been defined for the transmission of SL PRS, which assists in resource allocation and congestion control in SL, however a key open issue is the mechanism of how the SL PRS priority is mapped to the SL Positioning QoS. Since the SL Positioning QoS parameters may vary, a standardized method is required on how to map the SL PRS priority with the SL Positioning QoS. [0291] The disclosure herein describes methods to enable SL PRS priority to be mapped to different individual SL positioning QoS parameters, including absolute/relative horizontal/vertical accuracies, distance accuracy, direction accuracy, and mobility states. The disclosure herein also describes a consolidated method of mapping the SL PRS priority with all of the aforementioned SL positioning QoS parameters, considering the accuracy and positioning latency trade-off. The disclosure herein also describes the procedures of the communication stack, wherein the SL PRS priority is mapped to the SL Positioning QoS parameters and transferred to the lower layers, which assists in the transmission of SL PRS from one to another UE or other sets of UEs.
[0292] Currently, the SL Positioning QoS and transport SLPP/RSPP QoS handling has been described in the 3 GPP Technical Specification 23.586 titled “Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18)”, and SL PRS priorities have been defined in RANI for SL PRS transmission and further to be defined as 8-levels in RAN2. However, there has been no proposed solutions on how to map the SL PRS priority to SL Positioning QoS parameters and corresponding requirements.
[0293] The disclosure herein provides a method to describe various mechanisms to map the SL PRS priority to different SL Pos. QoS parameters are detailed. The disclosure herein provides a method to configure (i.e., pre-configure) a consolidated SL PRS priority mapping table, in addition a definition of a SL Positioning LCS Qos Class is further described. Furthermore, the disclosure herein provides a method to enable the procedures to map the SL PRS priority with the received SL Positioning QoS at the UE/device.
[0294] The disclosure herein provides a method in a wireless UE/device wherein: a first communication device receives SL Positioning QoS requirements associated to a location request from an LCS client/ Application and maps the requirements to SL Positioning QoS parameters; the first communication device selects a positioning method and an associated plurality of recommended SL PRS configuration parameters based on the received SL Positioning requirements; the recommended SL PRS configuration parameters comprising at least SL PRS priority; the first communication device determines an association/mapping amongst a set of SL PRS priorities according to the received SL Positioning QoS requirements; the first communication device selects a SL PRS priority according to the received SL Positioning QoS requirements; the first communication device transmits SL PRS to one or more other UE/devices according to the SL PRS priority and recommended SL PRS configuration.
[0295] In some embodiments the SL PRS priority values are mapped to SL positioning QoS parameters comprising absolute horizontal location accuracy, relative horizontal location accuracy, absolute vertical location accuracy, relative vertical location accuracy, horizontal distance, vertical distance, Azimuth direction accuracy or Zenith direction accuracy or combination thereof.
[0296] In some embodiments the SL PRS priority values are mapped according to SL positioning QoS parameters comprising a positioning response time/positioning latency defined as part of a received SL positioning location request.
[0297] In some embodiments the SL PRS priority values are mapped according to SL positioning QoS parameters, which are based on a category comprising of no delay, low delay or delay tolerant.
[0298] In some embodiments the SL PRS priority values are mapped according to SL positioning QoS parameters comprising the mobility state of the UE.
[0299] In some embodiments the SL PRS priority values are mapped according to all SL Positioning QoS parameters in a consolidated manner.
[0300] In some embodiments a SL Positioning LCS QoS Classes (SPLQC) may be defined to consolidate the one or more SL Positioning QoS Parameters and thereafter be mapped in a one-to-one manner with the SL-RS priority.
[0301] In some embodiments the SL PRS priority to SL Positioning QoS mapping may be performed in the Ranging/SL positioning communication layer, Sidelink positioning protocol layer or V2X/ProSe layer.
[0302] In some embodiments the first communication device transmits the SL PRS priority mapping table/profile to a second communication device using UE-specific signalling or broadcast or groupcast signalling. [0303] The disclosure herein also provides a method in a network apparatus, wherein the network apparatus performs the SL PRS priority to SL Positioning QoS mapping and transmits the mapping table/profile to the SL PRS transmitting UE and one or more receiving UEs using UE-specific signalling or broadcast signalling.
[0304] Figure 10 illustrates an example of a UE 1000 in accordance with aspects of the present disclosure. The UE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, 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.
[0305] The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, 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.
[0306] The processor 1002 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1002 may be configured to operate the memory 1004. In some other implementations, the memory 1004 may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the UE 1000 to perform various functions of the present disclosure.
[0307] The memory 1004 may include volatile or non-volatile memory. The memory 1004 may store computer-readable, computer-executable code including instructions when executed by the processor 1002 cause the UE 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1004 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.
[0308] In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause the UE 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004). For example, the processor 1002 may support wireless communication at the UE 1000 in accordance with examples as disclosed herein. The UE 1000 may be configured according to the various embodiments of a UE as described herein and/or to support a means for performing the methods described herein.
[0309] The controller 1006 may manage input and output signals for the UE 1000. The controller 1006 may also manage peripherals not integrated into the UE 1000. In some implementations, the controller 1006 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1006 may be implemented as part of the processor 1002.
[0310] In some implementations, the UE 1000 may include at least one transceiver 1008. In some other implementations, the UE 1000 may have more than one transceiver 1008. The transceiver 1008 may represent a wireless transceiver. The transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.
[0311] A receiver chain 1010 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1010 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1010 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 1010 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1010 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data. [0312] A transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1012 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 1012 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 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0313] Figure 11 illustrates an example of a processor 1100 in accordance with aspects of the present disclosure. The processor 1100 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1100 may include a controller 1102 configured to perform various operations in accordance with examples as described herein. The processor 1100 may optionally include at least one memory 1104, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 1100 may optionally include one or more arithmetic-logic units (ALUs) 1106. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0314] The processor 1100 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. 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 1100) 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). [0315] The controller 1102 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 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. For example, the controller 1102 may operate as a control unit of the processor 1100, generating control signals that manage the operation of various components of the processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0316] The controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1104 and determine subsequent instruction(s) to be executed to cause the processor 1100 to support various operations in accordance with examples as described herein. The controller 1102 may be configured to track memory address of instructions associated with the memory 1104. The controller 1102 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1102 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1102 may be configured to manage flow of data within the processor 1100. The controller 1102 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1100.
[0317] The memory 1104 may include one or more caches (e.g., memory local to or included in the processor 1100 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1104 may reside within or on a processor chipset (e.g., local to the processor 1100). In some other implementations, the memory 1104 may reside external to the processor chipset (e.g., remote to the processor 1100).
[0318] The memory 1104 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1100, cause the processor 1100 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 1102 and/or the processor 1100 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the processor 1100 to perform various functions. For example, the processor 1100 and/or the controller 1102 may be coupled with or to the memory 1104, the processor 1100, the controller 1102, and the memory 1104 may be configured to perform various functions described herein. In some examples, the processor 1100 may include multiple processors and the memory 1104 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.
[0319] The one or more ALUs 1106 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1106 may reside within or on a processor chipset (e.g., the processor 1100). In some other implementations, the one or more ALUs 1106 may reside external to the processor chipset (e.g., the processor 1100). One or more ALUs 1106 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1106 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1106 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 1106 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1106 to handle conditional operations, comparisons, and bitwise operations.
[0320] The processor 1100 may support wireless communication in accordance with examples as disclosed herein. The processor 1100 may be configured according to the various embodiments of a processor described herein and/or to or operable to support a means for performing the methods described herein.
[0321] Figure 12 illustrates an example of a NE 1200 in accordance with aspects of the present disclosure. The NE 1200 may include a processor 1202, a memory 1204, a controller 1206, and a transceiver 1208. The processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, 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.
[0322] The processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, 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.
[0323] The processor 1202 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1202 may be configured to operate the memory 1204. In some other implementations, the memory 1204 may be integrated into the processor 1202. The processor 1202 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the NE 1200 to perform various functions of the present disclosure.
[0324] The memory 1204 may include volatile or non-volatile memory. The memory 1204 may store computer-readable, computer-executable code including instructions when executed by the processor 1202 cause the NE 1200 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1204 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.
[0325] In some implementations, the processor 1202 and the memory 1204 coupled with the processor 1202 may be configured to cause the NE 1200 to perform one or more of the functions described herein (e.g., executing, by the processor 1202, instructions stored in the memory 1204). For example, the processor 1202 may support wireless communication at the NE 1200 in accordance with examples as disclosed herein. The NE 1200 may be configured according to the various embodiments of network entities described herein and/or to support a means for performing the methods described herein.
[0326] The controller 1206 may manage input and output signals for the NE 1200. The controller 1206 may also manage peripherals not integrated into the NE 1200. In some implementations, the controller 1206 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1206 may be implemented as part of the processor 1202.
[0327] In some implementations, the NE 1200 may include at least one transceiver 1208. In some other implementations, the NE 1200 may have more than one transceiver 1208. The transceiver 1208 may represent a wireless transceiver. The transceiver 1208 may include one or more receiver chains 1210, one or more transmitter chains 1212, or a combination thereof.
[0328] A receiver chain 1210 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1210 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1210 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 1210 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1210 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0329] A transmitter chain 1212 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1212 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 1212 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 1212 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0330] Figure 13 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.
[0331] At 1302, the method may include determining one or more SL positioning QoS requirements associated with a request for SL positioning of a target UE. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a UE as described with reference to Figure 10.
[0332] At 1304, the method may include determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL PRS configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a UE as described with reference to Figure 10.
[0333] At 1306, the method may include determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements. The operations of 1306 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1306 may be performed a UE as described with reference to Figure 10.
[0334] At 1308, the method may include determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values. The operations of 1308 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1308 may be performed by a UE as described with reference to Figure 10. [0335] At 1310, the method may include selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations. The operations of 1310 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1310 may be performed by a UE as described with reference to Figure 10.
[0336] At 1312, the method may include transmitting one or more SL PRS according to the one or more SL PRS configurations. The operations of 1312 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1312 may be performed by a UE as described with reference to Figure 10.
[0337] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0338] Figure 14 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a processor as described herein. In some implementations, the processor may execute a set of instructions to control the function elements of the processor to perform the described functions.
[0339] At 1402, the method may include inputting one or more SL positioning QoS requirements associated with a request for SL positioning of a target UE. The operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a processor as described with reference to Figure 11.
[0340] At 1404, the method may include determining, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL PRS configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a processor as described with reference to Figure 11.
[0341] At 1406, the method may include determining one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements. The operations of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1406 may be performed a processor as described with reference to Figure 11.
[0342] At 1408, the method may include determining a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values. The operations of 1408 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1408 may be performed by a processor as described with reference to Figure 11.
[0343] At 1410, the method may include selecting, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations. The operations of 1410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1410 may be performed by a processor as described with reference to Figure 11.
[0344] At 1412, the method may include outputting one or more SL PRS according to the one or more SL PRS configurations. The operations of 1412 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1412 may be performed by a processor as described with reference to Figure 11.
[0345] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0346] Figure 15 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
[0347] At 1502, the method may include determining a mapping of one or more sidelink (SL) positioning Quality of Service (QoS) parameters to a set of SL positioning reference signal (PRS) priority values. The operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a NE as described with reference to Figure 12.
[0348] At 1504, the method may include transmitting the mapping to at least one user equipment (UE), wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS. The operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a NE as described with reference to Figure 12.
[0349] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0350] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
[0351] The following abbreviations are relevant in the field addressed by this document:
ADR, Accumulated Delta-Range; A GNSS, Assisted GNSS; AP, Access Point; AoD, Angle-of-Departure; AoA, Angle-of-Arrival; ARFCN, Absolute Radio Frequency Channel Number; ARP, Antenna Reference Point; BFD, Beam failure detection; BSSID, Basic Service Set Identifier; BTS, Base Transceiver Station (GERAN); BWP, Bandwidth Part; CBR, Channel Busy Ratio; CG, Configured Grant; CID, Cell-ID (positioning method); CRS, Cell-specific Reference Signals; CSI, Channel State Information; CSI-RS, Channel State Information Reference Signal; DCI, Downlink Control Information; DL, Downlink; DL-AoD, Downlink Angle-of-Departure; DL-TDOA, Downlink Time Difference Of Arrival; DM-RS, DeModulation Reference Signal; DS-TWR, Double-sided Two Way Ranging; ECEF, Earth-Centered, Earth-Fixed; ECGI, Evolved Cell Global Identifier; E CID, Enhanced Cell-ID (positioning method); E-SMLC, Enhanced Serving Mobile Location Centre; E-UTRAN, Evolved Universal Terrestrial Radio Access Network; EOP, Earth Orientation Parameters; EPDU, External Protocol Data Unit; FDMA, Frequency Division Multiple Access; FEC, Forward Error Correction; FTA, Fine Time Assistance; GAGAN, GPS Aided Geo Augmented Navigation; GNSS, Global Navigation Satellite System; GPS, Global Positioning System; HA GNSS, High-Accuracy GNSS (RTK, PPP); IMU, Inertial Measurement Unit; IS, Interface Specification; LMC, Location Management Component; LMF, Location Management Function; LMU, Location Measurement Unit; LOS, Line-of-sight; LPP, LTE Positioning Protocol; LPPa, LTE Positioning Protocol Annex; LSB, Least Significant Bit; MAC, Master Auxiliary Concept; , Medium Access Control; MAC CE, Medium Access Control Element ; MBS, Metropolitan Beacon System; MO-LR, Mobile Originated Location Request; MSB, Most Significant Bit; MT-LR, Mobile Terminated Location Request; Multi-RTT, Multiple-Round Trip Time; NAV, Navigation; NB-IoT, NarrowBand Internet of Things; NCGI, NR Cell Global Identifier ; NI-LR, Network Induced Location Request; NLOS, Non-line-of-sight; NPRS, Narrowband Positioning Reference Signals; NR, NR Radio Access; NRPPa, NR Positioning Protocol Annex; NRSRP, Narrowband Reference Signal Received Power; NRSRQ, Narrowband Reference Signal Received Quality; OSR, Observation Space Representation; OTDOA, Observed Time Difference Of Arrival; PDU, Protocol Data Unit; PDCP, Packet Data Convergence Protocol; PDCCH, Physical Downlink Control Channel; PDSCH, Physical Downlink Shared Channel; PHY, Physical Layer; PSCCH, Physical Sidelink Control Channel; PSSCH, Physical Sidelink Shared Channel; PSBCH, Physical Sidelink Broadcast Channel; PPP, Precise Point Positioning; PQI, PC5 5G QoS Identifier; PRB, Physical Resource Block; PRC, Pseudo Range Correction; PRS, Positioning Reference Signals; posSIB, Positioning System Information Block; P-RNTI, Paging-Radio Network Temporary Identifier; PT-RS, Phase Tracking Reference Signal; PUCCH, Physical Uplink Control Channel; PUSCH, Physical Uplink Shared Channel; QCL, Quasi CoLocation; QoS, Quality of Service; RAT, Radio Access Technology; RF, Radio Frequency; RLC, Radio Link Control; RP, Resource Pool or Reception Point; RRC, Range Rate Correction; Radio Resource Control; RRM, Radio Resource Management; RS, Reference Signal; RSRP, Reference Signal Received Power; RSPP, Ranging Sidelink Positioning Protocol; RSRQ, Reference Signal Received Quality; RSTD, Reference Signal Time Difference; RSU, Roadside Unit; RTK, Real-Time Kinematic; RTOA, Relative Time of Arrival; RTT, Round Trip Time; SA, Standalone; SBAS, Space Based Augmentation System; SBCH, Sidelink Broadcast Channel; SCCH, Sidelink Control Channel; SCI, Sidelink Control Information; SET, SUPL Enabled Terminal; SFN, System Frame Number; SL, Sidelink; SL PRS, Sidelink Positioning Reference Signal; SLP, SUPL Location Platform; SLPP, SL Positioning Protocol; SPS, Semi -Persistent Scheduling; SS/PBCH Synchronization Signal/Physical Broadcast Channel; SSBRI, SS/PBCH Block Resource Index; SSID, Service Set Identifier; SSR, State Space Representation; SS-TWR, Singlesided Two Way Ranging; STCH, Sidelink Transport Channel; SUPL, Secure User Plane Location; TA, Timing-Advance; TB, Terrestrial Beacon; TBS, Terrestrial Beacon System; TCI, Transmission Configuration Indicator; TDRA, Time Domain Resource Allocation/Assignment; TECU, TEC Units; TLM, Telemetry; TOA, Time Of Arrival; TOF, Time of Flight; TP, Transmission Point; TRP, Transmission-Reception Point; UE, User Equipment; UDRE, User Differential Range Error; ULP, User Plane Location Protocol;
URA, User Range Accuracy; UTC, Coordinated Universal Time; WGS 84, World Geodetic System 1984; and WLAN, Wireless Local Area Network.

Claims

CLAIMS What is claimed is:
1. A user equipment ‘UE’ for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine one or more sidelink ‘SL’ positioning quality of service ‘QoS’ requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal ‘PRS’ configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and transmit one or more SL PRS according to the one or more SL PRS configurations.
2. The UE of claim 1, wherein the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
3. The UE of any preceding claim 1, wherein the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
4. The UE of any preceding claim, wherein the SL positioning QoS parameters comprise a mobility state of the UE.
5. The UE of any preceding claim, wherein the at least one processor is configured to cause the UE to determine the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services ‘LCS’ QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
6. The UE of any preceding claim, wherein the at least one processor is configured to cause the UE to determine the mapping in either of: a ranging/SL positioning communication layer; a SL positioning protocol ‘SLPP’ layer; a vehicle-to-everything ‘ V2X’/ProSe layer; or an access stratum ‘AS’ layer.
7. The UE of any preceding claim, wherein the at least one processor is further configured to cause the UE to: transmit, to at least one other UE, the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
8. The UE of any preceding claim, wherein the at least one processor is further configured to cause the UE to determine the mapping to correspond to a percentage or ratio of available SL positioning resources.
9. The UE of claim 8, wherein the at least one processor is configured to cause the UE to determine the mapping to correspond to a percentage or ratio of available SL positioning resources by mapping, in a one-to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority, which corresponds to a different percentage or ratio of available SL positioning resources.
10. The UE of claim 8, wherein the at least one processor is configured to cause the UE to apply the percentage or ratio of available SL positioning resources to: a SL PRS dedicated resource pool; and/or a SL PRS shared or common resource pool.
11. The UE of any preceding claim, wherein the at least one processor is configured to cause the UE to determine the mapping by: generating one or more mapping tables; accessing one of more preconfigured mapping tables; or receiving one or more mapping tables, from a network entity of a wireless communication network.
12. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: input one or more sidelink ‘SL’ positioning quality of service ‘QoS’ requirements associated with a request for SL positioning of a target UE; determine, based on the one or more SL positioning QoS requirements, one or more SL positioning methods having associated SL positioning reference signal ‘PRS’ configurations, wherein each SL PRS configuration comprises at least a SL positioning priority parameter; determine one or more SL positioning QoS parameters based on the one or more SL positioning QoS requirements; determine a mapping of the SL positioning QoS parameters amongst a set of SL PRS priority values; select, based on the mapping, SL PRS priority values for the SL positioning priority parameters of the SL PRS configurations; and output one or more SL PRS according to the one or more SL PRS configurations.
13. The processor of claim 12, wherein the SL positioning QoS parameters are selected from the list of SL positioning QoS parameters comprising: absolute horizontal location accuracy; absolute vertical location accuracy; relative horizontal location accuracy; relative vertical location accuracy; horizontal distance accuracy; vertical distance accuracy; azimuth direction accuracy; and zenith direction accuracy.
14. The processor of any one of claims 12-13, wherein the SL positioning QoS parameters comprise: a positioning response time or positioning latency; and/or a positioning response time/latency category.
15. The processor of any one of claims 12-14, wherein the SL positioning QoS parameters comprise a mobility state of a UE.
16. The processor of any one of claims 12-15, wherein the at least one controller is configured to cause the processor to determine the mapping based on: a one-to-one mapping of each SL PRS priority value to each of the SL positioning QoS parameters; a mapping of each SL PRS priority value to a combination, preferably all, of the SL positioning QoS parameters; or a one-to-one mapping of each SL PRS priority value to a SL positioning location services ‘LCS’ QoS class, each SL positioning LCS QoS class being mapped to one or more of the SL positioning QoS parameters.
17. The processor of any one of claims 12-16, wherein the at least one controller is configured to cause the processor to determine the mapping in either of: a ranging/SL positioning communication layer; a SL positioning protocol ‘SLPP’ layer; a vehicle-to-everything ‘ V2X’/ProSe layer; or an access stratum ‘AS’ layer.
18. The processor of any one of claims 12-17, wherein the at least one controller is further configured to cause the processor to: output the mapping of the SL positioning QoS parameters amongst the set of SL PRS priority values.
19. The processor of any one of claims 12-18, wherein the at least one controller is further configured to cause the processor to determine the mapping to correspond to a percentage or ratio of available SL positioning resources, preferably by mapping, in a one- to-one manner, the SL PRS priority values to logical channels for carrying SL PRS transmissions, wherein each logical channel optionally has an associated logical channel priority which corresponds to a different percentage or ratio of available SL positioning resources.
20. A network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: determine a mapping of one or more sidelink ‘SL’ positioning Quality of Service ‘QoS’ parameters to a set of SL positioning reference signal ‘PRS’ priority values; transmit the mapping to at least one user equipment ‘UE’, wherein the at least one UE comprises a UE for transmitting one or more SL PRS and/or a UE for receiving one or more SL PRS.
PCT/EP2023/081361 2023-10-02 2023-11-09 Mapping sidelink positioning reference signal priority in a wireless communication system WO2024153362A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20230100805 2023-10-02
GR20230100805 2023-10-02

Publications (1)

Publication Number Publication Date
WO2024153362A1 true WO2024153362A1 (en) 2024-07-25

Family

ID=88792997

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/081361 WO2024153362A1 (en) 2023-10-02 2023-11-09 Mapping sidelink positioning reference signal priority in a wireless communication system

Country Status (1)

Country Link
WO (1) WO2024153362A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022212533A1 (en) * 2021-03-30 2022-10-06 Idac Holdings, Inc. Nr positioning - methods for resource provision in sidelink positioning
WO2023154782A1 (en) * 2022-02-09 2023-08-17 Interdigital Patent Holdings, Inc. Transmission of sl-prs on condition that associated parameters are within a predetermined range

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022212533A1 (en) * 2021-03-30 2022-10-06 Idac Holdings, Inc. Nr positioning - methods for resource provision in sidelink positioning
WO2023154782A1 (en) * 2022-02-09 2023-08-17 Interdigital Patent Holdings, Inc. Transmission of sl-prs on condition that associated parameters are within a predetermined range

Non-Patent Citations (27)

* Cited by examiner, † Cited by third party
Title
"5G System (5GS) Location Services (LCS", 3GPP TS 23.273
"5G System (5GS) Location Services (LCS) Stage 2 (Release 18", 3GPP TECHNICAL SPECIFICATION 23.273
"5G System (5GS) Location Services (LCS) Stage 2 (Release 18)", 3GPP TECHNICAL SPECIFICATION 23.273
"5G System (5GS) Location Services (LCS)", 3GPP TS 23.273
"Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18", 3GPP TECHNICAL SPECIFICATION 23.586
"Architectural Enhancements to support Ranging based services and Sidelink positioning (Release 18)", 3GPP TECHNICAL SPECIFICATION 23.586
"Architectural Enhancements to support Ranging based services and Sidelink positioning", 3GPP TS 23.586
"Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services'' (Release 18", 3GPP TS 23.287
"Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services", 3GPP TS 23.287
"Location Management Services; Stage 3", 3GPP TS 29.572
"Location Services (LCS); Service description; Stage 1", 3GPP TS 22.071
"Location Services (LCS);Service description; Stage 1", 3GPP TS 22.071
"Physical-layer Measurements", 3GPP TS 38.215
"Proximity based Services (ProSe) in the 5G System (5GS", 3GPP TS 23.304
"Proximity based Services (ProSe) in the 5G System (5GS)", 3GPP TS 23.304
"rchitectural Enhancements to support Ranging based services and Sidelink positioning (Release 18)", 3GPP TECHNICAL SPECIFICATION 23.586
"Sidelink Positioning Protocol (SLPP); Protocol specification", 3GPP TS 38.355
"Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN", 3GPP TS 38.305
"Study on enhancements for cyberphysical control applications in vertical domains", 3GPP TR 22.832
"Study on expanded and improved NR positioning", 3GPP TR 38.
"Study on NR Positioning Enhancements (Release 17", 3GPP TR 38.857
"Study on NR positioning support (Release 16", 3GPP TR 38.855
3GPP TS 22.104
3GPP TS 22.186
3GPP TS 22.261
3GPP TS 23.502
XIAOWEI JIANG ET AL: "Discussion on SL positioning", vol. 3GPP RAN 2, no. Toulouse, FR; 20230821 - 20230825, 11 August 2023 (2023-08-11), XP052443217, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_123/Docs/R2-2307507.zip R2-2307507 Discussion on SL positioning.doc> [retrieved on 20230811] *

Similar Documents

Publication Publication Date Title
US11681010B2 (en) Measurements and reporting for user equipment (UE) positioning in wireless networks
US20200154240A1 (en) Methods and systems for on-demand transmission of a positioning reference signal in a wireless network
CN115699920B (en) User equipment positioning signal measurement and/or transmission
US11889336B2 (en) System and methods for rapid round-trip-time measurement
CN112956254A (en) System and method for supporting uplink and downlink position determination procedures in a wireless network
EP4289190A1 (en) Positioning reference signal measurement for joint positioning
US20230081093A1 (en) Physical layer considerations for ue positioning
KR20230107205A (en) Muting configuration for tracking reference signal for positioning
US11971499B2 (en) Distributed device management for positioning
WO2024153362A1 (en) Mapping sidelink positioning reference signal priority in a wireless communication system
US20240146486A1 (en) Processing gap requesting and/or error reporting
US20240036147A1 (en) Resource selection and prioritization of sidelink positioning operations
US20240172169A1 (en) On-demand positioning reference signal scheduling
US20240244570A1 (en) Device selection for ue positioning
WO2024069439A1 (en) Resource scheduling and processing for sidelink positioning
WO2024069435A1 (en) Resource allocation for sidelink positioning group
WO2024075088A1 (en) Combined one-to-many and many-to-one sidelink positioning
WO2024033843A1 (en) Priority criteria for positioning information
WO2023166396A1 (en) Configuring sidelink positioning reference signals from base station
WO2023148666A1 (en) Sidelink positioning reference signal processing
WO2023242804A1 (en) Wireless angle-based positioning
WO2023180847A1 (en) Sidelink anchor device management
KR20240096478A (en) Coupled resource pools
WO2023148638A1 (en) Sidelink positioning measurement procedures
KR20240038719A (en) Measurement gaps for measuring positioning signals

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: 23805536

Country of ref document: EP

Kind code of ref document: A1