FIRST APPLIANCE, WIRELESS COMMUNICATION PROCESSOR, WIRELESS COMMUNICATION USER EQUIPMENT, AND WIRELESS COMMUNICATION NETWORK EQUIPMENT

Abstract

Various aspects of the present disclosure relate to sidelink positioning assistance. An apparatus, such as a user equipment (UE), transmits a configuration message (e.g., to a network equipment) including an indication to perform one or more of sidelink positioning reference signal (SL-PRS) or SL positioning data message transmission, and the configuration message includes one or more SL positioning parameters. The apparatus receives a resource configuration message including a set of time-frequency resources in which to perform the one or more of the SL-PRS or SL positioning data message transmission.

Description

1 / 92 “FIRST APPARATUS, WIRELESS COMMUNICATION PROCESSOR, WIRELESS COMMUNICATION USER EQUIPMENT AND WIRELESS COMMUNICATION NETWORK EQUIPMENT” Related Orders

[001] This application claims priority over U.S. Non-Provisional Application Serial No. 18 / 805,183, filed August 14, 2024, entitled “SIDELINK POSITIONING ASSISTANCE,” the disclosure of which is incorporated herein by reference in full. This application also claims priority over U.S. Provisional Application Serial No. 63 / 532,984, filed August 16, 2023, entitled “ASSISTANCE OF "SIDELINK POSITIONING STATEMENT", the disclosure of which is incorporated herein by reference in its entirety. TECHNICAL AREA

[002] This disclosure relates to wireless communications and, more specifically, to the positioning of devices in wireless communications. Background of the Invention

[003] A wireless communications system may include one or more network communication devices, such as base stations, which may support wireless communications to one or more user communication devices, which may also be known as user equipment (UE) or other suitable terminology. The wireless communications system may support wireless communications with one or more user communication devices by utilizing wireless communications system features (e.g., timing features (e.g., symbols, slots, subframes, frames, or the like) or frequency features (e.g., subcarriers, carriers, or the like). Furthermore, the wireless communications system may support wireless communications on multiple Petition 870250089739, dated 02 / 10 / 2025, pages 110 / 209 2 / 92 radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies in addition to 5G (e.g., sixth generation (6G)).

[004] In a wireless communications system, determining the position of a UE can be important, such as for emergency services. However, current positioning techniques can be inaccurate and / or inefficient. Brief Description of the Invention

[005] The article “a” before an element is unrestricted and understood as referring to “at least one” of those elements or to “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 (for example, a list of items preceded by a phrase such as “at least one of” or “one or more of” or “one or both of”) indicates an inclusive list, so 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). Furthermore, as used herein, the phrase “based on” should not be interpreted as a reference to a closed set of conditions. For example, an example step described as “based on condition A” may be based on either condition A or condition B without departing from the scope of this disclosure.In other words, as used here, the expression “based on” should be interpreted in the same way as the expression “based at least in part on”. Furthermore, as used here, including in the claims, a “set” may include one or more elements.

[006] Some implementations of the method and devices described herein may also include transmission from a UE to a device of Petition 870250089739, dated 02 / 10 / 2025, p. 111 / 209 3 / 92 network (NE), a configuration message including an indication to perform one or more sidelink positioning reference signal (SL-PRS) or SL positioning data message transmissions, the configuration message including one or more SL positioning parameters; and receive, from the second device, a resource configuration message including a time-frequency resource set to perform one or more SL-PRS or SL positioning data message transmissions.

[007] In some implementations of the method and devices described herein, the UE receives a higher-layer trigger to perform one or more transmissions of SL-PRS or SL positioning data messages; the higher-layer trigger includes one or more of the following: sidelink positioning protocol layer (SLPP), vehicle-to-all layer (V2X), ProSe layer, range layer, SL positioning layer, or sidelink positioning application layer; the UE receives the higher-layer trigger from another UE by means of one or more of: higher-layer signaling, including one or more of the following: sidelink positioning protocol layer (SLPP), PC5 radio resource control (RRC), or PC5-S; or lower-layer signaling, including one or more of the following: first-stage sidelink control information (SCI), first-stage medium access control (MAC) control element (CE), second-stage SCI, or second-stage MAC CE;The configuration message includes one or more SL positioning quality of service (QoS) profiles, at least one transport QoS profile indicating SL positioning transport QoS parameters, an SL positioning session identifier, SL-PRS transmission characteristics, or one or more discovered UEs for SL positioning.

[008] In some implementations of the method and devices Petition 870250089739, dated 02 / 10 / 2025, pp. 112 / 209 4 / 92 described herein, the UE receives a system information message including one or more common SL positioning configurations, the one or more common SL positioning configurations including at least one from a list of SL positioning radio carrier configuration, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information; the UE includes one or more destination UEs, anchor UEs, server UEs, or devices configured to perform one or more SL-PRS or SL positioning data message transmissions; the configuration message includes one or more of: an SL positioning transmission resource request; at least one unicast, groupcast, or broadcast destination list from the SL positioning receiver;one or more of a list of SL positioning transmitter or receiver frequencies; SL positioning UE type; one or more SL positioning capabilities; an SL positioning transmission resource discovery request; an SL positioning destination identifier; an SL positioning conversion type; or a coverage status of a discovered UE; the configuration message includes one or more dedicated shared SL-PRS pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more dedicated SL-PRS and SL communication data resource pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission;The configuration message includes a coverage status indication for a set of uncovered UEs, where the coverage status indication specifies whether each uncovered UE is in or out of coverage.

[009] Some implementations of the method and devices Petition 870250089739, dated 02 / 10 / 2025, p. 113 / 209 5 / 92 described herein may further include the transmission, from the UE to a NE, of a configuration message including an indication to perform one or more transmissions of SL-PRS or SL positioning data messages, the configuration message including one or more SL positioning parameters; and the receipt, from the NE, of a resource configuration message including a set of time-frequency resources to perform one or more transmissions of SL-PRS or SL positioning data messages.

[0010] Some implementations of the method and devices described herein further include receiving a higher-layer trigger to perform one or more transmissions of SL-PRS or SL positioning data messages; the higher-layer trigger includes one or more of the following: Sidelink Positioning Protocol Layer (SLPP), Vehicle-to-Everything Layer (V2X), ProSe Layer, Range Layer, SL Positioning Layer, or Sidelink Positioning Application Layer; receiving the higher-layer trigger from a UE via one or more of the following: higher-layer signaling, including one or more of the following: Sidelink Positioning Protocol Layer (SLPP), PC5 RRC, or PC5-S layers; or lower-layer signaling, including one or more of the following: first-stage SCI, first-stage MAC CE, second-stage SCI, or second-stage MAC CE;The configuration message includes one or more of: an SL positioning QoS profile, at least one transport QoS profile indicating SL positioning transport QoS parameters, an SL positioning session identifier, SL-PRS transmission characteristics, or one or more UE discoveries for SL positioning.

[0011] Some implementations of the method and devices described here also include receiving an information message from Petition 870250089739, dated 02 / 10 / 2025, pp. 114 / 209 6 / 92 system including one or more common SL positioning configurations, the one or more common SL positioning configurations including at least one of a list of SL positioning radio carrier configuration, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning validity configuration information including time-based validity (e.g., a timer, a validity time and so on) and / or area-based validity, e.g., zone information, physical cell identity (PCI), system information block (SIB) area validity, cell identifiers (IDs), common SL positioning measurement information, etc.; the UE includes one or more of a destination UE, an anchor UE, a server UE or a device configured to perform one or more SL-PRS or SL positioning data message transmissions;The configuration message includes one or more of: an SL positioning transmission resource request; at least one unicast, groupcast, or broadcast destination list for the SL positioning receiver; one or more SL positioning transmitter or receiver frequency lists; SL positioning UE type; one or more SL positioning capabilities; an SL positioning transmission resource discovery request; an SL positioning destination identifier; an SL positioning conversion type; or a coverage status of a discovered UE; the configuration message includes one or more dedicated shared SL-PRS pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission;The configuration message includes one or more dedicated SL-PRS and SL communication data resource pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one; Petition 870250089739, dated 02 / 10 / 2025, pp. 115 / 209 7 / 92 uncovered EU set, an indication of coverage status of an uncovered EU set, and where the coverage status indication includes whether each uncovered EU is in or out of coverage.

[0012] Some implementations of the method and devices described herein may further include a processor to transmit, from a first device to a second device, a configuration message including an indication to perform one or more transmissions of SL-PRS or SL positioning data messages, the configuration message including one or more SL positioning parameters; and to receive, from the second device, a resource configuration message including a set of time-frequency resources to perform one or more transmissions of SL-PRS or SL positioning data messages.

[0013] In some implementations of the method and devices described herein, the processor receives an upper-layer trigger to execute one or more SL-PRS or SL positioning data message transmissions; the upper-layer trigger includes one or more of the following: Sidelink Positioning Protocol Layer (SLPP), Vehicle-to-Everything Layer (V2X), ProSe Layer, Range Layer, SL Positioning Layer, or Sidelink Positioning Application Layer; or at least one controller is configured to cause the processor to receive the upper-layer trigger from a UE via one or more of the following: upper-layer signaling, including one or more of the following: Sidelink Positioning Protocol Layer (SLPP), PC5 Radio Resource Control (RRC), or PC5-S layers; or lower-layer signaling, including one or more of the following: First-Stage SCI, First-Stage MAC CE, Second-Stage SCI, or Second-Stage MAC CE layers;The configuration message includes one or more SL positioning QoS profiles, and at least one transport QoS profile indicating QoS parameters; Petition 870250089739, dated 02 / 10 / 2025, pages 116 / 209 8 / 92 SL positioning transport, an SL positioning session identifier, SL-PRS transmission characteristics, or one or more discovered UEs for SL positioning; receive a system information message including one or more common SL positioning configurations, one or more common SL positioning configurations including at least one from a list of SL positioning radio carrier configurations, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0014] In some implementations of the method and devices described herein, the first device includes one or more of a target UE, an anchor UE, a server UE, or a device configured to perform one or more SL-PRS or SL positioning data message transmissions; the configuration message includes one or more of: an SL positioning transmission resource request; at least one list of unicast, groupcast, or broadcast SL positioning receiver destinations; one or more lists of SL positioning transmitter or receiver frequencies; SL positioning UE type; one or more SL positioning capabilities; an SL positioning transmission resource discovery request; an SL positioning destination identifier; an SL positioning transmission type; or a coverage status of a discovered UE;The configuration message includes one or more dedicated shared SL-PRS pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more dedicated SL-PRS and SL communication data resource pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; Petition 870250089739, dated 02 / 10 / 2025, pp. 117 / 209 9 / 92 Scheme 2; the configuration message includes a coverage status indication for a set of uncovered UEs, and the coverage status indication includes whether each uncovered UE is in or out of coverage.

[0015] Some implementations of the method and devices described herein may also include receiving, in a NE of a second device, a configuration message including an indication to perform one or more SL-PRS or SL positioning data message transmissions, the configuration message including one or more SL positioning parameters; and transmitting, to the second device, a resource configuration message including a set of time-frequency resources in which it performs one or more SL-PRS or SL positioning data message transmissions.

[0016] In some implementations of the method and devices described herein, the NE transmits a system information message including one or more common SL positioning configurations; the one or more common SL positioning configurations include at least one of a list of SL positioning radio carrier configuration, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0017] Some implementations of the method and devices described herein may also include receiving, in the NE and from a UE, a configuration message including an indication to perform one or more transmissions of SL-PRS or SL positioning data messages, the configuration message including one or more SL positioning parameters; and transmitting, to the UE, a resource configuration message including a set of time-frequency resources in which Petition 870250089739, dated 02 / 10 / 2025, pp. 118 / 209 10 / 92 performs one or more transmissions of SL-PRS or SL positioning data messages.

[0018] Some implementations of the method and apparatus described herein may further include the transmission of a system information message including one or more common SL positioning configurations; one or more common SL positioning configurations include at least one of a list of SL positioning radio carrier configuration, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0019] Some implementations of the method and devices described herein may also include the generation of a semi-static configuration of one or more SL-PRS transmission features, including one or more SL positioning pools or shared resources; and transmitting the semi-static configuration to a UE.

[0020] In some implementations of the method and devices described herein, the semistatic configuration is associated with one or more validity periods or validity areas; the NE transmits the semistatic configuration as one or more of a solicited message or an unsolicited message; the NE transmits to the UE an indication of unavailability of the SL positioning semistatic configuration; the SL-PRS transmission characteristics include one or more of: dedicated SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL-PRS transmissions; dedicated SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL positioning transmissions; dedicated SL positioning resource pool identifier for one or more transmissions Petition 870250089739, dated 02 / 10 / 2025, pages 119 / 209 11 / 92 of SL-PR of Mode 2 or Scheme 2; dedicated SL positioning resource pool identifier for one or more SL positioning transmissions of Mode 2 or Scheme 2; shared SL positioning resource pool identifier for one or more SL-PRS positioning transmissions of Mode 1 or Scheme 1; shared SL positioning resource pool identifier for one or more SL positioning transmissions of Mode 1 or Scheme 1; shared SL positioning resource pool identifier for one or more SL-PRS positioning transmissions of Mode 2 or Scheme 2; shared SL positioning resource pool identifier for one or more SL positioning transmissions of Mode 2 or Scheme 2;or SL-PRS resource index including one or more SL-PRS bandwidths, SL-PRS comb sizes, SL-PRS periodicity, SL-PRS resource identifier, SL-PRS identifier, SL placement session identifier, SL bandwidth portion (BWP) identifier, SL carrier identifier, or SL-PRS repeats.

[0021] In some implementations of the method and devices described herein, the NE transmits the semi-static configuration by means of one or more UE-specific signals or transmission signals; the NE activates the semi-static configuration by means of one or more UE-specific signals or transmission signals; and deactivates the semi-static configuration by means of one or more UE-specific signals or transmission signals.

[0022] Some implementations of the method and devices described herein may also include the generation, in an NE, of a semi-static configuration of one or more SL-PRS transmission features, including one or more SL positioning pools or shared resources; and the transmission of the semi-static configuration to a UE. Petition 870250089739, dated 02 / 10 / 2025, pp. 120 / 209 12 / 92

[0023] In some implementations of the method and devices described herein, the semistatic configuration is associated with one or more validity periods or validity areas; transmitting the semistatic configuration as one or more solicited messages or unsolicited messages; transmitting to the UE an indication of unavailability of the SL positioning semistatic configuration; the SL-PRS transmission features include one or more of: dedicated SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL-PRS transmissions; dedicated SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL positioning transmissions; dedicated SL positioning resource pool identifier for one or more Mode 2 or Scheme 2 SL-PR transmissions;Identifier of dedicated SL positioning resource pool for one or more Mode 2 or Scheme 2 SL positioning transmissions; identifier of shared SL positioning resource pool for one or more Mode 1 or Scheme 1 SL-PRS positioning transmissions; identifier of shared SL positioning resource pool for one or more Mode 1 or Scheme 1 SL positioning transmissions; identifier of shared SL positioning resource pool for one or more Mode 2 or Scheme 2 SL-PRS positioning transmissions; identifier of shared SL positioning resource pool for one or more Mode 2 or Scheme 2 SL positioning transmissions;or SL-PRS resource index including one or more SL-PRS bandwidths, SL-PRS comb sizes, SL-PRS periodicity, SL-PRS resource identifier, SL-PRS identifier, SL placement session identifier, SL BWP identifier, SL carrier identifier, or SL-PRS repeats. Petition 870250089739, dated 02 / 10 / 2025, pages 121 / 209 13 / 92

[0024] Some implementations of the method and devices described herein include transmitting the semistatic configuration by means of one or more specific UE signals or transmission signals; one or more of the following: activating the semistatic configuration by means of one or more specific UE signals or transmission signals; or deactivating the semistatic configuration by means of one or more specific UE signals or transmission signals. Brief Description of the Drawings

[0025] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0026] Figure 2 illustrates an example of a system for NR beam-based positioning in accordance with aspects of the present disclosure.

[0027] Figure 3 illustrates example scenarios for absolute and relative positioning scenarios.

[0028] Figure 4 illustrates an example of a multicellular Round Trip Time (RTT) procedure in accordance with aspects of the present disclosure.

[0029] Figure 5 illustrates an example of a system for relative range estimation using a gNB RTT positioning framework.

[0030] Figure 6 illustrates an example procedure to enable a UE to obtain sidelink positioning and / or range location results.

[0031] Figure 7 illustrates a procedure to enable a Location Services Client (LCS) and / or an AF to obtain range positioning and / or sidelink location results for a group of n UEs.

[0032] Figure 8 illustrates an example procedure for controlling the range and / or positioning of SL, as for UE-only operation. Petition 870250089739, dated 02 / 10 / 2025, pp. 122 / 209 14 / 92

[0033] Figure 9 illustrates an example procedure for a device to initiate a request to exchange SLPP message data and / or transmit SL-PRS with the gNB server in accordance with aspects of this disclosure.

[0034] Figure 10 illustrates an example of a procedure that supports sidelink placement assistance in accordance with aspects of this disclosure.

[0035] Figure 11 illustrates an example of a procedure that supports sidelink placement assistance in accordance with aspects of this disclosure.

[0036] Figure 12 illustrates an example of a procedure that supports sidelink placement assistance in accordance with aspects of this disclosure.

[0037] Figure 13 illustrates an example of a UE in accordance with aspects of this disclosure.

[0038] Figure 14 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0039] Figure 15 illustrates an example of a NE in accordance with aspects of this disclosure.

[0040] Figure 16 illustrates a flowchart of a method executed by a UE in accordance with aspects of this disclosure.

[0041] Figure 17 illustrates a flowchart of a method performed by a NE in accordance with aspects of this disclosure.

[0042] Figure 18 illustrates a flowchart of a method performed by a NE in accordance with aspects of this disclosure. Detailed Description of the Invention

[0043] SL placement structures were discussed to support varying target placement parameters in different cases. Petition 870250089739, dated 02 / 10 / 2025, pp. 123 / 209 15 / 92 of use. SL positioning, for example, is intended to be applied to a variety of use cases, such as V2X, public safety, IIoT, and commercial use cases. One objective of SL positioning is to determine the absolute and relative position of an UE using SL positioning methods, such as SL RTT-type methods, including one-sided and two-sided RTT, SL-AoA, and SL-time-of-arrival-difference (TDOA). SL positioning can utilize the new SL PRS that is transmitted via the PC5 interface and can be supported in multiple coverage scenarios (e.g., coverage, partial coverage, and out-of-coverage scenarios) and for PC5-only operation scenarios and PC5-Uu-based sets. Furthermore, for the exchange of SL positioning-related information between UEs via the PC5 interface, a new protocol called SLPP was discussed.

[0044] According to at least one Uu positioning framework, the delivery of positioning assistance data, including the DL-PRS (downlink positioning reference signal) configuration, can be managed by a location server, for example, LMF. The location server can initiate a PRS configuration (for example, using an NRPPa PRS CONFIGURATION REQUEST message) to NG-RAN nodes, including service and neighbor gNBs, to configure PRS features and receive a response message, for example, the NRPPa PRS CONFIGURATION RESPONSE message from the applicable gNB. In such scenarios, the PRS configuration may be semi-static in nature and may not change frequently unless requested via an on-demand NRPPa PRS configuration procedure. Furthermore, the location server may request the PRS configuration based on knowledge of the received positioning QoS and the subsequently selected positioning method.

[0045] However, due to the distributed nature of Petition 870250089739, dated 02 / 10 / 2025, pages 124 / 209 16 / 92 Positioning and operation of SL under different coverage scenarios and based on legacy SL resource allocation procedures, several problems may arise. For example, some SL resource allocation procedures (e.g., related to centralized Mode 1 / Scheme 1 resource allocation), gNB and UE may request resources for SL-PRS transmission. However, in such scenarios, it is still unclear how gNB will receive the positioning QoS and allocate resources for SL positioning based on factors such as location server involvement or absence. Furthermore, the mechanism for delivering SL positioning assistance data has not yet been addressed.

[0046] Thus, this disclosure presents systems, devices, and methods for enhanced SL mechanisms and procedures, enabling the delivery of SL positioning assistance data in different scenarios, with and without the involvement of the location server, considering different types of coverage scenarios. The implementations discussed here, for example, address scenarios without location server involvement and operation solely by the UE. In such scenarios, a gNB server may need to receive information about the positioning QoS and thus allocate SL-PRS resources based on the number of UEs involved in a specific SL positioning session, as well as the configured positioning technique.Furthermore, the disclosed implementations are applicable in location server engagement scenarios, and based on the request and status information received by the location server, a location server can deliver SL-PRS assistance data (e.g., Mode 1 and Mode 2 SL-PRS resources) to the UE in a semi-static manner. Additionally, if Mode 1 resources are dynamic, the location server can provide SL-PRS assistance data to UEs in an unsolicited manner, including information such as validity time. Petition 870250089739, dated 02 / 10 / 2025, pages 125 / 209 17 / 92 additional implementations, if a UE requests PRS assistance data from the SL location server, the UE can add an indication about a list of discovered UEs and their status, for example, whether the discovered UEs are in or out of coverage.

[0047] The techniques described, for example, allow the initiation of SL positioning information sharing with an NGRAN node, including a request for SL-PRS and SL positioning resource configurations based on the desired carrier frequencies for SL positioning transmission and reception, positioning QoS, and transport QoS profiles for SL-PRS and / or SL positioning data messages. Furthermore, the techniques described allow the provision of semistatic SL positioning assistance data collected from multiple NG-RAN nodes by a location server, for example, LMF. Additionally, the techniques described provide indications of discovered UEs for an SL positioning session and an associated coverage status of the discovered UEs.

[0048] Thus, the techniques described are adaptable to a variety of different SL positioning scenarios and can increase the accuracy with which the UE location can be determined. Aspects of the present disclosure are described in the context of a wireless communications system.

[0049] Figure 1 illustrates an example of a wireless communications system (100), according to aspects of the present disclosure. The wireless communications system (100) may include one or more NEs (102), one or more UEs (104) and a central 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 Petition 870250089739, dated 02 / 10 / 2025, pp. 126 / 209 18 / 92 In some other implementations, the wireless communications system (100) may be an NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultra-wideband (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 the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (WiFi), IEEE 802.16 (WiMAX), and IEEE 802.20 standards. The wireless communications system (100) may support radio access technologies beyond 5G, for example, 6G. In addition, 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.

[0050] One or more NEs (102) may be dispersed over a geographical region to form the wireless communications system (100). One or more of the NEs (102) described herein may be, include, or 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. A NE (102) and a UE (104) may communicate via a communication link, which may be a wireless or wired connection. For example, a NE (102) and a UE (104) may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0051] 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 service-related signals (e.g., voice, video, packet data, messaging, broadcasting, etc.) in accordance with one or more radio access technologies. In some Petition 870250089739, dated 02 / 10 / 2025, pp. 127 / 209 19 / 92 implementations, an NE (102) can be mobile, 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).

[0052] One or more UEs (104) may be dispersed across a geographical region of the wireless communications system (100). A UE (104) may include or 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 (IoT) device, an Internet of Everything (IoE) device, or a machine-type communication (MTC) device, among other examples.

[0053] A UE (104) can support wireless communication directly with other UEs (104) via a communication link. For example, a UE (104) can support wireless communication directly with another UE (104) via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or V2X cellular deployments, the communication link may be called a sidelink. For example, a UE (104) can support wireless communication directly with another UE (104) via a PC5 interface.

[0054] An NE (102) can support communications with the CN (106), or with another NE (102), or both. For example, an NE (102) can interact with another NE (102) or with the CN (106) through one or more backhaul links (e.g., S1, N2, N6, or another network interface). In some Petition 870250089739, dated 02 / 10 / 2025, pages 128 / 209 In 20 / 92 implementations, the NEs (102) can communicate directly with each other. In other implementations, the NEs (102) can communicate indirectly (for example, through the CN (106)). In some implementations, one or more NEs (102) may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC can communicate with one or more UEs (104) through one or more other access network transmission entities, which may be called radio heads, smart radio heads, or transmit and receive points (TRPs).

[0055] The CN (106) can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN (106) can 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), access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a service gateway (S-GW), a packet data network gateway (PDN) (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-accessible stratum (NAS) functions, such as mobility, authentication, and carrier management (e.g., data carriers, signal carriers, etc.) for one or more UEs (104) served by one or more NEs (102) associated with the CN (106).

[0056] The CN (106) can communicate with a packet data network via one or more backhaul links (e.g., via an S1, N2, N6, or other network interface). The packet data network may include an application server. In some implementations, one or more UEs (104) can communicate with the application server. A UE (104) can Petition 870250089739, dated 02 / 10 / 2025, pages 129 / 209 21 / 92 establish a session (e.g., a Protocol Data Unit (PDU) session or similar) with the CN (106) via a NE (102). The CN (106) can route traffic (e.g., control information, data, and similar) between the UE (104) and the application server using the established session (e.g., the established PDU session). The PDU session can 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)).

[0057] In the wireless communication system (100), NEs (102) and UEs (104) can utilize wireless communication system (100) resources (e.g., timing resources (e.g., symbols, slots, subframes, frames, or similar) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, NEs (102) and UEs (104) can support different resource structures. For example, NEs (102) and UEs (104) can support different frame structures. In some implementations, such as in 4G, NEs (102) and UEs (104) can support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, NEs (102) and UEs (104) can support various frame structures (i.e., multiple frame structures).NEs (102) and UEs (104) can support various frame structures based on one or more numerologies.

[0058] 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., μ = 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., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may use a Petition 870250089739, dated 02 / 10 / 2025, pp. 130 / 209 22 / 92 slot per subframe. A second numerology (e.g., μ=1) can be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) can 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., μ=3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) can be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0059] A time interval of a resource (for example, a communication resource) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0060] 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 one or more numerologies supported in the wireless communication system (100). For example, the first, second, third, fourth, and fifth numerologies (i.e., μ = 0, μ = 1, μ = 2, μ = 3, μ = 4) associated with the respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may use a single slot per subframe, two slots per subframe, Petition 870250089739, dated 02 / 10 / 2025, pp. 131 / 209 23 / 92 four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot can include a number (e.g., quantity) of symbols (e.g., Orthogonal Frequency Division Multiplexing (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 the reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and slots.

[0061] In wireless communications systems (100), an electromagnetic (EM) spectrum can be divided, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, wireless communications systems (100) can support one or multiple operating frequency bands, such as frequency band 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, NEs (102) and UEs (104) can perform wireless communications in one or more of the operating frequency bands. In some implementations, FR1 can be used by NEs (102) and UEs (104), among other equipment or devices for cellular communications traffic (e.g., control information, data).In some implementations, FR2 can be used by NEs (102) and UEs (104), among other equipment or devices for short-range, high-data-rate capabilities. Petition 870250089739, dated 02 / 10 / 2025, p. 132 / 209 24 / 92

[0062] 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., μ=0), which includes a subcarrier spacing of 15 kHz; a second numerology (e.g., μ=1), which includes a subcarrier spacing of 30 kHz; and a third numerology (e.g., μ=2), which includes a subcarrier spacing of 60 kHz. FR2 may be associated with one or multiple numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology (e.g., μ=2), which includes a subcarrier spacing of 60 kHz; and a fourth numerology (e.g., μ=3), which includes a subcarrier spacing of 120 kHz.

[0063] According to the implementations, one or more of the NEs (102) and UEs (104) are operable to implement various aspects of the techniques described with reference to this disclosure. For example, a UE (104) transmits a configuration message to an NE (102), including an indication to perform one or more SL-PRS or SL positioning data message transmissions, and the configuration message includes one or more SL positioning parameters. The NE (102) may transmit to the UE (104) a resource configuration message, including a set of time-frequency resources to perform one or more SL-PRS or SL positioning data message transmissions. The UE (104) may use the time-frequency resources to perform SL positioning, either for the UE (104) itself and / or for a different UE.

[0064] Regarding positioning requirements, NR positioning based on Uu NR signals and autonomous architecture (SA) (e.g., beam-based transmissions) was first specified in Version 16. Targeted use cases also included commercial and regulatory (emergency services) scenarios, as in Version 15. The Petition 870250089739, dated 02 / 10 / 2025, pp. 133 / 209 25 / 92 performance requirements are as follows: Table 1 Interior / Exterior Positioning Error: Horizontal positioning < 3m for 80% of UEs; < 10m for 80% of UEs; Vertical positioning < 3m for 80% of UEs; < 3m for 80% of UEs

[0065] Currently, the 3GPP placement in version 17 has defined the placement performance requirements for commercial and IIoT use cases as follows: Table 2 Commercial IIoT Positioning Error: Horizontal positioning (< 1 m) for 90% of UEs; Vertical positioning (< 3 m) for 90% of UEs; Physical layer latency for UE position estimation (< 10 ms); End-to-end latency for UE position estimation (< 100 ms); (< 100 ms, on the order of 10 ms is desired)

[0066] For Sidelink placement in version 18, multiple requirements were defined capturing a variety of use cases, as listed in the following table: Table 3 SL V2X Positioning KPIs Public Safety IIoT Commercial Horizontal Positioning Accuracy Set A (similar to “Set 2” defined in [2]): 1.5 m for 90% of UEs (absolute or relative) Set B (similar to “Set 3” defined in [2]): 0.5 m for 90% of UEs (absolute or relative) 1 m for 90% of UEs (absolute or relative) Set A: 1 m for 90% of UEs (absolute or relative) Set B: 0.2 m for 90% of UEs (absolute or relative) 1 m for 90% of UEs (absolute or relative) Petition 870250089739, dated 02 / 10 / 2025, pp. 134 / 209 26 / 92 SL V2X Positioning KPIs Public Safety IIoT Commercial UEs (absolute or relative) Vertical Positioning Accuracy Set A: 3 m for 90% of UEs (absolute or relative) 2 m (absolute or relative between 2 UEs) for 90% of UEs Set A: 1 m for 90% of UEs (absolute or relative) 2 m for 90% of UEs (absolute or relative) Set B: 2 m for 90% of UEs (absolute or relative) 0.3 m (relative positioning change for 1 UE) for 90% of UEs Set B: 0.2 m for 90% of UEs (absolute or relative) Relative Speed ​​- Up to 30 km / h Up to 30 km / h Up to 30 km / h Angle Accuracy Set A: Y = ± 15° for 90% of UEs Set B: Y = ± 8° for 90% of EUs NOTE 1: For evaluated SL positioning methods, performance results are described in terms of whether each of the two requirements is met and the percentage of UEs that satisfy the target positioning accuracy for a requirement that may not be met at 90%. NOTE 2: Target positioning requirements may not necessarily be met for all scenarios and deployments. NOTE 3: Not all positioning techniques can meet all positioning requirements in all scenarios.

[0067] The supported UE positioning techniques are listed in Table 4 below: Table 4 EU-Based Method EU-Assisted, LMF-Based Node NG-RAN Assisted SUPL A-GNSS Yes Yes No Yes (EU-based and EU-assisted) OTDOAN Notes 1, 2 No Yes No Yes (EU-assisted) E-CID Note 4 No Yes Yes Yes for E-UTRA (EU-assisted) Sensor Yes Yes No No WLAN Yes Yes No Yes Bluetooth No Yes No No TBS Note 5 Yes Yes No Yes (MBS) Petition 870250089739, dated 02 / 10 / 2025, pages 135 / 209 27 / 92 EU-Based Method EU-Assisted, LMF-Based Node NG-RAN Assisted SUPL DL-TDOA Yes Yes No No DL-AoD Yes Yes No No Multi-RTT No Yes Yes No NR E-CID No Yes FFS No UL-TDOA No No Yes No UL-AoA No No Yes No NOTE 1: This includes TBS positioning based on PRS signals. NOTE 2: In this version of the specification, only the Observed Time of Arrival Difference (OTDOA) based on LTE signals is supported. NOTE 4: This includes Cell-ID for the NR method. NOTE 5: This version of the specification is for TBS positioning based on Metropolitan Signaling System (MBS) signals.

[0068] Separate positioning techniques, as indicated in the table above, can currently be configured and executed based on the requirements of the LMF and UE capabilities. Uu PRS transmission (uplink and downlink) allows the UE to perform UE positioning-related measurements to enable the calculation of the absolute location estimate of a UE, and are configured per transmission reception point (TRP), where a TRP can include a set of one or more beams.

[0069] Figure 2 illustrates an example of the system (200) for NR beam-based positioning, according to aspects of the present disclosure. The system (200) illustrates a UE (104) and network entities (102) (e.g., gNBs). The PRS can be transmitted by different base stations (server and neighbor) using narrow beams over FR1 and FR2, as illustrated in the example system (200), which is relatively different when compared to LTE, where the PRS was transmitted throughout the cell. The PRS can be locally associated with a PRS resource identifier (ID) and a resource set ID for a base station (e.g., a TRP). Similarly, UE positioning measurements, such as reference signal time difference (RSTD) and received PRS reference signal power (RSRP), are made between beams (e.g., between a different pair of Petition 870250089739, dated 02 / 10 / 2025, pages 136 / 209 28 / 92 downlink PRS (DL) resources or sets of DL PRS resources), as opposed to separate cells, as was the case in LTE. Additionally, there are further uplink positioning methods for the network to explore in order to calculate the location of the target UE.

[0070] The tables below show reference signal (RS) for mapping measurements for each of the RAT-dependent positioning techniques supported in UE and gNB, respectively. RAT-dependent positioning techniques can utilize 3GPP RAT and core network entities to perform UE position estimation, which are differentiated from RAT-independent positioning techniques, which rely on Global Navigation Satellite System (GNSS), inertial measurement unit (IMU) sensor, wireless local area network (WLAN), and Bluetooth technologies to perform target device (UE) positioning.

[0071] Figure 3 illustrates example scenarios (300) for absolute and relative positioning scenarios. The scenarios (300), for example, are defined in the system architecture study (stage 1) reported in technical report (TR) 22,832, using three different coordinate systems, including Absolute Positioning (e.g., fixed coordinate systems), Relative Positioning (e.g., variable and moving coordinate systems) and Relative Positioning, e.g., variable coordinate systems. Table 5: EU measures to enable positioning techniques RAT DEPENDENTS DL / UL Reference Signs EU Measurements To facilitate support for positioning techniques Version 16 PRS of DL DL RSTD DL-TDOA Version 16 PRS of DL RSRP of DL PRS DL-TDOA, DL-AoD, Multi-RTT Version 16 PRS of DL / Version 16 SRS for positioning Time difference EU Rx-Tx Multi-RTT Version 15 SSB / CSI-RS for RRM SS-RSRP (RSRP for RRM), SS-RSRQ (for RRM), NR E-CID Petition 870250089739, dated 02 / 10 / 2025, pp. 137 / 209 29 / 92 DL / UL Reference Marks EU Measurements To facilitate support for CSI-RSRP (for RRM), CSI-RSRQ (for RRM), SS-RSRPB (for RRM) positioning techniques Table 6: GNB measurements to enable positioning techniques RAT DEPENDENTS DL / UL Reference Signals gNB Measurements To facilitate support for positioning techniques Version 16 SRS for UL RTOA positioning UL-TDOA Version 16 SRS for UL positioning SRS-RECEIVED POWER REFERENCE SIGNAL (RSRP) UL-TDOA, UL-AoA, Multi-RTT Version 16 SRS for positioning, Version 16 PRS of DL gNB Rx-Tx time difference Multi-RTT Version 16 SRS for AoA and ZoA positioning UL-AoA, Multi-RTT

[0072] Several RAT-dependent positioning techniques are supported in versions 16 and 17, such as DL-TDoA, DL-AoD, Multi-RTT, Enhanced Cell-ID (E-CID) / NR E-CID, Uplink (UL)-TDoA, and UL-AoA. The downlink arrival time difference (DL-TDOA) positioning method uses the DL RSTD (and optionally the DL PRS RSRP) of downlink signals received from multiple TPs in the UE. The UE measures the DL RSTD (and optionally 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 relative to neighboring TPs.

[0073] The DL AoD positioning method utilizes the DL PRS RSRP measured from downlink signals received from multiple TPs in 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 relative to neighboring TPs. The Multi-RTT positioning method Petition 870250089739, dated 02 / 10 / 2025, pages 138 / 209 30 / 92 utilizes UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs, measured by the UE, as well as gNB Rx-Tx measurements and UL probe reference signal (SRS)-RSRP on multiple TRPs of uplink signals transmitted from the UE.

[0074] Figure 4 illustrates an example (400) of a multi-cell RTT procedure related to carrier phase positioning configuration, according to aspects of the present disclosure. The multi-RTT positioning technique utilizes UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs, as measured by the UE, and gNB Rx-Tx measurements and uplink SRS RSRP (UL SRSRSRP) measured on multiple TRPs of uplink signals transmitted from the UE. The UE measures the UE Rx-Tx measurements (and optionally the DL PRS RSRP of the received signals) using assistance data received from the positioning server (also referred to herein as the location server), and the TRPs measure the gNB Rx-Tx measurements (and optionally the UL SRS-RSRP of the received signals) using assistance data received from the positioning server.The measurements are used to determine the RTT on the positioning server, which is used to estimate the UE location. In version 16, multi-RTT is only supported for UE-assisted and NG-RAN positioning techniques, as noted in Table 4.

[0075] Figure 5 illustrates an example of a (500) system for relative range estimation using a gNB RTT positioning structure related to the carrier phase positioning configuration.

[0076] For the NR-enhanced cell ID (E-CID) positioning technique, the position of a UE is estimated based on knowledge of its ng-eNB, gNB, and service cell, and is based on LTE signals. Information about the ng-eNB, gNB, and service cell can be Petition 870250089739, dated 02 / 10 / 2025, pages 139 / 209 31 / 92 obtained by pagination, logging, or other methods. NR ECID positioning refers to techniques that utilize additional UE measurements and / or NR radio capabilities and other measurements to enhance UE location estimation using NR signals. While ECID positioning may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE cannot perform additional measurements for the sole purpose of positioning (e.g., positioning procedures do not provide a measurement configuration or measurement control message, and the UE reports available measurements rather than being required to perform additional measurement actions).

[0077] The uplink time-of-arrival difference (UL-TDOA) positioning technique uses the relative time of arrival to the UL (RTOA) (and optionally the UL's SRS-RSRP) at multiple receiving points (RPs) of uplink signals transmitted by the UE. The RPs measure the UL-RTOA (and optionally the UL's 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 UE's location.

[0078] The uplink angle of arrival (UL-AoA) positioning technique utilizes the azimuth and zenith of arrival measured at multiple RPs of uplink signals transmitted from the UE. The RPs measure the azimuth-AoA (AAoA) and zenith-AoA (Z-AoA) of the received signals using assistance data received from the positioning server (also referred to here as the location server), and the resulting measurements are used along with other configuration information to estimate the UE's location.

[0079] Several RAT-independent positioning techniques can also be used, such as network-assisted GNSS techniques, barometric pressure sensor positioning, WLAN positioning, Bluetooth positioning, ground beacon system positioning. Petition 870250089739, dated 02 / 10 / 2025, pages 140 / 209 32 / 92 (TBS) and motion sensor positioning. Network-assisted GNSS techniques make use of UEs equipped with radio receivers capable of receiving GNSS signals. In the 3GPP specifications, the term GNSS encompasses global and regional / augmented satellite navigation systems. Examples of global satellite navigation systems include the Global Positioning System (GPS), the Modernized GPS, Galileo, the Global Navigation Satellite System (GLONASS), and the BeiDou Navigation Satellite System (BDS). Regional satellite navigation systems include the Quasi Zenith Satellite System (QZSS), while the many augmentation systems are classified under the generic term Space-Based Augmentation Systems (SBAS) and provide regional augmentation services. Network-assisted GNSS techniques may use different GNSSs (e.g., GPS, Galileo, etc.) separately or in combination to determine the location of a UE.

[0080] Positioning techniques using barometric pressure sensors utilize barometric sensors to determine the vertical component of the UE's position. The UE measures barometric pressure, optionally with the aid of assist data, to calculate the vertical component of its location or send measurements to the positioning server for position calculation. This technique should be combined with other positioning methods to determine the UE's three-dimensional position.

[0081] WLAN positioning techniques utilize WLAN measurements (access point (AP) identifiers and, optionally, other measurements) and databases to determine the UE's location. The UE measures signals received from WLAN access points, optionally aided by assist data, to send the measurements to the positioning server for position calculation. Using the measurement results and a reference database, the UE's location is calculated. Additionally or alternatively, the UE uses WLAN measurements and, optionally, data from Petition 870250089739, dated 02 / 10 / 2025, pages 141 / 209 33 / 92 AP WLAN assistance provided by the positioning server to determine its location.

[0082] Bluetooth positioning techniques use Bluetooth measurements (beacon identifiers and, optionally, other measurements) to determine the UE's location. The UE measures signals received from Bluetooth beacons. Using the measurement results and a reference database, the UE's location is calculated. Bluetooth methods can be combined with other positioning methods (e.g., WLAN) to improve the accuracy of the UE's positioning.

[0083] TBS positioning techniques utilize a TBS, which includes a network of ground transmitters, transmitting signals solely for positioning purposes. Examples of TBS positioning signal types are MBS (Metropolitan Beacon System) signals and PRSs. The UE measures the received TBS signals, optionally aided by assist data, to calculate its location or send measurements to the positioning server for position calculation.

[0084] Motion sensor positioning techniques utilize different sensors, such as accelerometers, gyroscopes, magnetometers, and others, to calculate the displacement of the UE. The UE estimates a relative displacement based on a reference position and / or reference time. The UE sends a report containing the determined relative displacement, which can be used to determine the absolute position. This method can be used with other positioning methods for hybrid positioning.

[0085] Different downlink measurements used for RAT-dependent positioning techniques include DL PRS-RSRP, DL RSTD, and UE Rx-Tx Time Difference. The following measurement configurations can be used: 4 pairs of DL RSTD measurements can be performed per cell pair, and each measurement is performed between a different pair of DL PRS Features / Feature Sets with a single time of Petition 870250089739, dated 02 / 10 / 2025, pp. 142 / 209 34 / 92 reference; 8 DL PRS RSRP measurements can be performed on different DL PRS features of the same cell. Table 7: Downlink measurements for downlink-based positioning techniques Received Power of DL Reference Signal PRS (DL PRS-RSRP) Definition: DL PRS-RSRP is the linear average over the power contributions (in [W]) of the feature elements carrying DL PRS reference signals configured for RSRP measurements within the considered measurement frequency bandwidth. For frequency band 1, the reference point for DL ​​PRS-RSRP should be the UE antenna connector. For frequency band 2, DL PRS-RSRP should be measured based on the combined signal of the antenna elements corresponding to a given receiver branch. For frequency bands 1 and 2, if the UE is using receiver diversity, the reported DL PRS-RSRP value should not be less than the corresponding DL PRS-RSRP of any of the individual receiver branches.Applicable to intra-frequency RRC_CONNECTED, inter-frequency RRC_CONNECTED Reference Signal Time Difference DL (DL RSTD) Definition The reference signal time difference DL (DL RSTD) is the relative DL time difference between positioning node j and reference positioning node i, defined as TSubframeRxj — TSubframeRxi, Where: TSubframeRxj is the time when the UE receives the start of a subframe from positioning node j. TSubframeRxi is the time when the UE receives the corresponding start of a subframe from positioning node i that is closest in time to the subframe received from positioning node j. Multiple DL PRS features can be used to determine the start of a subframe from a positioning node. For frequency band 1, the reference point for the DL RSTD will be the UE antenna connector. For frequency band 2, the reference point for the DL RSTD will be the UE antenna.Applicable to intra-frequency RRC_CONNECTED and inter-frequency RRC_CONNECTED. UE Rx - Tx Time Difference Definition: The UE Rx - Tx time difference is defined as Tue-rx - Tue-tx. Where: Tue-rx is the time received by the UE of the downlink subframe #i from a positioning node, defined by the first path detected in time. Tue-tx is the UE transmission time of the uplink subframe #j that is closest in time to the subframe #i received from the positioning node. Multiple DL PRS features can be used to determine the start of a subframe of the first arrival path from the positioning node. For frequency band 1, the reference point for the Tue-rx measurement should be the UE Rx antenna connector, and the reference point for the Tue-tx measurement should be the UE Tx antenna connector. For frequency band 2, the reference point for the Tue-rx measurement should be the UE's Rx antenna, and the reference point for the Tue-tx measurement should be the UE's Tx antenna. Petition 870250089739, dated 02 / 10 / 2025, pp. 143 / 209 35 / 92 Received Power of DL Reference Signal PRS (DL PRS-RSRP) Applicable to RRC_CONNECTED intra-frequency RRC_CONNECTED inter-frequency DLP PRS RSRP (Received Path Power of Reference Signal) Definition The received path power of the DL reference signal PRS (DL PRSRSRPP) is defined as the linear average power of the channel response at the i-th path delay of the feature elements carrying the DL PRS signal configured for measurement, where DL PRSRSRPP for the 1st path delay is the power contribution corresponding to the first path detected in time. For frequency band 1, the reference point for DL ​​PRS-RSRPP will be the UE antenna connector. For frequency band 2, DL PRS-RSRPP will be measured based on the combined signal of the antenna elements corresponding to a given receiver branch. Applicable to RRC_CONNECTED RRC_INACTIVE

[0086] Figure 6 illustrates an example procedure (600) to enable a UE to obtain sidelink positioning and / or range location results. Procedure (600), for example, may utilize one or more UEs with the aid of an LMF on a Public Mobile Terrestrial Network (PLMN) in service to UE1. In procedure (600), the SL positioning / range location results may include absolute locations, relative locations, or distances and directions, as based on the service request. Furthermore, if the destination UE decides to initiate a Mobile Device Originated Location Request (MO-LR) procedure, it may include one or multiple SL reference UEs and / or UEs located in the service request. For example, see technical specification (TS) 23.586.

[0087] In procedure (600), a UE1 may be in coverage and registered in a service PLMN. UEs 2 may or may not be in coverage and, if so, may or may not be registered in the same service PLMN as UE1: 1. The procedures and signage specified in clause TS 23.586 version 6.2 can be used to provision SL / reach positioning service authorization and policy / parameter provisioning. Petition 870250089739, dated 02 / 10 / 2025, pp. 144 / 209 36 / 92 for EUs 1 an, when in coverage; NOTE 1: If the operation indication is received only In the EU, the range / sidelink positioning control procedures, as defined in clause 6.8 of TS 23.586, may be performed; 2. Based on a service request trigger (e.g., received from the application layer), which includes UE1 / ... / UE n, UE discovery is performed for reach / SL placement as specified in clause 6.4 of TS 23.586: If EU1 is the destination EU, EU1 discovers EU2 and - If UE1 is the located UE, the destination UE (i.e., one of the UEs 2 an) discovers UE1 (and other UEs located in the set of UEs 2 an); 3. Secure groupcast and / or unicast links are established between UE1s, as defined in clause 5.3 of TS 23.586, to allow UE1 to exchange Reach and Sidelink Positioning Protocol (RSPP) messages over the PC5-U reference point with each of the UE2s, possibly allowing the UE2s to exchange RSPP over PC5-U with each other; 4. UE1 and UEs 2 and 3 can communicate via PC5 for Reach / SL positioning authorization and receipt of QoS parameters, if necessary. Each UE verifies whether Reach / SL positioning is permitted, including whether the results of Reach / SL positioning can be transferred to an LCS or AF Client, if used, in accordance with any service authorization and policy / parameter provisioning received in step 1. QoS requirements for Reach / SL positioning can also be provided based on the QoS requirements of the service request; 5. UE1 can obtain the positioning resources of Petition 870250089739, dated 02 / 10 / 2025, pages 145 / 209 37 / 92 Sidelink the UEs 2 an using the groupcast and / or unicast links established in step 3; Steps 4 and 5 can be performed to transfer information from UEs that are not served by the LMF; 6. Based on the Sidelink placement capabilities of UE1 / ... / UEn, the destination UE determines that SL-MO-LR should be run. If UE1 is the Localized UE (i.e., when the destination UE is one of the UE2 / ... / UEn and does not have a NAS connection), the destination UE initiates the SL-MO-LR service request to UE1; 7. If UE1 is in the Connection Management (CM)-IDLE state, UE1 initiates a UE-triggered service request to establish a signaling connection with the UE1 AMF server; 8. UE1 sends an SL-MO-LR request for supplementary services to the AMF server in a UL NAS TRANSPORT message. The SL-MO-LR request indicates the other UEs in the second instance (using the Application Layer ID and / or Generic Public Signature Identifier (GPSI)), indicates any required assistance data, indicates whether location calculation assistance is needed, and whether location results should be transferred to an LCS or AF client. The message must include the identity of the LCS or AF client and may include the Gateway Mobile Location Center (GMLC) address through which the LCS or AF client (via Network Exposure Function (NEF)) should be accessed. Additionally, a Service Type indicating which LCS Client MO-LR service is requested by the UE may be included.For assistance with LMF location calculation, the preferred type of Sidelink placement / reach location results (e.g., absolute locations, relative locations, or distances and directions between UE pairs) and the required QoS are included. If UE1 is the located UE and one of the UE2 / ... / UEn is the destination UE that does not have a NAS connection, the request... Petition 870250089739, dated 02 / 10 / 2025, pages 146 / 209 38 / 92 supplementary services SL-MO-LR includes an indication that one of the EU2 / ... / EUn is the destination EU instead of EU1; 9. The AMF server selects an LMF that meets UE1 (for example, an LMF that supports Sidelink placement / reach) and sends an Nlmf_Location_DetermineLocation service operation to the LMF with the SL-MO-LR request information. The service operation includes an LCS correlation identifier; 10. The LMF sends a request to UE1 for the resources of UEs 1 and; NOTE 3: UE2 / ... / UE It is not assumed that n is served by the same LMF that serves UE1; 11. UE1 returns its capabilities to the LMF. UE1 may additionally return the capabilities of the UEs obtained in step 5, if requested by the LMF in step 10; 12. UE1 can send a request for specific assistance data to LMF; 13. The LMF sends the requested assistance data to UE1, and UE1 forwards the assistance data received from the LMF to UE2 / ... / UE n. The assistance data may assist UEs 1 and 2 in obtaining sidelink location measurements in step 15 and / or may assist UE1 in calculating sidelink positioning / location results in step 16; NOTE 4: Steps 10 and 11 may be omitted if UE1 includes a message containing the capabilities of UE1 and in the SL-MO-LR request in step 8. Step 12 may be omitted if UE1 includes a message containing the request for specific assistance data in the SL-MO-LR request in step 8; 14. If the SL-MO-LR request in step 8 indicates the need for assistance in location calculation and / or indicates a transfer. Petition 870250089739, dated 02 / 10 / 2025, pages 147 / 209 Based on the sidelink positioning / reach results for an LCS or AF Client, the LMF sends a location information request to UE1 and may also send a location information request to UE2 / ... / UEn if it is serviced by the LMF. If the LMF decides to apply UE-based SL Positioning, the LMF includes the UE-based SL Positioning indication in the request. The LMF may also provide the list of located candidate UE(s) if absolute location is requested in step 8. If scheduled location time is received in step 14, the LMF may include a scheduled location time; 15. UE1 initiates a Sidelink positioning / reaching procedure between UEs 1 and 2, in which UEs 1 and 2 obtain Sidelink location measurements and UEs 2 and 2 transfer their Sidelink location measurements to UE1 and / or to the LMF (depending on the assistance requested). If the scheduled location time is received in step 14, the Sidelink positioning / reaching is performed at the scheduled location time; 16. If the absolute location information of the destination UE is required in step 8 and the absolute location of the located UE(s) is / are not available, the destination UE sends a request to the located UE(s) to trigger procedure 5GC-MO-LR, allowing the located UE(s) to obtain their own absolute location. The QoS requirement received in step 8 is included in the request, which is used to derive the QoS for the positioning of the located UE(s); 17. If the LMF determines to use the UE-based calculation, at least one of the UE1 / ... / UEn calculates the Sidelink positioning / reach location results based on the Sidelink location measurements obtained in step 15 and possibly using assistance data received in step 13. The positioning / reach location results Petition 870250089739, dated 02 / 10 / 2025, pages 148 / 209 Sidelink 40 / 92 may include absolute locations, relative locations or ranges and directions related to UEs 1 an; 18. If UE1 received a location information request in step 14, UE1 sends a response to the LMF and includes the Sidelink location measurements obtained in step 15, the Sidelink positioning / range location results obtained in step 17, if step 17 was executed, or the absolute location of the located UE obtained in step 16; 19. If the absolute location information of the destination UE(s) is required in step 8, and if the absolute location of the located UE(s) is / are not received in step 18, the LMF can retrieve the location of the located UE(s) locally or trigger Procedure 5GC-Mobile Terminated Location Request (MT-LR) to the GMLC to obtain the absolute location of the located UE(s) using the Application Layer ID or GPSI of the located UE(s). The LMF includes the QoS requirement received in step 8 of the request, which is used to derive the QoS for the positioning of the located UE(s). If scheduled location time is used, the LMF includes the scheduled location time in the request to the GMLC; 20. The LMF calculates the Sidelink positioning / range location results for UEs 1 an from the Sidelink location measurements received in step 18 and the absolute location of the UE(s) located in step 19. The Sidelink positioning / range location results may include absolute locations, relative locations, or ranges and directions related to UEs 1 an, depending on the location request received in step 8; 21. The LMF returns an Nlmf_Location_DetermineLocation service operation response to the AMF and includes the Sidelink positioning / reach location results received in step 18 or calculated in step 20; Petition 870250089739, dated 02 / 10 / 2025, pages 149 / 209 41 / 92 22. If the Sidelink location / positioning range results were received in step 21, the AMF executes steps 7 to 12 of clause 6.2 to send the Sidelink location / positioning range results to the GMLC and to an AF or LCS client, if requested in step 8. The Sidelink location / positioning range results include the identities of the respective UEs 1 and 2 received in step 8; NOTE 5: Sending location results and global identities for UEs 1 an to an AF or LCS client may require privacy verification of the UEs 1 an and / or the HPLMNs of the UEs 1 an; 23. The LMF returns an SL-MO-LR supplemental services response to UE1 in a DL NAS TRANSPORT message and includes any Sidelink range positioning / location results calculated in step 20, if step 20 was executed. If UE1 is a Localized UE and the destination UE is one of the UEs 2 and does not have a NAS connection, UE1 may transfer the Sidelink range positioning / location results to the destination UE.

[0088] Figure 7 illustrates a procedure (700) to allow an LCS or AF Customer to obtain range and / or sidelink positioning location results for a group of n UEs. For example (n > 2), e.g., UE1, UE2,..., UE n. In procedure (700), GMLC determines that one UE among the n UEs is designated as UE1 (e.g., Target UE in TS 23.586) and one or more other UEs are designated as UE2, UE3,..., UE n (n > 2) (e.g., Reference / Located UEs in TS 23.586). The range / sidelink positioning location results may include absolute locations, relative locations or ranges, and directions related to the UEs, based on the service request. An SL-MT-LR procedure can be used to estimate the relative locations or distances and / or directions between the UEs. Furthermore, an example procedure for periodic and triggered SL-MT-LR is Petition 870250089739, dated 02 / 10 / 2025, pages 150 / 209 42 / 92 defined in clause 6.20.4. In procedure (700), it can be assumed that at least one of the n UEs is covered and registered in a server PLMN; 1. The LCS Client or AF (via NEF) sends an LCS service request to (H)GMLC to obtain Sidelink Reach / Positioning location results for the n UEs, which can be identified by a GPSI or a permanent subscription identifier (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), the SL reference UE(s) in the case of relative locations, distance, or direction. The (H)GMLC or NEF authorizes the LCS Client or AF to use the LCS service. If authorization fails, the remaining steps will be skipped, and the (H)GMLC or NEF will respond to the LCS Client or AF informing them of the service authorization failure; Additionally, an application layer ID must be included for each of the n UEs to enable UE discovery in step 12; 2. The (H)GMLC invokes a service operation. Nudm_SDM_Get is used for the Unified Data Management (UDM) of each of the n UEs to obtain the privacy settings of the UE identified by its GPSI or SUPI. The UDM returns the UE's privacy setting. The (H)GMLC checks the UE's LCS privacy profile; 3. The (H)GMLC invokes a service operation. Nudm_UECM_Get to the UDM of each of the n UEs (for which GPSI or SUPI are available), one at a time, using the GPSI or SUPI of each UE. The (H)GMLC selects the UE (e.g., which is treated as UE1 in the following steps) that initiates range / SL positioning and selects the corresponding AMF server; NOTE: The UDM is aware of the AMF server address in the UE record in an AMF, as defined in clause 4.2.2.2.2 of TS 23.502. Petition 870250089739, dated 02 / 10 / 2025, pages 151 / 209 43 / 92 UDM is aware of a (V)GMLC service address in the UE register in an AMF, as defined in clause 4.2.2.2.2 of TS 23.502; 4. For a non-roaming case, this step is skipped. In the roaming case, the (H)GMLC can receive an address from a (V)GMLC (along with the network address of the current AMF server) from the UDM in step 3. Otherwise, the (H)GMLC can use the Network Repository Function (NRF) service on the (H)PLMN to select an available (V)GMLC on the (V)PLMN, based on the (V)PLMN ID contained in the AMF address received in step 3. The (H)GMLC then sends the location request to the (V)GMLC by invoking the Ngmlc_Location_ProvideLocation service operation towards the (V)GMLC. In cases where the (H)GMLC has not received the (V)GMLC address, or when the (V)GMLC address is the same as the (H)GMLC address, or when both PLMN operators agree, the (H)GMLC sends the location service request message to the AMF server. In this case, step 4 is skipped.The (H)-GMLC also provides the AF LCS client type, if received in step 1, or the LCS client type and other attributes to be sent to the AMF in step 5. 5. In the case of roaming, the (V)GMLC first authorizes the location request to be allowed from this (H)GMLC, PLMN, or this country. Otherwise, an error response is returned. The (H)GMLC or (V)GMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF serving UE1 to request the Sidelink positioning / reach results from the n UEs. The service operation includes the UE1 SUPI, the UEs' application layer IDs, 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 received or determined in step 1; 6. If UE1 is in the CM-IDLE state, the AMF initiates a Petition 870250089739, dated 02 / 10 / 2025, pages 152 / 209 44 / 92 Service Request procedure triggered by the network to establish a signaling connection with UE1. If establishing the signaling connection fails, steps 7 to 17 can be skipped; 7-8. If the privacy check indicator shows that action is required, the same operation as in step 7-8 of clause 6.1.2 will be performed; 9. The AMF server selects an LMF that serves UE1 (for example, an LMF that supports reach / sidelink positioning) and sends an Nlmf_Location_DetermineLocation service operation to the LMF with the information received in step 5, for example, required location results (e.g., relative locations or ranges and directions between UE pairs), SL reference UE(s) in the case of relative locations, application layer IDs of the UEs if received in step 5. The service operation includes an LCS correlation identifier; 10. The LMF sends an SL-MT-LR request to the AMF server as a supplemental services message, using the Namf_Communication_N1N2MessageTransfer service operation, and the session ID parameter is set to the LCS correlation identifier. The SL-MTLR request may include the application layer IDs of the other 2nd-generation UEs, the required location result types (e.g., relative locations or distances and / or directions), and SL Reference UE(s) in the case of relative locations; 11. The AMF server forwards the SL-MT-LR request and a routing identifier equal to the LCS correlation identifier to UE1 using a DL NAS TRANSPORT message; 12. UE1 attempts to discover the other UE2 using its Application Layer IDs, if it has not already been discovered using the procedure defined in clause 6.4 of TS 23.586; Petition 870250089739, dated 02 / 10 / 2025, pages 153 / 209 45 / 92 13. UE1 obtains Sidelink positioning resources from UEs discovered via SLPP, if they have not already been obtained; 14. UE1 returns an SL-MT-LR response of supplementary services to the AMF server in a UL NAS TRANSPORT message and includes the routing identifier received in step 11. The SL-MT-LR response indicates which of the UE2s were discovered and the Sidelink placement capabilities of the discovered UEs; 15. The AMF server forwards the SL-MT-LR response to the LMF indicated by the routing identifier received in step 14 and includes an LCS correlation identifier equal to the routing identifier; 16. The range / sidelink positioning of UE1 and the other discovered UEs occurs as in an SL-MO-LR, with the difference that the data or results of the range / sidelink positioning location measurement can be returned to the LMF, which indicates to UE1, in step 13 or 14 of Error! Reference source not found, whether the range / sidelink positioning location results will be calculated by the LMF (in step 19) or by UE1 (in step 17). For some undiscovered UEs among the other UEs of 2 years, the LMF interacts with the GMLC to initiate the 5GC-MT-LR procedure of UE2 years to obtain their absolute locations and calculate the relative locations or distances and / or directions related to the UEs; 17-20. The LMF returns the Sidelink location / range results to the LCS or AF Client, as per steps 13 to 15 and 24 of clause 6.1.2. The results also include information on any undiscovered UE(s) failures.

[0089] Figure 8 illustrates an example procedure (800) for range and / or SL positioning control, as for UE-only operation. Both UE-only operation and network-based operation can be applied in positioning control procedures. Petition 870250089739, dated 02 / 10 / 2025, pages 154 / 209 46 / 92 range / sidelink.

[0090] For example, the EU-only operation can be applied in the following cases: • Neither the destination UE nor the reference UE of the SL are served by NG-RAN; • Network-based operation is not supported by the network. 5GC; • When Network Based Operation is not supported by the 5GC network, an indication of whether the UE is permitted to use UE-only operation to perform range / SL positioning is included in the Policy / Parameter provisioned for the UE and is provisioned to the UE. The destination UE will take this into account to initiate the UE-only operation procedure; • The SL-MO-LR request is rejected by the network.

[0091] In procedure (800): 1. UE1 (i.e., destination UE) can receive a range / SL positioning service request from: 1a. EU Client SL positioning over PC5 during procedures for SL positioning / reach service exposure via PC5; - For absolute location, the service request includes user information from the SL positioning client's UE and user information from the destination UE, as well as the required positioning QoS; - For relative location or range information, the service request includes UE user information from the SL positioning client, destination UE user information, SL Reference UE user information (UE2 / ... / UE n), and SL range / positioning QoS information; Petition 870250089739, dated 02 / 10 / 2025, pages 155 / 209 47 / 92 1b. RSPP application layer; The service request includes the type of result (i.e., absolute location, relative location, or reach information) and the required QoS; 2. EU1 discovers EU2 / ... / EU n (for example, EUs of Reference to local SL / UEs); 3. If none of the UE1 / ... / UE n are served by the NG-RAN or the service network does not support range positioning / SL, the UE-only operation will be applied; 4. UE1 and UE2 / ... / UE n performs capacity exchange. Step 4 can be executed during steps 5 and 6, with coordination from the UE of the SL Positioning Server; 5. If UE1 does not support the Server functionalities of In SL Positioning, an SL Positioning Server UE (colocated with an SL Reference UE / Localized UE or operated by a separate UE) is discovered (if it has not already been discovered in step 2) and selected. If an SL Positioning Server UE is colocated with an SL Reference UE / Localized UE or operated by a separate UE, UE1 discovers and selects the SL Positioning Server UE and requests that the SL Positioning Server UE participate in Reach / Sidelink positioning; 6. Sidelink positioning assistant data is transferred between UE1 / ... / UE neo UE from the SL Positioning Server; 7. The SL-PRS measurement is performed between UE1 and UE2 / ... / UE ne, optionally also between UE2 / ... / UE n; 8. The SL-PRS measurement data is transferred to the UE of the SL Positioning Server or to UE1, if it supports the functionalities of the SL Positioning Server to perform the calculation of Petition 870250089739, dated 02 / 10 / 2025, pages 156 / 209 48 / 92 results. Based on the type of result received in step 1, absolute location, relative location, or range information is calculated in the EU; 9. The result of the range / SL positioning is transferred to: 9a. EU client SL positioning over PC5 during procedures for exposure of the SL positioning / reach service via PC5, as defined in clause 6.6.1.1; 9b. RSPP application layer.

[0092] Consequently, aspects of this disclosure foresee different positioning scenarios, including scenarios that do not involve a location server and implementations that do involve a location server. For example, in scenarios without location server involvement but with gNB server involvement, an NG-RAN can schedule resources for SL-PRS transmission and SL positioning data transmission. Such implementations may involve interlayer interaction between the UE's SLPP and RRC layers for sharing and exchanging positioning-related information with a gNB server. The UE may be triggered by its own upper layers (e.g., reach, SL positioning layer, etc.) and / or receive an indication from upper layers of another UE to initiate an SL positioning transmission process based on the gNB server's resource scheduling.In implementations, this can be a direct interaction between the UE and the NGRAN node (e.g., gNB server) and not involve a location server (e.g., LMF) for providing SL positioning assistance data.

[0093] In implementations, an UE can transmit information related to the UE's positioning QoS or the positioning QoS mapped to the standardized PC5 5G QoS Identifier (PQI) table. Petition 870250089739, dated 02 / 10 / 2025, pages 157 / 209 49 / 92 as part of the SL positioning assistance data request to the gNB server, where the UE is requesting resources for SLPRS transmission. Positioning QoS can be based on a sidelink SL MO-LR location service request made by the LCS client (e.g., application) and can be based on a single UE request or multiple UE requests, as in terms of the following metrics: • Absolute Location o Absolute horizontal location accuracy o Absolute vertical location accuracy • Relative Location o Relative horizontal location accuracy o Relative vertical location accuracy • Distance Range o Horizontal distance location accuracy o Vertical distance location accuracy • Direction Range o Azimuth Angle of Arrival Direction Accuracy o Zenith Angle of Arrival Direction Accuracy • Other mobility QoS parameters, such as: Absolute horizontal / vertical speed; Relative horizontal / vertical speed.

[0094] In implementations, the QoS for the placement of a UE (e.g., a group of UEs) is mapped to a standardized PQI table, also called the QoS for transporting messages related to SL placement, as highlighted in Table 8 below. It can be observed that: • The PQI value can be given by 'X', which can be an integer value; Petition 870250089739, dated 02 / 10 / 2025, pages 158 / 209 50 / 92 • The resource type is non-guaranteed bit rate (GBR), as shown in Table 8, to accommodate different types of SL-PRS and SLPP message transmission, including capacity exchange, assistance data exchange, location information exchange, and error and interrupt message exchange. In implementations, the resource type can be configured for GBR or critical delay service, since SL placement can be considered a critical sidelink service; • The Default Priority Level can be 'Y', which can be an integer value to reflect the default priority of messages related to SL placement; In another implementation, the default priority can help determine the Layer 1 priority of messages related to SL and / or SL-PRS placement; • The Packet Delay Budget (PDB) can be given by 'Z' ms, which can be an integer value. In another implementation, the delay budget can be split to reflect SLPP placement-related messages provided by PDB 'Z1' and SL-PRS transmissions provided by the placement / location delay budget 'Z2' (PoDB / LDB); The PDB / PoDB / LDB can be used by lower layers to transmit the SLPRS / SLPP placement resource selection window to Mode 2 procedures. This can indicate a latency limit within which the SLPP or SLPRS transport block message must be transmitted; The feature selection window is defined by [ n + T1 ,n + T2], where n is the slot in which resources should be selected, T1 is defined as the processing time to identify candidate SL-PRS / SLPP message resources and select those resources for transmission, while T2 is defined as T2min. <T2 < PDB; Petition 870250089739, dated 02 / 10 / 2025, pages 159 / 209 51 / 92 This PDB / PoDB / LDB can be signaled as part of the QoS profile of the UE's own upper layers, or in other implementations received from another UE / device, via 1st or 2nd stage SCI; • The packet error rate can be given by 'A' to indicate the reliability of messages related to SL placement, provided by the block error rate (BLER), bit error rate (BER), packet error rate (PER), or any related metric; • The maximum standard burst data volume is not specified for SL placement, but in other implementations, a burst data volume may be provided in bytes applicable to messages related to SL placement; • The standard averaging window can be given by 'B' ms, which can be an integer value; • NOTE that multiple sets of {X, Y, Z, A, B} can be defined as part of the standardized PQI.

[0095] In scenarios where the standardized PQI is unavailable or not provided, a standard set of SL positioning PQIs applicable to the values ​​{X, Y, Z, A, B} can be pre-configured in a UE. In another implementation, the supported PQIs {X, Y, Z, A, B} can be passed to the UE for appropriate selection.

[0096] Depending on the implementation, Mode 2 and / or Scheme 2 can support both standalone and semi-persistent dynamic scheduling. In a dynamic scheme, a UE can detect and select resources based on the SL-PRS transmission configuration and / or the SL positioning data message (e.g., transport block (TB)), while a semi-persistent scheme can select a number of consecutive resources based on a number of consecutive re-selection counters applicable to SL positioning data transmissions. Petition 870250089739, dated 02 / 10 / 2025, pp. 160 / 209 52 / 92 PRS and SL. In implementations, a time period is defined between the selected resources for the transmission of consecutive SL-PRS and / or SL positioning data messages (e.g., TBs), given by the RRI (Resource Reservation Interval) with a range of {[1:99], 100, 200, ..., 1000} ms.

[0097] A UE can select resources when it generates a new SL placement TB based on a higher-layer trigger and / or when it receives a higher-layer trigger to transmit SL-PRS according to a defined SL-PRS configuration. A UE can perform detection according to a detection window limited by [n - T0, n - Tproc00], where n is defined as above, T0 is defined in terms of the number of slots (also dependent on Subcarrier Spacing (SCS)), and Tproc00 is the time to complete the detection operation. A resource selection window can initially be defined by the UE as a function of T1 and T2 of the PDB / PoDB / LDB described above. Additionally, T2 can be defined as a function of T2lllin, which can be based on a priority value of the SL placement TB or SL-PRS. This priority can be based on placement QoS, transport QoS, or a combination thereof.

[0098] Subsequently, once the selection window has been defined, the UE can identify candidate resources within the selection window. A resource exclusion algorithm can then be applied to exclude the candidate resource based on defined policies, and subsequently, the UE can select resources from among the remaining candidate resources. In implementations, resources can be selected subject to a percentage of the remaining available resources in the selection window being greater than a configured P% threshold for SL-PRS transmission or SL positioning data message transmission. The configured P% threshold can be based on an SL positioning TB priority value or Petition 870250089739, dated 02 / 10 / 2025, pages 161 / 209 53 / 92 of SL-PRS, where a P% mapping for a specific priority can be determined and provided to a UE sensor.

[0099] In implementations, the positioning QoS and positioning-mapped PQI described above (also referred to as transport QoS) can be signaled to another entity (e.g., gNB and / or location server) as part of a QoS profile applicable to a specific LCS request. This QoS profile can also be signaled together with an SL QoS Flow ID. In implementations where a location server is not involved in scheduling SL-PRS transmissions, the UE can share one or more of the above QoS profiles with a gNB server to assist in the gNB resource allocation procedure. Table 8: Illustrative example of standardized PQI with PQI of SL POSITIONING PQI Value Resource Type Default Priority Level Packet Delay Budget Packet Error Rate Default Maximum Data Burst Volume Average Window Default Example Services 21 GBR 3 20 ms 10-4 N / A 2000 ms Platoon between UEs Highest degree of automation; Platoon between UE and roadside unit (RSU) - Highest degree of automation 22 (NOTE 1) 4 50 ms 10-2 N / A 2000 ms Sensor sharing highest degree of automation 23 3 100 ms 10-4 N / A 2000 ms Information sharing for automated driving between UEs or UE and RSU - highest degree of automation 55 Non-GBR 3 10 ms 10-4 N / A / A Cooperative lane change - highest degree of automation 56 6 20 ms 10-1 N / A / A Information exchange Petition 870250089739, dated 02 / 10 / 2025, pages 162 / 209 54 / 92 PQI Value Resource Type Default Priority Level Packet Delay Budget Packet Error Rate Default Maximum Data Burst Volume Average Window Default Example Services Platoon - Low degree of automation; Platoon sharing information with RSU XYZ ms AN / AB ms SLPP - SL Positioning Messages 57 5 25 ms 10-1 N / AN / A Cooperative lane change - lower degree of automation 58 4 100 ms 10-2 N / AN / A Sensor information sharing - lower degree of automation 59 6 500 ms 10-1 N / AN / A Platoon reporting to an RSU 90 GBR Critical Delay 3 10 ms 10-4 2000 bytes 2000 ms Cooperative collision avoidance; Sensor sharing - Higher degree of automation; Video sharing - higher degree of automation 91 (NOTE 1) 2 3 ms 10-5 2000 bytes 2000 ms Emergency trajectory alignment;Sensor sharing. Higher degree of automation. NOTE 1: GBR and GBR PQIs with critical delay can be used exclusively for PC5 unicast communications.

[00100] According to the implementations and considering the QoS positioning parameters above, a UE can partition an SL-PRS resource request by positioning method. Examples of such positioning methods are described above, such as SL-TDOA (similar to UL) for SL RTOA measurements, SL-TDOA (similar to DL) Petition 870250089739, dated 02 / 10 / 2025, pp. 163 / 209 55 / 92 for SL RSTD measurements, unilateral or bilateral SL-RTT for Rx-Tx time difference measurements of SL UEs, SL-AoA for Azimuth-AoA and / or Zenith-AoA measurements, etc. This can allow a UE to request resources according to a specified positioning method. In cases of SL MO-LR without location server involvement, the decision may rest with the target UE / device and / or anchor UE / device, and the UE / devices may act as a server UE and / or be equipped with server UE capabilities. In implementations, a server UE may be another UE requesting SL-PRS resources for transmission.

[00101] In implementations, a requesting UE / device may request SL-PRS transmission features for a given set of SL positioning features, including but not limited to the following: • SL-PRS Resource Index o SL-PRS Resource Index ID o SL-PRS bandwidth in terms of PRBs, subchannels, subchannel size o SL-PRS comb size in terms of: SL-PRS comb displacements and associated SL-PRS comb sizes (N) Initial symbols of SL-PRS and number of symbols and SL- PRS(M) The SL-PRS start time can be relative to SFN0 or DFN0, and the total SL-PRS duration is given by X ms. SL-PRS Periodicity in terms of: _ ySL-PRSc1pos-1fc 2μ{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} slots, where μ=0,1,2,3 according to an SL-PRS subcarrier spacing=15, 30, Petition 870250089739, dated 02 / 10 / 2025, pp. 164 / 209 56 / 92 and 120 kHz respectively TSL-PRSc1pos-2t{100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 5000, 10000} milliseconds (ms) In another implementation, the configured grant periodicity can be the union of TpSL—PRS and TpSL—PRS to cover multiple periodicity values; The SL-PRS resource ID uniquely identifies a time-frequency resource within a slot of a dedicated SL PRS resource pool that is used for SL PRS transmission, and, in the case of a resource pool shared with SL data transmissions, uniquely identifies a time-frequency resource based on an SL PRS resource ID and an SL PRS frequency domain allocation; The SL-PRS ID, which uniquely identifies an SL-PRS based on the SL-PRS resource ID and / or SL-PRS feature set ID, may be applicable to SL-PRS transmitted over different slots; The ID of the SL placement session; The ID of the SL-PRS resource set; SL's BWP ID; The SL operator ID; SL-PRS repetitions; SL-PRS muting pattern.

[00102] The example SL-PRS transmission features indicated above may be part of a feature index list composed of multiple SL-PRS transmission features. In other implementations, SL-PRS transmission features may include QCL information, such as a QCL source, for example, SLSS or another SLPRS.

[00103] In implementations, a UE that initiates a session Petition 870250089739, dated 02 / 10 / 2025, pages 165 / 209 57 / 92 SL positioning or transmits SL-PRS to one or more peer UEs (e.g., via unicast, groupcast, broadcast, etc.) can initiate an SL positioning request to a gNB server. The SL positioning request can contain parameters related to the delivery of SL positioning assistance data, including the SL-PRS configuration, which may include a dynamic grant, a Type 1 configured grant, where the RRC / SLPP directly provides the configured sidelink grant for NR sidelink positioning and / or communication, and / or a Type 2 configured grant, where the RRC / SLPP sets a periodicity for the configured sidelink grant, while lower-layer signaling (e.g., DCI) can signal and enable or disable the configured sidelink grant, for example, by releasing SL positioning resources.In implementations, SLPP can trigger lower layers, such as the RRC, to perform NR sidelink placement and resource requests with the gNB server, for example, the NG-RAN node.

[00104] Figure 9 illustrates an example procedure (900) for a device to initiate a request to exchange SLPP message data and / or transmit SL-PRS with the gNB server, in accordance with aspects of this disclosure. For example, an UE with SL positioning capability may initiate procedures to indicate its interest in transmitting or receiving SL positioning information / operation in various scenarios. Examples of such scenarios include successful connection establishment and / or connection resumption, alteration of SL positioning information transmission or reception, alteration of QoS profile(s), receipt of UE capability information, sidelink / SLPP message providing SL positioning capability information from an associated peer SL positioning UE, etc. Furthermore, an UE with SL positioning capability may initiate a procedure to request Petition 870250089739, dated 02 / 10 / 2025, pages 166 / 209 58 / 92 the assignment of dedicated sidelink DRB configuration(s) and the transmission of time-frequency resources for the SL positioning reference signal and the transmission of SL positioning data, for example, SLPP.

[00105] In procedure (900), at step (902), a UE (104) may receive from a NE (102) (e.g., an NG-RAN node, such as a gNB server) a system information transmission message, including SIB12 and / or a new SL positioning SIB, containing the initial common SL positioning configuration information applicable to one or more UEs / devices. In implementations, the UE (104) may not receive SIB 12 or the new SL positioning SIB, but may still proceed to Step (904) with the transmission of SL UE information, including information related to the start of SL positioning procedures. Note that SIB 12 is used as an example in Table 9 below; however, a new or equivalent SIB may be defined containing the same information for SL positioning.

[00106] The content of the system information transmission message may include the following information elements, as listed in Table 9: Table 9: SIB 12 or new SIB for SL positioning information COMMON Parameter Description List of SL Positioning Radio Carrier Configurations Indicates one or more sidelink radio carrier configurations for SL Positioning. SL radio carrier configurations may apply to sidelink data radio carriers (DRBs) or other implementations, sidelink signaling radio carriers (SRBs). >SL PDCP Configuration Indicates the PDCP parameters for the sidelink DRB intended to carry SL positioning information. >SL SDAP Configuration Indicates how to map sidelink QoS flows to sidelink DRBs intended to carry SL positioning information. >SL Radio Carrier Index Indicates the SL DRB configuration Petition 870250089739, dated 02 / 10 / 2025, pp. 167 / 209 59 / 92 Parameter Description SL DFN Offset Indicates the time offset for the UE to determine the DFN time when GNSS is used as a time reference. The value 1 corresponds to 0.001 milliseconds, the value 2 corresponds to 0.002 milliseconds, and so on. SL PRS or Positioning Message Priority Indicates the transmission and / or reception priority of SL Positioning. SL Positioning Frequency Information List Indicates the SL positioning configuration for a list of carrier frequencies for transmission and reception of SL-PRS messages and SL positioning (SLPP).Information on the validity of the SL-PRS / SL positioning area. Information on the SL-PRS / SL positioning validity configuration, including time-based validity criteria (e.g., timer, validity time, etc.) and / or area-based validity criteria, e.g., zone information (e.g., zone IDs), physical cell identity (PCI), SIB area validity, cell IDs. Common information on SL positioning measurement. Indicates common measurement settings (e.g., SLPRS RSRP) for SL-PRS.

[00107] Step (904): This RRC message (e.g., sidelink UE information or similar message) may share information related to the UE (104) SL positioning with the NE (102) (such as with the gNB server), indicating that the UE (104): Is it currently configured to receive and / or transmit SL and / or SL-PRS positioning messages? You are requesting the allocation or release of transmission resources for SL and / or SL-PRS positioning messages; is reporting SL positioning QoS parameters and / or associated SL transport QoS profile(s) related to SL positioning; and / or is reporting UE Sidelink positioning capacity information for the associated UE pair for communication of all transmission types; The message content in step (904) may include the following information elements, as listed in Table 10. For illustrative purposes, the Sidelink UE Information RRC message is used. Petition 870250089739, dated 02 / 10 / 2025, pages 168 / 209 60 / 92 as shown in the example in the table below. However, a new RRC message can be defined and / or another existing RRC message can be used to carry the same information containing information related to SL Positioning. Table 10: Sidelink EU information, including information RELATED TO SL'S POSITIONING Parameter Description List of frequencies of interest in SL Positioning Rx Indicates the frequency index at which the UE is interested in receiving SL Positioning (SLPP) or SLPRS messages. The value 1 corresponds to the frequency of the first entry in the SL Frequency Information List transmitted in SIB12, the value 2 corresponds to the frequency of the second entry in the SL Frequency Information List transmitted in SIB12, and so on. If SIB12 is not provided, the UE relies on the same information from the SL Positioning Rx Interest List received and stored via a previous sidelink UE information message or, if this is not available, relies on the pre-configuration of the SL Positioning Rx interest frequencies.List of Unicast, Groupcast, Interested Rx SL Positioning Transmission Destinations Indicates the QoS profile reported and associated with one or more destinations / receivers that the UE is interested in receiving on the network for unicast, groupcast, and SL-PRS and SLPP / SL SL positioning broadcasts. This destination list may contain a set of Layer 2 Destination IDs, which may be generated in the Reach / SL positioning layer. Anchor or Destination UE SL Positioning Source Identity Indicates the Layer-2 Source ID to be used to establish a PC5 link with the respective destination UE or anchor UE. SL Positioning Transmission Resource Request Parameters for requesting transmission resources for SL or SL-PRS positioning from the gNB server in the Sidelink UE Information report > SL UE Capacity Information Indicates the SL Positioning UE capacity for the network.Detailed and relevant resources for performing SL positioning are provided using the SL Positioning Capabilities IE in SL Positioning-related Information. >SL Positioning Transmission Type Indicates the transmission type for the corresponding destination to which to request resources for SL-PRS and / or SLPP messages. >SL Positioning Destination ID Indicates the destination to which the SL Positioning transmission resource request and network allocation are applicable. This destination ID may include a Layer 2 Destination ID, which may be generated in the Reach / SL positioning layer. >SL Transport QoS Information List Includes the QoS profile of the sidelink QoS flow, as shown in Error! Reference source not found, applicable to SL Positioning messages. >SL QoS Flow ID Uniquely identifies a sidelink QoS flow between the... Petition 870250089739, dated 02 / 10 / 2025, pp. 169 / 209 61 / 92 Parameter Description UE and the gNB server, which is unique for different destinations and transmission types indicated above. >SL RLC Mode Indications Indicates the RLC mode and, optionally, the related QoS profiles for the sidelink radio data carrier, which has not been configured by the network and is initiated by another target EU, anchor EU, or server EU in unicast, groupcast, or broadcast. The RLC mode for a sidelink radio carrier is aligned between UE and NW by the SL QoS Flow ID. >SL Tx Frequency List Each entry in this field indicates the frequency index at which the UE is interested in transmitting SL-PRS and SL Positioning (SLPP) messages. The value 1 corresponds to the frequency of the first entry in the SL Frequency Information List transmitted in SIB12, the value 2 corresponds to the frequency of the second entry in the SL Frequency Information List transmitted in SIB12, and so on.If SIB12 is not provided, the UE relies on the same information from the SL Positioning Transaction Interested Frequency List received and stored via a previous sidelink UE information message, or, if this is not available, relies on the pre-configuration of the SL Positioning Transaction Interested frequencies. > SL Tx Synchronization List A list of synchronization references used by the requesting UE. The requesting UE must include the same number of entries, listed in the same order, as in the SL Transmission Frequency List, i.e., one for each carrier frequency included in the SL Transmission Frequency List. Synchronization references may include the GNSS synchronization source, the eNB / gNB synchronization source, or the UE synchronization reference. > SL Positioning Session ID Indicates the ID of the specific SL positioning session for which the transmission resource is requested.A UE can request resources for one or more parallel SL positioning sessions. This information can be retrieved through layer-to-layer interaction between SLPP and RRC. SL Positioning Transmission Resource Request List: List of parameters for requesting transmission resources for SL positioning for one or more destination UEs or associated responders. UE Type: Indicates whether the UE is acting as an anchor UE, destination UE, server UE, client UE, or assistant UE.Information related to SL positioning. Parameters that transmit information related to SL positioning applicable to a specific session. >SL Positioning Capabilities. Indicates the UE's SL positioning capabilities, including supported positioning methods, and can be retrieved through layer interaction between SLPP and RRC. >SL Positioning Methods. Indicates the SL positioning method for which transmission resources are requested for SL-PRS transmission. >List of SL Positioning QoS Information. Indicates the positioning QoS associated with the resource request transmission with the parameters detailed previously in Emphasis 1. Discovery Request. Parameters to request transmission resources for. Petition 870250089739, dated 02 / 10 / 2025, pages 170 / 209 62 / 92 Parameter Description SL Positioning Discovery Transmission Resource SL Positioning Discovery for the gNB Server in the Sidelink UE Information Report >SL Positioning Discovery Cast Type SL Indicates the type of cast for the corresponding destination to which to request SL Positioning Discovery messages >SL Positioning Discovery Destination ID Indicates the destination to which the SL Positioning Discovery resource request and network allocation are applicable. >SL Positioning Discovery Source ID Indicates the L2 source ID of the SL Positioning Discovery transmission by destination UE, anchor UE, server UE, client UE, or similar. >SL Positioning Discovery Transmission Frequency List Each entry in this field indicates the frequency index at which the UE is interested in transmitting SL Positioning Discovery messages.The value 1 corresponds to the frequency of the first entry in the SL Frequency Information List transmitted in SIB12, the value 2 corresponds to the frequency of the second entry in the SL Frequency Information List transmitted in SIB12, and so on. If SIB12 is not provided, the UE relies on the same information from the SL Positioning Transaction Discovery Frequency List received and stored via a previous sidelink UE information message, or, if this is not available, it relies on the pre-configuration of the SL Positioning Transaction Discovery frequencies of interest.

[00108] Step 906: Transmission of time-frequency resources from NE (102) to UE (104), including resource pool information (e.g., resource pool dedicated only to SL-PRS, shared pool including SL-PRS and SL data), which may be provided to UE (104) via lower-layer signaling such as DCI and / or an RRC message, e.g., RRCReconfiguration, and / or a separate / new SL Positioning Information message. This resource message may be a high-level resource configuration message, indicating a general set of resources to perform the transmission of SL-PRS and SL positioning data messages applicable to a cell. This may include: • one or more dedicated SL-PRS resource pools for Mode 1 / Scheme 1 transmissions and / or Mode 2 / Scheme 2 transmissions; • one or more shared resource pools of SL-PRS and SL communication data for Mode 1 / Scheme 1 transmissions and / or Petition 870250089739, dated 02 / 10 / 2025, pp. 171 / 209 63 / 92 Mode 2 / Scheme 2 transmissions; • one or more exceptional SL positioning resource pools for exceptional transmissions, including cases where the UE is transitioning from the RRC_IDLE to RRC_CONNECTED state, experiences a Uu radio link failure, performs a transfer, or switches between a transmission resource pool, for example, from a dedicated resource pool to a shared resource pool, which may include only SLPRS or SL-PRS and SL positioning data messages; • In implementations, Mode 1 / Scheme 1 may refer to a centralized resource allocation scheme, where gNB manages and schedules SL transmissions, while Mode 2 / Scheme 2 may refer to a distributed resource allocation scheme, where each UE autonomously detects and executes the selection of desired transmission resources.

[00109] In implementations, a UE can transmit sidelink UE information messages on behalf of multiple UEs involved in a single SL positioning session. This can reduce the signaling overhead of each UE involved in an SL positioning session due to the individual transmission of an SL UE information message.

[00110] As mentioned above, implementations also include the delivery of SL positioning assistance data involving a location server. For example, in scenarios involving a location server, the location server can deliver SL-PRS (SL Positioning) assistance data, such as the inclusion of dedicated (SL-PRS only) and / or shared / common (SL-PRS and SL data) Mode 1 and / or Mode 2 resource pool information, in a semi-static manner, to a UE via LPP / SLPP signaling, for example, upon UE request and / or periodically after a period. This can be beneficial as the server Petition 870250089739, dated 02 / 10 / 2025, pages 172 / 209 64 / 92 location can have multiple sets of SL positioning data from multiple NG-RAN nodes; however, this SL positioning assistance data delivery mechanism may not be dynamic enough.

[00111] Depending on the implementation, a gNB server (e.g., an NG-RAN server node) and / or neighboring gNBs may transmit unsolicited SL PRS configuration response messages containing the requested SL-PRS transmission characteristics to a location server. In additional or alternative implementations, requested requests may be transmitted by the location server to receive the SL-PRS transmission characteristics from the NG-RAN nodes.

[00112] Figure 10 illustrates an example of a procedure (1000) that supports sidelink positioning assistance, in accordance with aspects of this disclosure. The procedure (1000), for example, provides for the supply of SL-PRS semi-static configuration information by the location server to the UE / device. In implementations, the SL-PRS semi-static configuration consists of SL-PRS transmission characteristics, which may allow the UE to transmit SL-PRS to one or more other UEs, for example, unicast, groupcast, or broadcast. In implementations, the semi-static configuration may also be applied to the transmission of SL positioning data messages, for example, SLPP messages to one or more other UEs, such as via unicast, groupcast, and / or broadcast. The UE, for example, may use the semi-static configuration based on configured validity criteria (e.g., time-based criteria, area-based criteria, etc.).) associated with one or more semi-static configurations. If the semi-static configuration is invalid, the associated semi-static configuration(s) may also be considered invalid. In implementations, the UE / device may represent a target EU, an anchor EU, a server EU, or an involved EU. Petition 870250089739, dated 02 / 10 / 2025, pages 173 / 209 65 / 92 SL-PRS transmission, etc.

[00113] In procedure (1000), in step (1004), a location server (1002) (e.g., LMF) may request from an NE (102) (e.g., an NG-RAN node) a request for SL-PRS configuration information, including SL-PRS transmission characteristics of the applicable NG-RAN node, which may be provided periodically or whenever said transmission characteristics are updated / released. The requested SL-PRS transmission characteristics may include one or more of the following: • ID of the dedicated SL positioning resource pool for SL-PRS or SL Mode / Scheme 1 or Mode / Scheme 2 positioning transmissions; • ID of the shared SL positioning resource pool for SL-PRS or SL Mode / Scheme 1 or Mode / Scheme 2 positioning transmissions; • An SL-PRS resource index ID comprising the following can also be shared with the NG-RAN node location server (in implementations, the NG-RAN node can receive this information from the UE in the case of SL MO-LR or SL UE-based positioning): SL-PRS bandwidth in terms of PRBs, subchannels, subchannel size; The SL-PRS magazine size in terms of: SL-PRS comb displacements and associated SL-PRS comb sizes (N); Initial symbols of SL-PRS and number of SL- symbols PRS (M); The SL-PRS start time can be relative to SFN0 or DFN0, and the total duration of the SL-PRS is given by X ms. SL-PRS Periodicity in terms of: Petition 870250089739, dated 02 / 10 / 2025, pages 174 / 209 66 / 92 ySL-PRS1pos-1t 2μ{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} slots, where μ=0,1,2,3 according to a subcarrier spacing of SL-PRS=15, 30, and 120 kHz respectively; SL-PRS1pos-2e{100,200,300,400,500,600,700,800,900,1000,5000,10000} milliseconds (ms); In implementations, the configured grant periodicity can be a combination of TpSLsPRS and TpoL-PRS to cover multiple periodicity values; An SL-PRS resource ID can identify a time-frequency resource within a slot of a dedicated SL PRS resource pool that is used for SL PRS transmission and, in scenarios involving a resource pool shared with SL data transmissions, identify a time-frequency resource based on an SL PRS resource ID and an SL PRS Frequency Domain allocation; The SL-PRS ID, which uniquely identifies an SL-PRS based on the SL-PRS resource ID and / or the SL-PRS feature set ID; The ID of the SL placement session; The ID of the SL-PRS resource set; SL's BWP ID; The SL operator ID; SL-PRS repeats; and / or the SL-PRS silencing pattern; • Validity period associated with the SL-PRS transmission characteristics above, based on a start and duration timer or an expiration timer. In implementations, the validity Petition 870250089739, dated 02 / 10 / 2025, pp. 175 / 209 67 / 92 of the semi-static SL-PRS configurations can be associated with an area validity, for example, the SL-PRS configurations are valid only in certain zones with zone IDs, cells, TRPs, PCI, CGI, TAI, RAN notification areas and / or combinations thereof; • Example signage may include NRPPa signage and associated messages.

[00114] In step (1006), NE (102) may respond with one or more SL-PRS configuration information, including SL-PRS transmission characteristics. Example signaling may include NRPPa signaling and associated messages. In step (1008), as in the case of unavailability of one or more SL-PRS configuration information, including SL-PRS transmission characteristics, NE (102) may indicate this appropriately. Example signaling may include NRPPa signaling and associated messages.

[00115] In step (1010), and based at least in part on the type of positioning performed (e.g., SL MO-LR-based positioning and / or SL UE-based positioning), the UE (104) may request semistatic SL positioning assistance data. The request for semistatic SL positioning assistance data configuration may include SL-PRS transmission features and / or SL positioning data message features. In implementations, semistatic SL positioning assistance data may override preconfigured SL positioning assistance data. Additionally, the UE (104) may use the semistatic SL positioning assistance data configuration first before the previously stored and / or preconfigured semistatic SL positioning assistance data configuration. Example signaling may include SLPP / LPP signaling and associated messages. Petition 870250089739, dated 02 / 10 / 2025, pages 176 / 209 68 / 92

[00116] In step (1012), the location server (1002) can signal SL positioning assistance data, including SL-PRS semistatic transmission features, to the UE (104) using UE-specific signaling, such as LPP / SLPP, or transmission signaling via positioning SIBs. Example signaling may include SLPP / LPP signaling and associated messages. In step (1014), the location server (1002) can signal the unavailability of the requested SL-PRS semistatic transmission features to the UE (104) using UE-specific signaling, such as LPP / SLPP. In implementations, steps (1006, 1008, 1012, and / or 1014) can be transmitted unsolicited. Example signaling may include SLPP / LPP signaling and associated messages.

[00117] Figure 11 illustrates an example of a procedure (1100) that supports sidelink positioning assistance, in accordance with aspects of this disclosure. The procedure (1100), for example, provides discovered UEs for SL positioning and associated coverage status without the involvement of the location server. In step (1102), an NE (102) (e.g., an NG-RAN node, such as a gNB server) can transmit to a UE (104) SIB 12 and / or new Common SL Positioning Settings SIB=V2X, including common SL Positioning settings. In step (1104), the UE (104) can transmit to the NE (102) a sidelink UE information message, including discovered UEs and associated coverage status. In step (1106), NE (102) can transmit to UE (104) a resource message, including SL positioning time-frequency information, for example, an SL positioning resource pool configuration.

[00118] In procedure (1100), as in scenarios where a location server is involved, a request for assistance data Petition 870250089739, dated 02 / 10 / 2025, pages 177 / 209 69 / 92 to SL positioning can transmit information about already discovered UEs and their respective coverage status. The steps may be similar to procedure (1000) Error! Reference source not found. Except that, in at least some implementations, the SL positioning assistance data request may include the following information: • Uncovered EUs consisting of: The UE Type: Anchor UE (with or without known location information), Server UE, Client UE, Assistant UE; The UE ID, such as 5G TMSI (when in coverage), Layer 2 source ID, Layer 2 destination ID, group IDs, and associated member IDs; Indication of coverage status using a flag or variable of choice that includes within coverage or outside coverage; • SL positioning QoS information.

[00119] Figure 12 illustrates an example of a procedure (1200) that supports sidelink positioning assistance, in accordance with aspects of this disclosure. The procedure (1200), for example, provides discovered UE for SL positioning and coverage status associated with location server engagement. In step (1202), a location server (1002) (e.g., LMF) can transmit to an NE (102) (e.g., an NG-RAN node) a request for SL-PRS transmission characteristics. In step (1204), the NE (102) can transmit SL-PRS transmission characteristics to the location server (1002). In step (1206), and optionally, the NE (102) can transmit to the location server (1002) an indication of unavailability of SL-PRS configuration information.

[00120] In (1208), UE (104) may optionally transmit to the location server (1002) a request for SL positioning assistance data, including discovered UEs and the status of Petition 870250089739, dated 02 / 10 / 2025, pp. 178 / 209 70 / 92 coverage associated. At (1210), the location server (1002) can transmit to UE (104) SL positioning assistance data and at (1212) the location server (1002) can transmit to UE (104) an indication of the unavailability of SL positioning assistance data.

[00121] According to the implementations, UE (104) in procedures (1100) and (1200) may already have received coverage status from discovered UEs through multiple signaling mechanisms, including lower layer signaling such as 1st or 2nd stage SCI, SL MAC CE and / or upper layer signaling such as PC5 RRC, SLPP, PC5-S and so on. A coverage status request may also be based on solicited or unsolicited messages.

[00122] Figure 13 illustrates an example of a UE (1300) according to aspects of this disclosure. The UE (1300) may include a processor (1302), a memory (1304), a controller (1306) and a transceiver (1308). The processor (1302), the memory (1304), the controller (1306) or the transceiver (1308), or various combinations thereof or multiple components thereof, may be examples of means for implementing multiple aspects of this disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) by means of one or more interfaces.

[00123] The processor (1302), memory (1304), controller (1306) or transceiver (1308), or various combinations or components thereof, may be implemented in hardware (e.g., circuits). 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 to execute the Petition 870250089739, dated 02 / 10 / 2025, pages 179 / 209 71 / 92 functions described in this disclosure.

[00124] The processor (1302) may include an intelligent hardware device (for example, a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor (1302) may be configured to operate the memory (1304). In other implementations, the memory (1304) may be integrated into the processor (1302). The processor (1302) may be configured to execute computer-readable instructions stored in memory (1304) to enable the UE (1300) to perform various functions of this disclosure.

[00125] Memory (1304) may include volatile or non-volatile memory. Memory (1304) may store computer-readable and executable code, including instructions that, when executed by the processor (1302), cause the UE (1300) to perform various functions described herein. The code may be stored on a computer-readable non-transient medium, such as memory (1304) or another type of memory. Computer-readable media includes non-transient storage media and communication media, including any media that facilitates the transfer of a computer program from one place to another. A non-transient storage medium may be any available media that can be accessed by a general-purpose or specific-purpose computer.

[00126] In some implementations, the processor (1302) and the memory (1304) coupled to the processor (1302) can be configured to cause the UE (1300) to perform one or more of the functions described herein (for example, executing, by the processor (1302), instructions stored in memory (1304)). For example, the processor (1302) can support wireless communication in the UE (1300), according to the examples disclosed herein. The UE (1300) can be configured or operable to support a means for Petition 870250089739, dated 02 / 10 / 2025, pages 180 / 209 72 / 92 transmit, from the UE to a second device, a configuration message, including an indication to perform one or more sidelink positioning reference signal (SLPRS) or SL positioning data message transmissions, the configuration message including one or more SL positioning parameters; and receive, from the second device, a resource configuration message, including a set of time-frequency resources to perform one or more SL-PRS or SL positioning data message transmissions.

[00127] In addition, the UE (1300) can be configured to support any one or a combination of receiving a higher-layer trigger to perform one or more transmissions of SL-PRS or SL positioning data messages; the higher-layer trigger includes one or more Sidelink Positioning Protocol (SLPP) layers, Vehicle-to-Everything (V2X) layer, ProSe layer, range layer, SL positioning layer, or Sidelink Positioning Application layer; receiving the higher-layer trigger from a UE via one or more of: higher-layer signaling, including one or more Sidelink Positioning Protocol (SLPP) layers, PC5 Radio Resource Control (RRC), or PC5-S;or lower-layer signaling, including one or more first-stage sidelink control information (SCI), first-stage medium access control (MAC) element control (CE), second-stage SCI, or second-stage MAC CE; the configuration message includes one or more SL positioning QoS profiles, at least one transport QoS profile indicating SL positioning transport QoS parameters, an SL positioning session identifier, SL-PRS transmission characteristics, or one or more discovered UEs for SL positioning.

[00128] In addition, the UE (1300) can be configured to Petition 870250089739, dated 02 / 10 / 2025, pages 181 / 209 73 / 92 support any one or combination of receiving a system information message including one or more common SL positioning configurations, to one or more common SL positioning configurations including at least one of an SL positioning radio carrier configuration list, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information; the UE includes one or more of a destination UE, an anchor UE, a server UE, or an appliance configured to perform one or more transmissions of SL-PRS or SL positioning data messages; the configuration message includes one or more of: an SL positioning transmission resource request; at least one unicast, groupcast, or broadcast destination list from the SL positioning receiver;one or more of a list of SL positioning transmitter or receiver frequencies; SL positioning UE type; one or more SL positioning capabilities; an SL positioning transmission resource discovery request; an SL positioning destination identifier; an SL positioning transmission type; or a coverage status of a discovered UE; the configuration message includes one or more dedicated shared SL-PRS pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more dedicated SL-PRS and SL communication data resource pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission;The configuration message includes a coverage status indication for a set of uncovered UEs, where the coverage status indication specifies whether each uncovered UE is in or out of coverage. Petition 870250089739, dated 02 / 10 / 2025, pages 182 / 209 74 / 92

[00129] Additionally, or alternatively, the UE (1300) may support the transmission, from the UE to an NE, of a configuration message including an indication to perform one or more transmissions of sidelink positioning reference signal (SL-PRS) or SL positioning data messages, the configuration message including one or more SL positioning parameters; and receive, from the second device, a resource configuration message including a set of time-frequency resources to perform one or more transmissions of SL-PRS or SL positioning data messages.

[00130] In addition, the UE (1300) can be configured to support any one or a combination of where the UE receives a higher-layer trigger to perform one or more SL-PRS or SL positioning data message transmissions; the higher-layer trigger includes one or more Sidelink Positioning Protocol (SLPP) layers, Vehicle-to-Everything (V2X) layer, ProSe layer, range layer, SL positioning layer, or Sidelink Positioning Application layer; the UE receives the higher-layer trigger from another UE via one or more of the following: higher-layer signaling, including one or more Sidelink Positioning Protocol (SLPP) layers, PC5 Radio Resource Control (RRC), or PC5-S;or lower-layer signaling, including one or more first-stage sidelink control information (SCI), first-stage medium access control (MAC) element control (CE), second-stage SCI, or second-stage MAC CE; the configuration message includes one or more SL positioning QoS profiles, at least one transport QoS profile indicating SL positioning transport QoS parameters, an SL positioning session identifier, SL-PRS transmission characteristics, or one or more discovered UEs for SL positioning; Petition 870250089739, dated 02 / 10 / 2025, pages 183 / 209 75 / 92

[00131] In addition, the UE (1300) can be configured to support any or a combination of where the UE receives a system information message including one or more common SL positioning configurations, to one or more common SL positioning configurations including at least one of an SL positioning radio carrier configuration list, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information or common SL positioning measurement information; the UE includes one or more of a destination UE, an anchor UE, a server UE or an appliance configured to perform one or more SL-PRS or SL positioning data message transmissions; the configuration message includes one or more of: an SL positioning transmission resource request;at least one of a unicast, groupcast, or broadcast destination list of the SL positioning receiver; one or more of an SL positioning transmitter or receiver frequency list; SL positioning UE type; one or more SL positioning capabilities; an SL positioning transmission resource discovery request; an SL positioning destination identifier; an SL positioning transmission type; or a coverage status of a discovered UE; the configuration message includes one or more dedicated shared SL-PRS pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more dedicated SL-PRS and SL communication data resource pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission;The configuration message includes a coverage status indication for a set of uncovered UEs, and the coverage status indication includes whether each uncovered UE is within coverage. Petition 870250089739, dated 02 / 10 / 2025, pages 184 / 209 76 / 92 or out of coverage.

[00132] The controller (1306) can manage input and output signals for the UE (1300). The controller (1306) can also manage peripherals not integrated into the UE (1300). In some implementations, the controller (1306) can utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller (1306) can be implemented as part of the processor (1302).

[00133] In some implementations, the UE (1300) may include at least one transceiver (1308). In some other implementations, the UE (1300) may have more than one transceiver (1308). The transceiver (1308) may represent a wireless transceiver. The transceiver (1308) may include one or more receiver chains (1310), one or more transmitter chains (1312), or a combination thereof.

[00134] A receiving chain (1310) may be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiving chain (1310) may include one or more antennas to receive a signal via an aerial or wireless medium. The receiving chain (1310) may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiving chain (1310) may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during signal transmission. The receiving chain (1310) may include at least one decoder to decode the demodulated signal and receive the transmitted data.

[00135] A transmission chain (1312) can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain (1312) can include at least one Petition 870250089739, dated 02 / 10 / 2025, pages 185 / 209 77 / 92 modulator for modulating data into a carrier signal, preparing the signal for wireless transmission. 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 such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain (1312) may also include at least one power amplifier configured to amplify the modulated signal to a power level appropriate for wireless transmission. The transmission chain (1312) may also include one or more antennas to transmit the amplified signal into the air or wirelessly.

[00136] Figure 14 illustrates an example of a processor (1400) according to aspects of the present disclosure. The processor (1400) may be an example of a processor configured to perform various operations according to the examples described herein. The processor (1400) may include a controller (1402) configured to perform various operations according to the examples described herein. The processor (1400) may optionally include at least one memory (1404), which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor (1400) may optionally include one or more arithmetic logic units (ALUs) (1406). One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) by means of one or more interfaces (e.g., buses).

[00137] The processor (1400) may be a processor chip set and include a protocol stack (e.g., a software stack) executed by the processor chip set to perform various operations (e.g., receive, get, retrieve, transmit, send, forward, store, determine, identify, access, write, read) according to Petition 870250089739, dated 02 / 10 / 2025, pages 186 / 209 78 / 92 with the examples described here. The processor chipset may include one or more cores, one or more caches (e.g., local memory or memory included in the processor chipset (e.g., the processor (1400)) 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).

[00138] The controller (1402) can 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 (1400) to enable the processor (1400) to support various operations, as described in the examples herein. For example, the controller (1402) can operate as a control unit of the processor (1400), generating control signals that manage the operation of various components of the processor (1400). These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[00139] The controller (1402) can be configured to fetch (e.g., get, retrieve, receive) instructions from memory (1404) and determine the subsequent instruction(s) to be executed so that the processor (1400) supports various operations as described in the examples herein. The controller (1402) can be configured to track memory addresses of instructions associated with memory (1404). The controller (1402) can be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller (1402) can be configured to interpret the instruction and Petition 870250089739, dated 02 / 10 / 2025, pages 187 / 209 79 / 92 determine the control signals to be sent to other processor components (1400) to enable the processor (1400) to support various operations as described in the examples herein. Additionally, or alternatively, the controller (1402) can be configured to manage the data flow within the processor (1400). The controller (1402) can be configured to control the data transfer between registers, ALUs (1406) and other functional units of the processor (1400).

[00140] The memory (1404) may include one or more caches (e.g., local memory or memory included in the processor (1400) or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory (1404) may reside within or on a processor chipset (e.g., local to the processor (1400)). In some other implementations, the memory (1404) may reside externally to the processor chipset (e.g., remote to the processor (1400)).

[00141] Memory (1404) can store computer-readable and executable code, including instructions that, when executed by the processor (1400), cause the processor (1400) to perform various functions described herein. The code can be stored in a non-transient, computer-readable medium, such as system memory or other types of memory. The controller (1402) and / or the processor (1400) can be configured to execute computer-readable instructions stored in memory (1404) to cause the processor (1400) to perform various functions. For example, the processor (1400) and / or the controller (1402) can be coupled to memory (1404), to the processor (1400), and to the controller (1402), and can be configured to perform various functions described herein. In some examples, the processor (1400) can include multiple processors and the memory (1404) can include multiple memories. One or more of the multiple Petition 870250089739, dated 02 / 10 / 2025, pp. 188 / 209 80 / 92 processors can be coupled to one or more of the multiple memories, which can be configured individually or collectively to perform various functions described herein.

[00142] One or more ALUs (1406) can be configured to support various operations, as described in the examples herein. In some implementations, one or more ALUs (1406) may reside within or on a processor chip set (e.g., the processor (1400)). In some other implementations, one or more ALUs (1406) may reside externally to the processor chip set (e.g., the processor (1400)). One or more ALUs (1406) can perform one or more calculations, such as addition, subtraction, multiplication, and division, on data. For example, one or more ALUs (1406) may receive input operands and an operation code, which determines an operation to be performed. One or more ALUs (1406) can be configured with a variety of logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation.Additionally, or alternatively, one or more ALUs (1406) can support logical operations such as AND, OR, XOR, NOR, and NAND, allowing one or more ALUs (1406) to handle conditional operations, comparisons, and bitwise operations.

[00143] The processor (1400) can support wireless communication according to the examples disclosed herein. The processor (1400) can be configured or operated to transmit, from a first device to a second device, a configuration message including an indication to perform one or more sidelink positioning reference signal (SL-PRS) or SL positioning data message transmissions, the configuration message including one or more SL positioning parameters; and receive, from the second device, a message of Petition 870250089739, dated 02 / 10 / 2025, pages 189 / 209 81 / 92 feature configuration including a time-frequency feature set to perform one or more SL-PRS data message transmissions or SL positioning.

[00144] In addition, the processor (1400) can be configured to support any one or a combination of to receive a higher-layer trigger to perform one or more SL-PRS or SL positioning data message transmissions; the higher-layer trigger includes one or more of the following: Sidelink Positioning Protocol Layer (SLPP), Vehicle-to-Everything Layer (V2X), ProSe Layer, Range Layer, SL Positioning Layer, or Sidelink Positioning Application Layer; at least one controller is configured to cause the processor to receive the higher-layer trigger from a UE via one or more higher-layer signaling, including one or more of the Sidelink Positioning Protocol Layer (SLPP), PC5 Radio Resource Control (RRC), or PC5-S;or lower layer signaling, including one or more first-stage sidelink control information (SCI), first-stage medium access control (MAC) element control (CE), second-stage SCI, or second-stage MAC CE; the configuration message includes one or more SL positioning QoS profiles, at least one transport QoS profile indicating SL positioning transport QoS parameters, an SL positioning session identifier, SL-PRS transmission characteristics, or one or more discovered UEs for SL positioning; receive a system information message including one or more common SL positioning configurations, one or more common SL positioning configurations including at least one from an SL positioning radio carrier configuration list, SL-PRS priority, positioning message priority, frequency information list; Petition 870250089739, dated 02 / 10 / 2025, pages 190 / 209 82 / 92 SL positioning, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[00145] In addition, the processor (1400) can be configured to support any or a combination of where the first device includes one or more of a target UE, an anchor UE, a server UE, or a device configured to perform one or more SL-PRS or SL positioning data message transmissions; the configuration message includes one or more of: an SL positioning transmission resource request; at least one list of unicast, groupcast, or broadcast SL positioning receiver destinations; one or more of an SL positioning transmitter or receiver frequency lists; SL positioning UE type; one or more SL positioning capabilities; an SL positioning transmission resource discovery request; an SL positioning destination identifier; an SL positioning transmission type; or a coverage status of a discovered UE;The configuration message includes one or more dedicated shared SL-PRS pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more dedicated SL-PRS and SL communication data resource pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes a coverage status indication for a set of discovered UEs, where the coverage status indication includes whether each discovered UE is in or out of coverage.

[00146] Figure 15 illustrates an example of a NE (1500) according to aspects of the present disclosure. The NE (1500) may include a processor (1502), a memory (1504), a controller (1506) and a transceiver (1508). The processor (1502), the memory (1504), the controller Petition 870250089739, dated 02 / 10 / 2025, pp. 191 / 209 83 / 92 (1506) or the transceiver (1508), or various combinations thereof or multiple components thereof, may be examples of means for carrying out multiple aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) by means of one or more interfaces.

[00147] The processor (1502), memory (1504), controller (1506) or transceiver (1508), or various combinations or components thereof, may be implemented in hardware (e.g., circuits). 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 this disclosure.

[00148] The processor (1502) may include an intelligent hardware device (for example, a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor (1502) may be configured to operate the memory (1504). In other implementations, the memory (1504) may be integrated into the processor (1502). The processor (1502) may be configured to execute computer-readable instructions stored in memory (1504) to enable the NE (1500) to perform various functions of the present disclosure.

[00149] Memory (1504) may include volatile or non-volatile memory. Memory (1504) may store computer-readable and executable code, including instructions that, when executed by the processor (1502), cause the NE (1500) to perform various functions described herein. The code may be stored on a non-transient, computer-readable medium, Petition 870250089739, dated 02 / 10 / 2025, pages 192 / 209 84 / 92 such as memory (1504) or other type of memory. Computer-readable media include both non-transient storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. A non-transient storage medium can be any available medium that can be accessed by a general-purpose or specific-purpose computer.

[00150] In some implementations, the processor (1502) and the memory (1504) coupled to the processor (1502) can be configured to make the NE (1500) perform one or more of the functions described here (for example, executing, by the processor (1502), instructions stored in memory (1504)). For example, the processor (1502) can support wireless communication in the NE (1500), according to the examples disclosed here.

[00151] The NE (1500) may be configured or operable to support a means of receiving, on the NE and from a UE, a configuration message including an indication to perform one or more transmissions of sidelink positioning reference signal (SL-PRS) or SL positioning data messages, the configuration message including one or more SL positioning parameters; and transmitting, to the UE, a resource configuration message including a set of time-frequency resources on which to perform one or more transmissions of SL-PRS or SL positioning data messages.

[00152] In addition, the NE (1500) can be configured to support any one or a combination of system information message transmission, including one or more common SL positioning configurations; one or more common SL positioning configurations include at least one of a list of SL positioning radio carrier configuration, SL-PRS priority, positioning message priority, SL positioning frequency information list, Petition 870250089739, dated 02 / 10 / 2025, pages 193 / 209 85 / 92 SL-PRS / SL positioning area validity information or common SL positioning measurement information.

[00153] The NE (1500) may be configured or operable to support a means of generating, in an NE, a semistatic configuration of one or more sidelink positioning reference signal transmission features (SL-PRS), including one or more shared or SL positioning feature sets; and transmitting the semistatic configuration to a UE.

[00154] In addition, the NE (1500) can be configured to support any one or a combination of where the semistatic configuration is associated with one or more of a validity time or a validity area; transmitting the semistatic configuration as one or more of a solicited message or an unsolicited message; transmitting, to the UE, an indication of unavailability of the SL positioning semistatic configuration; the SL-PRS transmission features include one or more of: dedicated SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL-PRS transmissions; dedicated SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL positioning transmissions; dedicated SL positioning resource pool identifier for one or more Mode 2 or Scheme 2 SL-PR transmissions;SL positioning dedicated resource pool identifier for one or more Mode 2 or Scheme 2 SL positioning transmissions; SL positioning shared resource pool identifier for one or more Mode 1 or Scheme 1 SL-PRS positioning transmissions; SL positioning shared resource pool identifier for one or more Mode 1 or Scheme 1 SL positioning transmissions; SL positioning shared resource pool identifier; Petition 870250089739, dated 02 / 10 / 2025, pages 194 / 209 86 / 92 for one or more Mode 2 or Scheme 2 SL-PRS positioning transmissions; SL positioning shared resource pool identifier for one or more Mode 2 or Scheme 2 SL positioning transmissions; or SL-PRS resource index including one or more SL-PRS bandwidth, SL-PRS comb size, SL-PRS periodicity, SL-PRS resource identifier, SL-PRS identifier, SL positioning session identifier, SL bandwidth portion (BWP) identifier, SL carrier identifier, or SL-PRS repeats.

[00155] In addition, the NE (1500) can be configured to support either or a combination of semistatic configuration transmission via one or more specific UE signals or transmission signals; one or more of: activation of the semistatic configuration via one or more specific UE signals or transmission signals; or deactivation of the semistatic configuration via one or more specific UE signals or transmission signals.

[00156] Additionally, or alternatively, the NE (1500) may support receiving, on a NE of a second device, a configuration message including an indication to perform one or more sidelink positioning data message transmissions (SL-PRS) or SL positioning, the configuration message including one or more SL positioning parameters; and transmitting, to the second device, a feature configuration message including a time-frequency feature set to perform one or more SL-PRS or SL positioning data message transmissions.

[00157] In addition, the NE (1500) can be configured to support any or a combination of where the NE transmits a system information message including one or more settings Petition 870250089739, dated 02 / 10 / 2025, pages 195 / 209 87 / 92 common SL positioning configurations; one or more common SL positioning configurations include at least one from a list of SL positioning radio carrier configurations, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[00158] Additionally, or alternatively, the NE (1500) can support the generation of a semi-static configuration of one or more sidelink positioning reference signal transmission features (SL-PRS), including one or more SL positioning pools or shared resources; and transmit the semi-static configuration to a UE.

[00159] In addition, the NE (1500) can be configured to support any one or a combination of where the semistatic configuration is associated with one or more of a validity period or a validity area; the NE transmits the semistatic configuration as one or more of a solicited message or an unsolicited message; the NE transmits, to the UE, an indication of unavailability of the SL positioning semistatic configuration; the SL-PRS transmission features include one or more of: dedicated SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL-PRS transmissions; dedicated SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL positioning transmissions; dedicated SL positioning resource pool identifier for one or more Mode 2 or Scheme 2 SL-PR transmissions;Dedicated SL positioning resource pool identifier for one or more Mode 2 or Scheme 2 SL positioning transmissions; Shared SL positioning resource pool identifier for one or more Mode 1 or Scheme 1 SL-PRS positioning transmissions; Petition 870250089739, dated 02 / 10 / 2025, pages 196 / 209 88 / 92 Shared resource pool identifier for SL positioning for one or more Mode 1 or Scheme 1 SL positioning transmissions; Shared resource pool identifier for SL positioning for one or more Mode 2 or Scheme 2 SL-PRS positioning transmissions; Shared resource pool identifier for SL positioning for one or more Mode 2 or Scheme 2 SL positioning transmissions; or SL-PRS resource index including one or more SL-PRS bandwidth, SL-PRS comb size, SL-PRS periodicity, SL-PRS resource identifier, SL-PRS identifier, SL positioning session identifier, SL bandwidth portion (BWP) identifier, SL carrier identifier, or SL-PRS repeats.

[00160] In addition, the NE (1500) can be configured to support either or a combination of where the NE transmits the semi-static configuration via one or more specific UE signals or broadcast signaling; the NE activates the semi-static configuration via one or more specific UE signals or broadcast signaling; and deactivates the semi-static configuration via one or more specific UE signals or broadcast signaling.

[00161] The controller (1506) can manage input and output signals for the NE (1500). The controller (1506) can also manage peripherals not integrated into the NE (1500). In some implementations, the controller (1506) can use an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller (1506) can be implemented as part of the processor (1502).

[00162] In some implementations, NE(1500) may include at least one transceiver (1508). In other implementations, NE(1500) may have more than one transceiver (1508). The transceiver (1508) may Petition 870250089739, dated 02 / 10 / 2025, pp. 197 / 209 89 / 92 represent a wireless transceiver. The transceiver (1508) may include one or more receiver chains (1510), one or more transmitter chains (1512) or a combination thereof.

[00163] A receiving chain (1510) may be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiving chain (1510) may include one or more antennas to receive a signal via an aerial or wireless medium. The receiving chain (1510) may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiving chain (1510) may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during signal transmission. The receiving chain (1510) may include at least one decoder to decode the demodulated signal and receive the transmitted data.

[00164] A transmitter chain (1512) may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain (1512) may include at least one modulator to modulate data into a carrier signal, preparing the signal for wireless transmission. 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 such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain (1512) may also include at least one power amplifier configured to amplify the modulated signal to a power level appropriate for wireless transmission. The transmitter chain (1512) may also include one or more antennas to transmit the amplified signal into the air or to a wireless medium.

[00165] Figure 16 illustrates a flowchart of a method Petition 870250089739, dated 02 / 10 / 2025, pages 198 / 209 90 / 92 (1600) in accordance with aspects of this disclosure. The method operations can be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the UE's functional elements to perform the described functions. It should be noted that the method described herein describes one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[00166] In (1602), the method may include the transmission, from a first device to a second device, of a configuration message comprising an indication to perform one or more sidelink positioning reference signal (SL-PRS) or SL positioning data message transmissions, wherein the configuration message comprises one or more SL positioning parameters. The operations of (1602) may be performed in accordance with the examples described herein. In some implementations, aspects of the operations of (1602) may be performed by a UE, as described with reference to Figure 13.

[00167] In (1604), the method may include receiving, from the second device, a resource configuration message comprising a set of time-frequency resources to perform one or more of the SL-PRS or SL positioning data message transmissions. The operations of (1604) may be performed according to the examples described herein. In some implementations, aspects of the operations of (1604) may be performed by a UE, as described with reference to Figure 13.

[00168] Figure 17 illustrates a flowchart of a method (1700) according to aspects of the present disclosure. The method operations can be implemented by a NE, as described herein. In some implementations, the NE can execute a set of instructions to Petition 870250089739, dated 02 / 10 / 2025, pages 199 / 209 91 / 92 control the functional elements of the NE to perform the described functions. It should be noted that the method described here describes one possible implementation, and that the operations and steps may be rearranged or modified in another way, and that other implementations are possible.

[00169] In (1702), the method may include receiving, on a first device and a second device, a configuration message comprising an indication to perform one or more sidelink positioning reference signal (SL-PRS) or SL positioning data message transmissions, wherein the configuration message comprises one or more SL positioning parameters. The operations of (1702) may be performed in accordance with the examples described herein. In some implementations, aspects of the operations of (1702) may be performed by a NE, as described with reference to Figure 15.

[00170] In (1704), the method may include transmitting to the second device a resource configuration message comprising a time-frequency resource set to perform one or more of the SLPRS or SL positioning data message transmissions. The operations of (1704) may be performed in accordance with the examples described herein. In some implementations, aspects of the operations of (1704) may be performed by a NE, as described with reference to Figure 15.

[00171] Figure 18 illustrates a flowchart of a method (1800) according to aspects of the present disclosure. The method operations can be implemented by a NE, as described herein. In some implementations, the NE may execute a set of instructions to control the NE's functional elements to perform the described functions. It should be noted that the method described herein describes a possible Petition 870250089739, dated 02 / 10 / 2025, pages 200 / 209 92 / 92 implementation, and that the operations and steps can be reorganized or modified in another way, and that other implementations are possible.

[00172] In (1802), the method may include the generation, in a first device, of a semistatic configuration of one or more sidelink positioning reference signal transmission features (SL-PRS), including one or more SL positioning pools or shared resources. The operations of (1802) may be performed according to the examples described herein. In some implementations, aspects of the operations of (1802) may be performed by a NE, as described with reference to Figure 15.

[00173] In (1804), the method may include transmitting the semistatic configuration to a second device. The operations of (1804) may be performed according to the examples described here. In some implementations, aspects of the operations of (1804) may be performed by a NE, as described with reference to Figure 15.

[00174] The description presented here is intended to enable a person with common technical knowledge in the field to create or use this disclosure. Several modifications to the disclosure will be evident to a person with common technical knowledge in the field, and the generic principles defined here can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and projects described here, but should be given the broader scope consistent with the principles and new features disclosed here. Petition 870250089739, dated 02 / 10 / 2025, pages 201 / 209

Claims

1 / 7 Claims 1. FIRST APPARATUS, characterized by comprising: at least one memory (1304, 1404, 1504); and at least one processor (1302, 1400, 1502) coupled to at least one memory (1304, 1404, 1504) and configured to cause the first apparatus to: transmit (1602), to a second apparatus, a configuration message comprising an indication to execute one or more of the sidelink positioning reference signals (SL-PRS) or SL positioning data message transmission, the configuration message comprising one or more SL positioning parameters; and receive (1604), from the second apparatus, a resource configuration message comprising a set of time-frequency resources on which it executes one or more SL-PRS or SL positioning data message transmissions.

2. FIRST APPARATUS, according to claim 1, characterized in that at least one processor (1302, 1400, 1502) is configured to cause the first apparatus to receive a higher-layer trigger to perform one or more transmissions of SL-PRS or SL positioning data messages.

3. FIRST APPARATUS, according to claim 2, characterized by the upper layer trigger comprising one or more layers of sidelink positioning protocol (SLPP), vehicle-to-all (V2X) layer, ProSe layer, reach layer, SL positioning layer or sidelink positioning application layer.

4. FIRST APPLIANCE, according to claim 2, characterized in that at least one processor (1302, 1400, 1502) is configured to cause the first appliance to receive the upper layer trigger from a UE (104, 1300) by means of one or more of: upper layer signaling comprising one or more of: sidelink positioning protocol layer (SLPP), PC5 radio resource control (RRC) or PC5-S; or lower layer signaling comprising one or more of: first-stage sidelink control information (SCI), first-stage medium access control (MAC) control element (CE), second-stage SCI or second-stage MAC CE.

5. FIRST APPARATUS, according to claim 1, characterized in that the configuration message comprises one or more SL positioning quality of service (QoS) profiles, at least one transport QoS profile indicating SL positioning transport QoS parameters, an SL positioning session identifier, SL-PRS transmission characteristics or one or more UE (104, 1300) discovered for SL positioning.

6. FIRST APPARATUS, according to claim 1, characterized in that at least one processor (1302, 1400, 1502) is configured to cause the first apparatus to receive a system information message comprising one or more common SL positioning configurations, the one or more common SL positioning configurations comprising at least one of a list of SL positioning radio carrier configuration, SLPRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information or common SL positioning measurement information.

7. FIRST APPARATUS, according to claim 1, characterized in that the first apparatus comprises one or more of a target user equipment (UE), an anchor UE, a server UE or an apparatus configured to perform one or more SL-PRS or SL positioning data message transmissions.

8. FIRST APPARATUS, according to claim 1, characterized in that the configuration message comprises one or more of: an SL positioning transmission resource request; at least one of a list of unicast, groupcast, or broadcast destinations of the SL positioning receiver; one or more of a list of SL positioning transmitter or receiver frequencies; SL positioning user equipment type (104, 1300) (UE); one or more SL positioning capabilities; an SL positioning transmission resource discovery request; an SL positioning destination identifier; an SL positioning transmission type; or a coverage status of a discovered UE (104, 1300).

9. FIRST APPARATUS, according to claim 1, characterized in that the configuration message comprises one or more dedicated shared pools of SL-PRS for at least one transmission of mode 1 and Scheme 1 or transmission of mode 2 and Scheme 2.

10. FIRST APPARATUS, according to claim 1, characterized in that the configuration message comprises one or more dedicated SL-PRS and SL communication data resource pools for at least one Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission. Petition 870250089739, dated 10 / 02 / 2025, pp. 204 / 209 4 / 7 11. FIRST APPARATUS, according to claim 1, characterized in that the configuration message comprises an indication of coverage status of a set of uncovered user equipment (104, 1300) (UE), and in that the coverage status indication comprises whether each uncovered UE (104, 1300) is in or out of coverage.

12. WIRELESS COMMUNICATION PROCESSOR (1302, 1400, 1502), characterized by comprising: at least one controller (1306, 1402, 1506) coupled with at least one memory (1304, 1404, 1504) and configured to cause the processor (1302, 1400, 1502) to: transmit (1602), from a first device to a second device, a configuration message comprising an indication to execute one or more of the sidelink positioning reference signals (SLPRS) or SL positioning data message transmission, the configuration message comprising one or more SL positioning parameters; and receive (1604), from the second device, a configuration message of resources comprising a set of time-frequency resources in which it executes one or more of the SL-PRS or SL positioning data message transmissions.

13. PROCESSOR (1302, 1400, 1502), according to claim 12, characterized in that at least one controller (1306, 1402, 1506) is configured to cause the processor (1302, 1400, 1502) to receive a higher-layer trigger to execute one or more SL-PRS or SL positioning data message transmissions.

14. PROCESSOR (1302, 1400, 1502), according to claim 13, characterized in that the upper layer trigger comprises one or more layers of sidelink positioning protocol (SLPP), Petition 870250089739, 10 / 02 / 2025, p. 205 / 209 5 / 7 vehicle-to-everything (V2X) layer, ProSe layer, reach layer, SL positioning layer or sidelink positioning application layer.

15. PROCESSOR (1302, 1400, 1502), according to claim 13, characterized in that at least one controller (1306, 1402, 1506) is configured to cause the processor (1302, 1400, 1502) to receive the upper layer trigger from a user equipment (104, 1300) (UE) by means of one or more of: upper layer signaling comprising one or more of: sidelink positioning protocol layer (SLPP), PC5 radio resource control (RRC) or PC5-S; or lower layer signaling comprising one or more of: first-stage sidelink control information (SCI), first-stage medium access control element (MAC), second-stage SCI or second-stage MAC CE.

16. PROCESSOR (1302, 1400, 1502), according to claim 12, characterized in that the configuration message comprises one or more SL positioning quality of service (QoS) profiles, at least one transport QoS profile indicating SL positioning transport QoS parameters, an SL positioning session identifier, SL-PRS transmission characteristics, or one or more discovered user equipment (UE) for SL positioning.

17. PROCESSOR (1302, 1400, 1502), according to claim 12, characterized in that at least one controller (1306, 1402, 1506) is configured to cause the processor (1302, 1400, 1502) to receive a system information message comprising one or more common SL positioning configurations, to one or more common SL positioning configurations comprising at least one of an SL positioning radio carrier configuration list, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information or common SL positioning measurement information.

18. PROCESSOR (1302, 1400, 1502), according to claim 12, characterized in that the first apparatus comprises one or more of: a destination user equipment (UE) (104, 1300), an anchor UE, a server UE or an apparatus configured to perform one or more SL-PRS or SL positioning data message transmissions.

19. USER EQUIPMENT (104, 1300) (UE) FOR WIRELESS COMMUNICATION, characterized by comprising: at least one memory (1304); and at least one processor (1302) coupled with the at least one memory (1304) and configured to cause the UE (104, 1300): to transmit (1602), to a second device, a configuration message comprising an indication to execute one or more of the sidelink positioning reference signals (SL-PRS) or SL positioning data message transmission, the configuration message comprising one or more SL positioning parameters; and to receive (1604), from the second device, a resource configuration message comprising a set of time-frequency resources in which it executes one or more SL-PRS or SL positioning data message transmissions.

20. NETWORK EQUIPMENT (102, 1500) FOR WIRELESS COMMUNICATION, characterized by comprising: at least one memory (1504); and at least one processor (1502) coupled to at least one memory (1504) and configured to cause the network equipment (102, 1500) to: receive (1702), from a second device, a configuration message comprising an indication to perform one or more transmissions of sidelink positioning reference signals (SL-PRS) or SL positioning data messages, the configuration message comprising one or more SL positioning parameters; and transmit (1704), to the second device, a resource configuration message comprising a set of time-frequency resources in which it performs one or more SL-PRS or SL positioning data message transmissions. Petition 870250089739, dated 02 / 10 / 2025, pp. 208 / 209

Images