RELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Application Serial No. 63/315,706 filed March 02, 2022 entitled “Sidelink Positioning Frequency Layer Configuration,” the disclosure of which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to sidelink positioning frequency layer configuration.

BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. Each network communication device, such as a base station, may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system, such as time resources (e.g., symbols, slots, subslots, mini-slots, aggregated slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers). Additionally, the wireless communications system may support wireless communications across various radio access technologies (RATs) including third generation (3G) RAT, fourth generation (4G) RAT, fifth generation (5G) RAT, and other suitable RATs beyond 5G. In some cases, a wireless communications system may be a non-terrestrial network (NTN), which may support various communication devices for wireless communications in the NTN. For example, an NTN may include network entities onboard non-terrestrial vehicles such as satellites, unmanned aerial vehicles (UAV), and high-altitude platforms systems (HAPS), as well as network entities on the ground, such as gateway entities capable of transmitting and receiving over long distances. [0004] As related to third generation partnership project (3 GPP) positioning framework, which includes UE-assisted and UE-based positioning procedures, there is a lack of support for efficient UE-to-UE range and orientation determinations, which is necessary to support relative positioning applications across other services, such as for vehicle-to-everything (V2X), public safety, industrial Internet of things (IIoT), commercial, and other applications. Relative positioning use cases can include new radio (NR) positioning in in-coverage, partial coverage, and out-of-coverage scenarios.

[0005] Uplink and downlink positioning reference signals (PRSs) are transmitted across time frequency resources, with a defined hierarchy in terms of positioning frequency layer (PFL), bandwidth part (BWP), resource set, and resources. Currently, there are no procedures that detail the hierarchical relationship among sidelink PFLs, sidelink BWP, resource pools, sidelink PRS resource set, and resources. These resource relationships are needed to determine the overall configured bandwidth in which the sidelink positioning measurements are to be measured, which can in turn impact the overall absolute and relative positioning accuracy of UE and other sidelink enabled devices as network entities in a wireless communications system.

SUMMARY

[0006] The present disclosure relates to methods, apparatuses, and systems that support sidelink positioning frequency layer configuration. By utilizing the described techniques, a network entity (e.g., a UE or other sidelink enabled device) and a sidelink device are operable to implement various aspects of sidelink positioning frequency layer configuration. Any network entity (e.g., a UE or other device) and/or the sidelink device may be implemented in a wireless communications system as a UE, a base station, a roadside unit, an anchor UE, a target UE, a reference UE, a location server, an unmanned or uncrewed ariel vehicle (UAV) (e.g., a drone), and/or as any other type of network devices or entities performing procedures for sidelink positioning frequency layer configuration.

[0007] Aspects of the disclosure are directed to the configuration of sidelink positioning frequency layer and configuring sidelink positioning reference signal resources using different hierarchical parameters, including sidelink positioning frequency layer (PFL), sidelink bandwidth part (BWP), resource pools, and resource sets. This disclosure describes sidelink PFL configuration options with respect to sidelink BWP, sidelink data resource pools, and Uu interface PFL. A sidelink PFL configuration message can provide hierarchical relationships of sidelink PFL, sidelink BWP, positioning resource pools, and sidelink resource sets for selecting PRS resources for sidelink PRS transmission. The sidelink PRS resources are configured for different receiving UEs and/or destination devices. In addition, sidelink PFL configuration may be defined by a bitmap within the sidelink BWP or a sidelink carrier.

[0008] Some implementations of the method and apparatuses described herein may include wireless communication and positioning configuration at a network device (e.g., a base station, a gNB, a UE, or other sidelink device), and the device configures a sidelink PRS configuration indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration. The sidelink positioning resource parameters of the sidelink PRS configuration can include one or more of a sidelink positioning frequency layer (PFL), a sidelink bandwidth part (BWP), a sidelink positioning resource pool (PRP), or a sidelink PRS. The network device can also transmit the sidelink PRS configuration to one or more receiving devices that utilize the hierarchal resource relationship of the sidelink positioning resource parameters to determine at least one PRS resource for sidelink PRS transmission.

[0009] In some implementations of the method and apparatuses described herein, the hierarchal resource relationship is configured as the sidelink PFL defined within a sidelink carrier and one or more sidelink PRSs are defined within the sidelink PFL. Alternatively, the hierarchal resource relationship is configured as the sidelink PFL defined within the sidelink BWP and one or more of sidelink PRSs are defined within the sidelink PFL. Alternatively, the hierarchal resource relationship is configured as the sidelink PRP defined within the sidelink BWP or the sidelink PFL, and one or more sidelink PRSs are defined within the sidelink PRP. Alternatively, the hierarchal resource relationship is configured as a time domain bitmap comprising sidelink slots and a time period that define the sidelink PFL within one of a sidelink carrier or the sidelink BWP. In implementations, the network device can transmit the sidelink PRS configuration via a location management function (LMF) utilizing LIE positioning protocol (LPP) and/or transmit the sidelink PRS configuration via a next-generation NodeB (gNB) utilizing radio resource control (RRC).

[0010] Some implementations of the method and apparatuses described herein may include wireless communication and positioning configuration at a receiving device (e.g., a UE or other sidelink device), and the device receives a sidelink PRS configuration indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration. The sidelink positioning resource parameters of the sidelink PRS configuration can include one or more of a sidelink PFL, a sidelink BWP, a sidelink PRP, or a sidelink PRS. The receiving device can process the hierarchal resource relationship of the sidelink positioning resource parameters to allocate at least one PRS resource for sidelink PRS transmission, and transmit the sidelink PRS transmission based on the received sidelink PRS configuration.

[0011] In some implementations of the method and apparatuses described herein, the receiving device can process the hierarchal resource relationship of the sidelink positioning resource parameters to determine a configured bandwidth in which sidelink positioning measurements are measured for absolute or relative positioning accuracy. The hierarchal resource relationship is configured as the sidelink PFL defined within a sidelink carrier and one or more sidelink PRSs are defined within the sidelink PFL. Alternatively, the hierarchal resource relationship is configured as the sidelink PFL defined within the sidelink BWP and one or more of sidelink PRSs are defined within the sidelink PFL. Alternatively, the hierarchal resource relationship is configured as the sidelink PRP defined within one of the sidelink BWP or the sidelink PFL, and one or more sidelink PRSs are defined within the sidelink PRP. Alternatively, the hierarchal resource relationship is configured as a time domain bitmap comprising sidelink slots and a time period that define the sidelink PFL within one of a sidelink carrier or the sidelink BWP. In implementations, the receiving device can receive the sidelink PRS configuration via a LMF utilizing LTE positioning protocol (LPP) and/or receive the sidelink PRS configuration via a next-generation NodeB (gNB) utilizing radio resource control (RRC).

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Various aspects of the present disclosure for sidelink positioning frequency layer configuration are described with reference to the following Figures. The same numbers may be used throughout to reference like features and components shown in the Figures.

[0013] FIG. 1 illustrates an example of a wireless communications system that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0014] FIG. 2 illustrates an example of positioning performance requirements as related to aspects of the present disclosure. [0015] FIG. 3 illustrates an example of absolute and relative positioning scenarios as related to sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0016] FIG. 4 illustrates an example of a multi-cell RTT procedure as related to sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0017] FIG. 5 illustrates an example of a system for existing relative range estimation as related to sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0018] FIG. 6 illustrates an example of a system of new radio (NR) beam- based positioning as related to sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0019] FIG. 7 illustrates an example of a downlink (DL)-TDOA assistance data configuration as related to sidelink positioning frequency layer configuration, as described herein.

[0020] FIG. 8 illustrates an example of measurement reporting information as related to sidelink positioning frequency layer configuration, as described herein.

[0021] FIG. 9 illustrates an example of a sidelink configured grant (CG) as related to sidelink positioning frequency layer configuration, as described herein.

[0022] FIG. 10 illustrates an example of a group member discovery with Model A procedure as related to sidelink positioning frequency layer configuration, as described herein.

[0023] FIG. 11 illustrates an example of a group member discovery with Model B procedure as related to sidelink positioning frequency layer configuration, as described herein.

[0024] FIG. 12 illustrates an example of a sidelink PFL and resource pool overlap that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0025] FIG. 13 illustrates an example of a sidelink PFL located within the sidelink carrier that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. [0026] FIG. 14 illustrates an example of PRS configuration levels as related to sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0027] FIG. 15 illustrates an example of a sidelink PRS hierarchical structure that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0028] FIG. 16 illustrates an example of another sidelink PRS hierarchical structure that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0029] FIG. 17 illustrates an example of another sidelink PRS hierarchical structure that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0030] FIG. 18 illustrates an example of a PRS hierarchical relationship that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0031] FIG. 19 illustrates an example of a PRS hierarchical relationship that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0032] FIG. 20 illustrates an example of a PRS hierarchical relationship that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0033] FIG. 21 illustrates an example block diagram of components of a device (e.g., a initiating device, network device) that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0034] FIG. 22 illustrates an example block diagram of components of a device (e.g., a receiving device, UE) that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure.

[0035] FIGs. 23-26 illustrate flowcharts of methods that support sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0036] Implementations of sidelink positioning frequency layer configuration are described, such as related to sidelink positioning frequency layer configuration. By utilizing the described techniques, a network entity (e.g., a UE or other sidelink enabled device) and a sidelink device are operable to implement various aspects of sidelink positioning frequency layer configuration. Any network entity (e.g., a UE or other device) and/or the sidelink device may be implemented in a wireless communications system as a UE, a gNB a base station, a roadside unit, an anchor UE, a target UE, a reference UE, a location server, an unmanned or uncrewed ariel vehicle (UAV) (e.g., a drone), and/or as any other type of network devices or entities performing procedures for sidelink positioning frequency layer configuration.

[0037] Uplink and downlink PRSs are transmitted across time frequency resources, with a defined hierarchy in terms of positioning frequency layer (PFL), bandwidth part (BWP), resource set, and resources. However, a hierarchal resource relationship of sidelink positioning resource parameters of a sidelink PRS configuration are not established, such as for positioning resource parameters that include a sidelink PFL, a sidelink BWP, a sidelink PRP, or a sidelink PRS. These resource relationships are needed to determine the overall configured bandwidth in which the sidelink positioning measurements are to be measured, which can in turn impact the overall absolute and relative positioning accuracy of UE and other sidelink enabled devices as network entities in a wireless communications system.

[0038] Aspects of the disclosure are directed to the configuration of sidelink positioning frequency layer and configuring sidelink positioning reference signal resources using the different hierarchical parameters. Further, this disclosure describes sidelink PFL configuration options with respect to sidelink BWP, sidelink data resource pools, and Uu interface PFL. A sidelink PFL configuration message can provide hierarchical relationships of sidelink PFL, sidelink BWP, positioning resource pools, and sidelink resource sets for selecting PRS resources for sidelink PRS transmission. The sidelink PRS resources can be configured for different receiving UEs and/or destination devices. In addition, sidelink PFL configuration may be defined by a bitmap within the sidelink BWP or a sidelink carrier. [0039] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flowcharts that relate to sidelink positioning frequency layer configuration.

[0040] FIG. 1 illustrates an example of a wireless communications system 100 that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as a NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0041] The one or more base stations 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the base stations 102 described herein may be, or include, or may be referred to as a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), a Radio Head (RH), a relay node, an integrated access and backhaul (IAB) node, or other suitable terminology. A base station 102 and a UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, a base station 102 and a UE 104 may perform wireless communication over a NR-Uu interface.

[0042] A base station 102 may provide a geographic coverage area 110 for which the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area. For example, a base station 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a base station 102 may be moveable, such as when implemented as a gNB onboard a satellite or other non-terrestrial station (NTS) associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, and different geographic coverage areas 110 may be associated with different base stations 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0043] The one or more UEs 104 may be dispersed throughout a geographic region or coverage area 110 of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, a customer premise equipment (CPE), a subscriber device, or as 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, a UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or as a machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In other implementations, a UE 104 may be mobile in the wireless communications system 100, such as an earth station in motion (ESIM).

[0044] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the base stations 102, other UEs 104, or network equipment (e.g., the core network 106, a relay device, a gateway device, an integrated access and backhaul (IAB) node, a location server that implements the location management function (LMF), or other network equipment). Additionally, or alternatively, a UE 104 may support communication with other base stations 102 or UEs 104, which may act as relays in the wireless communications system 100.

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

[0046] A base station 102 may support communications with the core network 106, or with another base station 102, or both. For example, a base station 102 may interface with the core network 106 through one or more backhaul links 114 (e.g., via an SI, N2, or other network interface). The base stations 102 may communicate with each other over the backhaul links 118 (e.g., via an X2, Xn, or another network interface). In some implementations, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other implementations, the base stations 102 may communicate with each other indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as remote radio heads, smart radio heads, gateways, transmissionreception points (TRPs), and other network nodes and/or entities.

[0047] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)), and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for the one or more UEs 104 served by the one or more base stations 102 associated with the core network 106.

[0048] According to implementations, one or more of the UEs 104 and base stations 102 are operable to implement various aspects of sidelink positioning frequency layer configuration, as described herein. For instance, a base station 102 is a network device (e.g., initiating device) that can configure a sidelink PRS configuration 116 indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration. The sidelink positioning resource parameters of the sidelink PRS configuration can include a sidelink PFL, a sidelink BWP, a sidelink PRP, or a sidelink PRS. The base station 102 (e.g., network device) can transmit the sidelink PRS configuration to the UE 104 as a receiving device that utilizes the hierarchal resource relationship of the sidelink positioning resource parameters to determine one or more PRS resources at 118 for sidelink PRS transmission. Accordingly, the UE 104 can transmit the sidelink PRS transmission 120 to the base station 102 based on the received sidelink PRS configuration 116 and the hierarchal resource relationship of the sidelink positioning resource parameters.

[0049] FIG. 2 illustrates an example 200 of positioning performance requirements in a Table T1 as related to sidelink positioning frequency layer configuration. The Table T1 lists industrial Internet of things (IIoT) positioning performance requirements (for release 17), which are especially stringent with respect to accuracy, latency, and reliability. Table T1 shows the positioning performance requirements for different scenarios in an IIoT or indoor factory setting.

[0050] The supported positioning techniques (release 16) are listed in Table T2, and separate positioning techniques can be currently configured and performed based on the requirements of the LMF and UE capabilities. The transmission of PRS enable the UE to perform UE positioning-related measurements to enable the computation of a UE’s location estimate and are configured per transmission reception point (TRP), where a TRP may transmit one or more beams. Various RAT- dependent positioning techniques (also referred to as positioning methods, or positioning procedures) are supported for a UE, for UE-assisted, LMF-based, and/or for next generation radio access network (NG-RAN) node assisted. The RAT-dependent positioning techniques that are supported include DL- TDOA, downlink-angle of departure (DL-AoD), multi-round trip time (multi-RTT), new radio enhanced cell-ID (NR E-CID); uplink-time difference of arrival (UL-TDOA); and uplink-angle of arrival (UL-AoA).

[0051] Table T2: Supported Rel-16 UE positioning methods

[0052] FIG. 3 illustrates an example 300 of absolute and relative positioning scenarios as related to measurement and reporting for sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The network devices described with reference to example 300 may use and/or be implemented with the wireless communications system 100 and include UEs 104 and base stations 102 (e.g., eNB, gNB). The example 300 is an overview of absolute and relative positioning scenarios as defined in the architectural (stage 1) specifications using three different coordinate systems, including (III) a conventional absolute positioning, fixed coordinate system at 302; (II) a relative positioning, variable and moving coordinate system at 304; and (I) a relative positioning, variable coordinate system at 306. Notably, the relative positioning, variable coordinate system at 306 is based on relative device positions in a variable coordinate system, where the reference may be always changing with the multiple nodes that are moving in different directions. The example 300 also includes a scenario 308 for an out of coverage area in which UEs need to determine relative position with respect to each other. [0053] With reference to RAT-dependent positioning techniques, the DL-TDOA positioning technique utilizes at least three network nodes for positioning based on triangulation. The DL-TDOA positioning method makes use of the downlink reference signal time difference (RSTD) (and optionally DL PRS RSRP) of downlink signals received from multiple transmission points (TPs) at the UE. The UE measures the downlink RSTD (and optionally 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 resulting measurements are used along with other configuration information to locate the UE in relation to the neighboring TPs.

[0054] The DL-AoD positioning technique makes use of the measured downlink PRS reference signal received power (RSRP) (DL PRS RSRP) of downlink signals received from multiple TPs at the UE. The UE measures the DL PRS RSRP of the received signals using assistance data received from the positioning server (also referred to herein as the location server), and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighboring TPs.

[0055] FIG. 4 illustrates an example 400 of a multi-cell RTT procedure as related to measurement and reporting for sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The multi-RTT positioning technique makes use of the UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs, as measured by the UE and the measured gNB Rx-Tx measurements and uplink sounding reference signal (SRS) RSRP (UL SRS- RSRP) at multiple TRPs of uplink signals transmitted from UE. The UE measures the UE Rx-Tx measurements (and optionally DL PRS RSRP of the received signals) using assistance data received from the positioning server (also referred to herein as the location server), and the TRPs the gNB Rx-Tx measurements (and optionally UL SRS-RSRP of the received signals) using assistance data received from the positioning server. The measurements are used to determine the RTT at the positioning server, which are used to estimate the location of the UE. The multi-RTT is only supported for UE-assisted and NG-RAN assisted positioning techniques as noted in Table T2.

[0056] FIG. 5 illustrates an example of a system 500 for existing relative range estimation as related to measurement and reporting for sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The system 500 illustrates the relative range estimation using the existing single gNB RTT positioning framework. The location server (e.g., an LMF) 502 can configure measurements to the different UEs (e.g., UE 104), and then the target UEs can report their measurements in a transparent way to the location server. The location server can compute the absolute location, but in order to get the relative distance between two of the UEs, it would need prior information, such as the locations of the target UEs.

[0057] For the NR enhanced cell ID (E-CID) positioning technique, the position of a UE is estimated with the knowledge of its serving ng-eNB, gNB, and cell, and is based on LTE signals. The information about the serving ng-eNB, gNB, and cell may be obtained by paging, registration, or other methods. The NR enhanced cell-ID (NR E-CID) positioning refers to techniques which use additional UE measurements and/or NR radio resources and other measurements to improve the UE location estimate using NR signals. Although enhanced cell-ID (E-CID) positioning may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE may not make additional measurements for the sole purpose of positioning (i.e., the positioning procedures do not supply a measurement configuration or measurement control message, and the UE reports the measurements that it has available rather than being required to take additional measurement actions).

[0058] The uplink time difference of arrival (UL-TDOA) positioning technique makes use of the UL-TDOA (and optionally UL SRS-RSRP) at multiple reception points (RPs) of uplink signals transmitted from UE. The RPs measure the UL-TDOA (and optionally UL SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.

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

[0060] FIG. 6 illustrates an example of a system 600 of NR beam-based positioning as related to measurement and reporting for sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The system 600 illustrates a UE 104 and base stations 102 (e.g., gNB). The PRS can be transmitted by different base stations (serving and neighboring) using narrow beams over FR1 and FR2 as illustrated in the example system 600, which is relatively different when compared to LTE where the PRS was transmitted across the whole cell. The PRS can be locally associated with a PRS resource identifier (ID) and resource Set ID for a base station (TRP). Similarly, UE positioning measurements such as reference signal time difference (RSTD) and PRS RSRP measurements are made between beams (e.g., between a different pair of DL PRS resources or DL PRS resource sets) as opposed to different cells as was the case in LTE. In addition, there are additional uplink positioning methods for the network to exploit in order to compute the target UE’s location.

[0061] The Tables T3 and T4 show the reference signal to measurements mapping for each of the supported RAT-dependent positioning techniques at the UE and gNB, respectively. The RAT- dependent positioning techniques may utilize the 3 GPP RAT and core network entities to perform the position estimation of the UE, which are differentiated from RAT-independent positioning techniques, which rely on global navigation satellite system (GNSS), inertial measurement unit (IMU) sensor, WLAN, and Bluetooth technologies for performing target device (UE) positioning. UE measurements have been defined (e.g., release 16), which are applicable to DL-based positioning techniques.

[0062] Table T3: UE measurements to enable RAT-dependent positioning techniques. [0063] Table T4: gNB measurements to enable RAT-dependent positioning techniques.

[0064] FIG. 7 illustrates an example 700 of a DL-TDOA assistance data configuration as related to sidelink positioning frequency layer configuration, as described herein. The information element (IE) NR-DL-TDOA-ProvideAssistanceData is used by the location server to provide assistance data to enable UE-assisted and UE-based NR downlink TDOA. It may also be used to provide NR DL TDOA positioning specific error reason.

[0065] FIG. 8 illustrates an example 800 of measurement reporting information as related to sidelink positioning frequency layer configuration, as described herein. The IE NR-DL-TDOA- SignalMeasurementlnformation is used by the target device to provide NR-DL TDOA measurements to the location server. The measurements are provided as a list of TRPs, where the first TRP in the list is used as reference TRP in case RSTD measurements are reported. The first TRP in the list may or may not be the reference TRP indicated in the NR-DL-PRS-AssistanceData. Furthermore, the target device selects a reference resource per TRP, and compiles the measurements per TRP based on the selected reference resource.

[0066] With reference to RAT-dependent positioning measurements, the different downlink measurements, including DL PRS RSRP, downlink RSTD, and UE Rx-Tx time difference required for the supported RAT-dependent positioning techniques are shown in Table T5. The measurement configurations may include four (4) pair of downlink RSTD measurements performed per pair of cells, and each measurement is performed between a different pair of downlink PRS resources or resource sets with a single reference timing; and eight (8) downlink PRS reference signal received power (RSRP) measurements can be performed on different downlink PRS resources from the same cell.

[0067] Table T5: Downlink measurements for downlink-based positioning techniques.

[0068] A positioning frequency layer consists of one or more downlink PRS resource sets, each of which consists of one or more downlink PRS resources as described in 3 GPP technical specification (TS) 38.214. For sequence generation, the UE assumes the reference-signal sequence r(m) is defined by where the pseudo-random sequence c(i) is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialised with where is the slot number, the downlink PRS sequence is given by the higher-layer parameter dl-PRS-SequencelD, and I is the orthogonal frequency division multiplexing (OFDM) symbol within the slot to which the sequence is mapped. [0069] In mapping to physical resources in a downlink PRS resource, for each downlink PRS resource configured, the UE assumes the sequence r(m) is scaled with a factor β _PRS and mapped to resources elements according to when the following conditions are fulfilled:

• the resource element is within the resource blocks occupied by the downlink PRS resource for which the UE is configured;

• the symbol I is not used by any synchronization signal/physical broadcast channel (SS/PBCH) block used by a serving cell for downlink PRS transmitted from the same serving cell or any SS/PBCH block from a non-serving cell whose time frequency location is provided to the UE by higher layers for downlink PRS transmitted from the same non-serving cell;

• the slot number satisfies the conditions in TS 38.321 (clause 7.4.1.7.4) of 3GPP. and where the antenna port p = 5000 is the first symbol of the downlink PRS within a slot and given by the higher-layer parameter dl-PRS-ResourceSymbolOffset; the size of the downlink PRS resource in the time domain is given by the higher-layer parameter dl-PRS-NumSymbols; the comb size is given by the higher- lay er parameter dl-PRS- CombSizeN such that the combination the resource-element offset is obtained from the higher-layer parameter dl-PRS-CombSizeN-AndReOffset, the quantity k' is given by Table T6. [0070] The reference point for k = 0 is the location of the point A of the positioning frequency layer, in which the downlink PRS resource is configured where point A is given by the higher-layer parameter dl-PRS-PointA.

[0071] Table T6 shows the frequency offset k' as a function of

[0072] In mapping to slots in a downlink PRS resource set, for a downlink PRS resource in a downlink PRS resource set, the UE assumes the downlink PRS resource being transmitted when the slot and frame numbers fulfil and one of the following conditions are fulfilled:

• the higher-layer parameters dl-PRS-MutingOptionl and dl-PRS-MutingOption2 are not provided;

• the higher-layer parameter dl-PRS-MutingOptionl is provided with bitmap {b ¹ } but dl- PRS-MutingOption2 with bitmap {b ² } is not provided, and bit is set;

• the higher-layer parameter dl-PRS-MutingOption2 is provided with bitmap {b ² } but dl- PRS-MutingOptionl with bitmap {b ¹ } is not provided, and bit is set;

• the higher-layer parameters dl-PRS-MutingOptionl with bitmap {b ¹ } and dl-PRS- MutingOption2 with {b ² } are both provided, and both bit and are set. where

• given by the higher-layer parameter dl-PRS-MutingOptionl where is the size of the bitmap; • bitmap given by the higher-layer parameter dl-PRS-MutingOption2;

• the periodicity {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} and the slot offset are given by the higher-layer parameter dl-PRS- Periodicity-and-ResourceSetSlotOffset;

• the downlink PRS resource slot offset is given by the higher- lay er parameter dl- PRS-ResourceSlotOffset,

• the repetition factor is given by the higher-layer parameter dl- PRS-ResourceRepetitionFactor,

• the muting repetition factor is given by the higher-layer parameter dl-PRS- MutingBitRepetitionFactor,

• the time gap is given by the higher-layer parameter dl-PRS- ResourceTimeGap;

[0073] For a downlink PRS resource in a downlink PRS resource set configured, the UE shall assume the downlink PRS resource being transmitted as described in clause 5.1.6.5 of 3 GPP TS 38.214.

[0074] For sidelink CG configuration as described in 3GPP TS 38.321, there are two types of transmission without dynamic sidelink grant: configured grant Type 1 where an sidelink grant is provided by RRC, and stored as configured sidelink grant; and configured grant Type 2 where an sidelink grant is provided by physical downlink control channel (PDCCH), and stored or cleared as configured sidelink grant based on LI signaling indicating configured sidelink grant activation or deactivation.

[0075] Type 1 and/or Type 2 are configured with a single bandwidth part (BWP). Multiple configurations of up to eight (8) configured grants (including both Type 1 and Type 2, if configured) can be active simultaneously on the BWP. RRC configures the following parameters when the configured grant Type 1 is configured, as specified in 3GPP TS 38.331 or 3GPP TS 36.331:

• sl-ConfiglndexCG: the identifier of a configured grant for sidelink; • sl-CS-RNTI: sidelink configure scheduling radio network temporary identifier (SLCS- RNTI) for retransmission;

• sl-NrOjHARQ-Processes: the number of HARQ processes for configured grant;

• sl-PeriodCG'. periodicity of the configured grant Type 1 ;

• sl-TimeOffsetCG-Type 1: Offset of a resource with respect to reference logical slot defined by sl-TimeReferenceSFN-Typel in time domain, referring to the number of logical slots in a resource pool;

• sl-TimeResourceCG-Typel : time resource location of the configured grant Type 1 ;

• sl-CG-MaxTransNumList. the maximum number of times that a TB can be transmitted using the configured grant;

• sl-HARQ-ProcID-offset. offset of HARQ process for configured grant Type 1 ;

• sl-TimeReferenceSFN-Type 1. SFN used for determination of the offset of a resource in time domain. If it is present, the UE uses the first logical slot of associated resource pool after the starting time of the closest SFN with the indicated number preceding the reception of the sidelink configured grant configuration Type 1 as reference logical slot. If it is absent, the indicated reference SFN is zero.

[0076] The RRC configures the following parameters when the configured grant Type 2 is configured, as specified in 3GPP TS 38.331:

• sl-ConfiglndexCG'. the identifier of a configured grant for sidelink;

• sl-CS-RNTI: SLCS-RNTI for activation, deactivation, and retransmission;

• sl-NrOfHARQ-Processes'. the number of HARQ processes for configured grant;

• sl-PeriodCG'. periodicity of the configured grant Type 2;

• sl-CG-MaxTransNumList. the maximum number of times that a TB can be transmitted using the configured grant;

• sl-HARQ-ProcID-offset. offset of HARQ process for configured grant Type 2.

[0077] Upon configuration of a configured grant Type 1, the MAC entity shall, for each configured sidelink grant, store the sidelink grant provided by RRC as a configured sidelink grant and initialize or re- initialize the configured sidelink grant to determine physical sidelink control channel (PSCCH) duration(s) and physical sidelink shared channel (PSSCH) duration(s) according to sl- TimeOffsetCG-Type1 and sl-TimeResourceCG-Type 1 , and to reoccur with sl-periodCG for transmissions of multiple MAC PDUs according to clause 8.1.2 of 3GPP TS 38.214. Note that if the MAC entity is configured with multiple configured sidelink grants, collision among the configured sidelink grants may occur. How to handle the collision is left to UE implementation.

[0078] After a sidelink grant is configured for a configured grant Type 1, the MAC entity shall consider sequentially that the first slot of the S ^th sidelink grant occurs in the logical slot for which: where CURRENT slot refers to current logical slot in the associated resource pool, is the number of slots that belongs to the associated resource pool as defined in clause 8 of 3GPP TS 38.214. sl-ReferenceSlotCG-Type 1 refers to reference logical slot defined by sl-TimeReferenceSFN-Type1

[0079] After a sidelink grant is configured for a configured grant Type 2, the MAC entity shall consider sequentially that the first slot of S ^th sidelink grant occurs in the logical slot for which: where sl-StartSlotCG- Type2 refers to the logical slot of the first transmission opportunity of PSSCH where the configured sidelink grant was (re) initialized.

[0080] When a configured sidelink grant is released by RRC, all the corresponding configurations shall be released and all corresponding sidelink grants shall be cleared. The MAC entity shall: if the configured sidelink grant confirmation has been triggered and not cancelled; and if the MAC entity has UL resources allocated for new transmission: instruct the Multiplexing and Assembly procedure to generate a Sidelink Configured Grant Confirmation MAC CE as defined in clause TS 38.321 (clause 6.1.3.34) of 3GPP; cancel the triggered configured sidelink grant confirmation. For a configured grant Type 2, the MAC entity shall clear the corresponding configured sidelink grant immediately after first transmission of Sidelink Configured Grant Confirmation MAC CE triggered by the configured sidelink grant deactivation.

[0081] Integrity and Reliability of the positioning estimate is defined by the parameters Alert limit (AL), Time to alert (TTA), and Target Integrity Risk (TIR). The Alert limit (AL) is the maximum allowable positioning error such that the positioning system is available for the intended application. If the positioning error is beyond the AL, operations are hazardous and the positioning system should be declared unavailable for the intended application to prevent loss of integrity. Note that when the AL bounds the positioning error in the horizontal plane or on the vertical axis then it is called Horizontal Alert Limit (HAL) or Vertical Alert Limit (VAL) respectively. The time to alert (TTA) is the probability that the positioning error exceeds the Alert Limit (AL) without warning the user within the required Time-to- Alert (TTA). Note that the TIR is usually defined as a probability rate per some time unit (e.g. per hour, per second or per independent sample). The Target Integrity Risk (HR) is the maximum allowable elapsed time from when the positioning error exceeds the Alert Limit (AL) until the function providing position integrity annunciates a corresponding alert.

[0082] A UE (an initiating UE) may be allocated SL resources semi-persistently by way of a SL configured grant. Similar to NR Uu there may be two types of configured grants, type 1 and type 2 CG. SL resources are allocated with a given configured periodicity, also referred to as period. Within each period of SL CG up to three CG resources can be allocated by the base station (e.g., gNB). The HARQ process ID for each transmission in a SL resource corresponding to a SL CG is determined based on the formula used for UL configured grants in 3GGP TS 38.321.

[0083] FIG. 9 illustrates an example 900 of a SL CG as related to sidelink positioning frequency layer configuration, as described herein. In the example 900, three CG resources are allocated per period and two HARQ processes are used for the SL configured grant. After each CG resource a physical sidelink feedback channel (PSFCH) is allocated for the transmission of HARQ feedback from the responder (e.g., receiving) UE. After the last CG resource within a period physical uplink control channel (PUCCH) resources are allocated in order to send HARQ feedback information to the base station (e.g., gNB) indicating whether the transmission was successful or not.

[0084] Returning to FIG. 1 , group member discovery is applicable to, for example, public safety use and commercial services. To perform group member discovery, the UE 104 is configured with the related information as described in TS 23.303 (clause 5.2). Group member discovery is a form of restricted discovery in that only users that are affiliated with each other can discover each other (e.g., only users sharing the same application layer group ID). In the case of public safety use, the ProSe Restricted Code is not used for group member discovery, and pre- configured or provisioned information for the discovery procedures as defined in clause 5.2 is used. Note that the group member discovery performed by the application layer in coordination with an application server is out of scope of this discussion. Both Model A and Model B discovery are supported. Model A discovery uses a single discovery protocol message (announcement). Model B discovery uses two discovery protocol messages (solicitation and response).

[0085] FIG. 10 illustrates an example 1000 of a group member discovery with Model A procedure as related to sidelink positioning frequency layer configuration, as described herein. In the example 1000, an announcing UE 1002 as well as a monitoring UE 1004, a monitoring UE 1006, and a monitoring UE 1008 are illustrated. Although three monitoring UEs are illustrated, it is to be appreciated that there can be any number of monitoring UEs. The announcing UE 1002 sends a group member discovery announcement message 1010, which is received by each of the monitoring UEs 1004, 1006, and 1008. The group member discovery announcement message 1010 includes the type of discovery message, announcer information and application layer group ID (e.g., as discussed in clause 5.8.1). The Destination Layer-2 ID and Source Layer-2 ID used to send the group member discovery announcement message 1010 are specified in clause 5.8.1.2 and clause 5.8.1.3. The monitoring UE determines the Destination Layer-2 ID for signaling reception as specified in clause 5.8.1.2. Note that the announcing UE 1002 may send multiple group member discovery announcement messages in accordance with Model A if the announcing UE 1002 belongs to more than one discovery group.

[0086] FIG. 11 illustrates an example 1100 of a group member discovery with Model B procedure as related to sidelink positioning frequency layer configuration, as described herein. In the example 1100, a discoverer UE 1102 as well as a discoveree UE 1104, a discoveree UE 1106, and a discoveree UE 1108 are illustrated. Although three discoveree UEs are illustrated, it is to be appreciated that there can be any number of discoveree UEs. The discoverer UE 1102 sends a group member discovery solicitation message 1110. The group member discovery solicitation message 1110 includes the type of discovery message, discoverer information, application layer group ID and optionally target information (e.g., as discussed in clause 5.8.1). The Destination Layer-2 ID and Source Layer-2 ID used to send the group member discovery solicitation message 1110 are specified in clause 5.8.1.2 and clause 5.8.1.3. How the discoveree UE determines the Destination Layer-2 ID for signaling reception is specified in clause 5.8.1.2.

[0087] FIG. 11 illustrates an example 1100 of a group member discovery with Model B procedure as related to sidelink positioning frequency layer configuration as described herein. In the example 1100, a discoverer UE 1102 as well as a discoveree UE 1104, a discoveree UE 1106, and a discoveree UE 1108 are illustrated. Although three discoveree UEs are illustrated, it is to be appreciated that there can be any number of discoveree UEs. The discoverer UE 1102 sends a group member discovery solicitation message 1110. The group member discovery solicitation message 1110 includes the type of discovery message, discoverer information, application layer group ID and optionally target information (e.g., as discussed in clause 5.8.1). The Destination Layer-2 ID and Source Layer-2 ID used to send the group member discovery solicitation message 1110 are specified in clause 5.8.1.2 and clause 5.8.1.3. How the discoveree UE determines the Destination Layer-2 ID for signaling reception is specified in clause 5.8.1.2.

[0088] Aspects of the present disclosure include solutions for sidelink positioning frequency layer configuration, which includes the configuration of sidelink PFL and configuring sidelink PRS resources using different hierarchical parameters, such as sidelink PFL, sidelink BWP, resource pools, and resource sets. In implementations, an initiating device initiates a sidelink positioning and/or ranging session, and one or more responding devices respond to a sidelink positioning and/or ranging session from the initiating device. As described herein, a positioning-related reference signal may be referred to as a reference signal used for positioning procedures and/or purposes in order to estimate a target-UE’s location, such as based on PRS, or based on existing reference signals, such as channel state information reference signal (CSI-RS) or sounding reference signal (SRS). In implementations, the term ‘PRS’ may refer to any signal such as a reference signal, which may or may not be used primarily for positioning. A target-UE may be referred to as the device or network entity to be localized or positioned, or as a UE of interest having a position (absolute or relative) to be obtained by the network or by the UE itself.

[0089] The described techniques enable sidelink PRS bandwidth configuration. A UE can receive a configuration for sidelink PFL and correspondingly, the location (e.g., as related to time/frequency resource, time domain bitmap, period) of the sidelink PFL can be semi-statically configured from a network node, or pre- configured. The sidelink PRS positioning frequency layer can be configured with parameters that include subcarrier spacing (SCS), the cyclic prefix, a same center frequency, and configured sidelink bandwidth, and the reference point-A and sidelink PRS positioning frequency layer may define multiple sidelink PRS resource sets.

[0090] In implementations, there are different ways to configure a sidelink PRS resource set, positioning frequency layer, positioning resource pool, BWP, and sidelink carrier. In a first described implementation, one or more sidelink PFL can be defined within a sidelink carrier, and the sidelink positioning frequency layer may be shared with sidelink BWP containing sidelink data communication. The sidelink PFL for positioning and sidelink BWP for data may be configure or pre-configured to have same numerology to avoid switching gaps. The sidelink PFL may partially or fully overlap with Uu interface PFL, or may be confined within Uu interface PFL, and may share the same numerology (including for SCS, the cyclic prefix, a same center frequency, a configured sidelink bandwidth, and the reference point-A) to avoid any switching gaps. A time/frequency multiplexing between sidelink PFL and sidelink BWP maybe defined using a bitmap of sidelink slots and period. Within a sidelink PFL, subchannels can be configured to transmit physical sidelink control channel (PSCCH) and/or second sidelink control information (SCI) using PSCCH or physical sidelink shared channel (PSSCH). The PSCCH resource, such as starting physical resource block (PRB) and PRB length, can be configured as part of the sidelink PFL configuration, and a plurality of sidelink positioning resource sets maybe defined within sidelink PFL.

[0091] In a second described implementation, one or more sidelink PFL may be configured or pre-configured in a sidelink BWP, and sidelink PFL identifier(s) can be configured to distinguish further. The sidelink PFL may replace resource pool configuration for sidelink positioning. A time/frequency division multiplexing scheme can be used to multiplex sidelink PFL and sidelink data resource pools, and a plurality of sidelink positioning resource sets maybe defined within sidelink PFL. In a third described implementation, a separate sidelink BWP may be defined for sidelink positioning, which may be configured within a sidelink carrier. One or more sidelink PFL may be configured or pre-configured in a sidelink BWP. The sidelink BWP for positioning and sidelink BWP for data may fully or partially overlap, and can be defined using a bitmap of sidelink slots and period.

[0092] In a fourth described implementation, one or more positioning resource pools may be configured within a PFL or BWP, which in combination, can be defined together with other options. The positioning resource pool and the data resource pool may be multiplexed in time/frequency domain using a bitmap of sidelink slots and period. In a fifth described implementation, one or more positioning resource sets may be configured within a PFL, BWP, or positioning resource pool, which in combination can be defined together with the above options. The positioning resource set and the data resource pool may be multiplexed in time/frequency domain using a bitmap of sidelink slots and period. [0093] FIG. 12 illustrates an example 1200 of a sidelink PFL and resource pool overlap that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. A plurality of positioning resources maybe defined within the positioning resource set. Alternatively, a positioning resource may be defined within a sidelink configured grant (CG) configuration defined for sidelink positioning.

[0094] FIG. 13 illustrates an example 1300 of a sidelink PFL located within the sidelink carrier that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. A data resource pool for transmitting and/or receiving measurement reports and other positioning configurations may be configured or pre- configured, while the corresponding resource pool identifier may be provided with the sidelink PFL configuration. A time domain bitmap with sidelink slots containing sidelink PFL and sidelink BWP for data, or a sidelink resource pool for data, may be defined as shown in the example 1300.

[0095] FIG. 14 illustrates an example 1400 of PRS configuration levels as related to sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The configuration levels can include at the cell level (e.g., PFL level), at the TRP level, at the resource set level, and/or for each TRP associated with a resource.

[0096] FIG. 15 illustrates an example 1500 of a sidelink PRS hierarchical structure in a first implementation that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. In aspects of sidelink positioning frequency layer configuration, the configuring of a sidelink PRS resource using hierarchical relationship options using sidelink PFL, sidelink BWP, positioning resource pools and resource sets, and PRS resources for multiple destination devices, such as receiving UEs, responder UEs, and anchor UEs may be defined according to the periodic, aperiodic, and/or semi-persistent PRS transmission. The sidelink PRS time- frequency resources can be arranged in a structural manner for easier measurement and reporting, and FIGs. 15- 17 illustrate different options in which the sidelink PRS resources may be structured and signaled. In this example 1500, each sidelink PFL 1502 may include of a set of sidelink positioning resource pools (PRPs) 1504, where each sidelink PRP includes a set of sidelink PRSs 1506, and each sidelink PRS includes a set of sidelink positioning resources 1508. [0097] FIG. 16 illustrates an example 1600 of a sidelink PRS hierarchical structure in a second implementation that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. In this example 1600, each sidelink PFL 1602 includes of a set of SL BWPs 1604, where each sidelink BWP includes a set of sidelink PRPs 1606. Each sidelink PRP may include a set of sidelink PRSsl608, and each sidelink PRS includes a set of sidelink positioning resources 1610.

[0098] FIG. 17 illustrates an example 1700 of a sidelink PRS hierarchical structure in a third implementation that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. In this example 1700, each sidelink BWP 1702 can include of a set of sidelink PFLs 1704, where each sidelink PFL includes a set of sidelink PRSs 1706, and each sidelink PRS may include a set of sidelink positioning resources 1708.

[0099] In alternate implementations, the sidelink BWP may correspond to a common sidelink BWP to be shared for both sidelink positioning and sidelink data, while in another implementation, separate sidelink BWPs may be defined for sidelink positioning. Each of the hierarchical layers shown in examples 1500, 1600, and 1700 may associated with an identifier (ID), which may be signaled along with the PRS resources to identify each of hierarchical layers of the sidelink PRS resource structure. Each of the resources may also vary from transmission-reception point (at the cell level), and the following Table T7 illustrates optional additional parameters that may also be signaled to uniquely identify an individual sidelink PRS resource. This may be signaled from a plurality of devices including a base station, roadside unit, anchor device, initiating device, responding device, and the like.

[0100] Table T7: Additional parameters may be associated to a sidelink PRS resource.

[0101] In an implementation, the sidelink PRPs described above may also correspond to sidelink data resource pools in the event that the PRS is multiplexed with data. In an alternative implementation, the sidelink resource pool may include two fully or partially overlapping resource pools comprising a positioning resource pool and a data resource pool. In another implementation, the sidelink PRS resources may also be measured outside of a sidelink BWP to provide the resources and maintain the same numerology, CP, etc.

[0102] FIG. 18 illustrates an example 1800 of a PRS hierarchical relationship that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. In this example 1800, a sidelink PFL 1802 may include of a set of sidelink PRPs 1804, where each sidelink PRP includes a set of sidelink PRSs 1806, and each sidelink PRS includes a set of sidelink positioning resources 1808 (resource identifiers).

[0103] FIG. 19 illustrates an example 1900 of a PRS hierarchical relationship that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. In this example 1900, a sidelink PFL 1902 may include of a set of sidelink PRSs 1904, and each sidelink PRS includes a set of sidelink positioning resources 1906 (resource identifiers).

[0104] FIG. 20 illustrates an example 2000 of a PRS hierarchical relationship that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. In this example 2000, a sidelink BWP 2002 may include a set of sidelink PFLs 2004, where each sidelink PFL may include of a set of sidelink PRSs 2006, and each sidelink PRS includes a set of sidelink positioning resources 2008 (resource identifiers).

[0105] In an implementation, one or more sidelink PFL configurations can be provided by the LMF and/or LTE positioning protocol (LPP) using the higher layer parameter NR-SL- along with a sidelink PRP positioning resource set and a plurality of associated PRS resource ids. However, a gNB could activate the PRS resource id within the positioning resource set using a medium access control element (MAC CE).

[0106] In another implementation, one or more sidelink PFL or PRP could be signaled by radio resource control (RRC) common signaling, and then a plurality of positioning resource sets associated within PFL could be configured as part of the sidelink PFL configuration. Exemplary RRC common signaling may include the RRCReconfiguration message, positioning and/or V2X system information broadcast signaling, and/or the like. However, a gNB could activate the PRS resource id within the positioning resource set using MAC CE. In another implementation, a UE can perform sensing (i.e., by monitoring SCI transmission from other UEs) on the plurality of positioning resources configured in a PRP or sidelink PFL (as described above) and select the resource within or below a certain reference signal received power (RSRP) threshold for sidelink PRS transmission. In another implementation, other RSS metrics may also be used against a pre-defined or configured threshold, including received signal strength indicator (RS SI), reference signal received quality (RSRQ), or the like. A mode 2 higher layer parameter may provide the positioning resource set for the candidate resource selection procedure, and the UE may choose the positioning resource within the positioning resource set according to the RSRP value.

FIG. 21 illustrates an example of a block diagram 2100 of a device 2102 that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The device 2102 may be an example of an initiating device, a UE 104, gNB, base station 102, or other sidelink-enabled device as described herein. The device 2102 may support wireless communication and/or network signaling with one or more base stations 102, other UEs 104, network entities and devices, or any combination thereof. The device 2102 may include components for bi-directional communications including components for transmitting and receiving communications, such as a positioning manager 2104, a processor 2106, a memory 2108, a receiver 2110, a transmitter 2112, and an I/O controller 2114. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0107] The positioning manager 2104, the receiver 2110, the transmitter 2112, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the positioning manager 2104, the receiver 2110, the transmitter 2112, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0108] In some implementations, the positioning manager 2104, the receiver 2110, the transmitter 2112, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 2106 and the memory 2108 coupled with the processor 2106 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 2106, instructions stored in the memory 2108).

[0109] Additionally or alternatively, in some implementations, the positioning manager 2104, the receiver 2110, the transmitter 2112, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 2106. If implemented in code executed by the processor 2106, the functions of the positioning manager 2104, the receiver 2110, the transmitter 2112, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0110] In some implementations, the positioning manager 2104 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 2110, the transmitter 2112, or both. For example, the positioning manager 2104 may receive information from the receiver 2110, send information to the transmitter 2112, or be integrated in combination with the receiver 2110, the transmitter 2112, or both to receive information, transmit information, or perform various other operations as described herein. Although the positioning manager 2104 is illustrated as a separate component, in some implementations, one or more functions described with reference to the positioning manager 2104 may be supported by or performed by the processor 2106, the memory 2108, or any combination thereof. For example, the memory 2108 may store code, which may include instructions executable by the processor 2106 to cause the device 2102 to perform various aspects of the present disclosure as described herein, or the processor 2106 and the memory 2108 may be otherwise configured to perform or support such operations.

[0111] For example, the positioning manager 2104 may support wireless communication and/or network signaling at a device (e.g., the initiating device 2102, a UE, a gNB, a base station, or other sidelink-enabled device) in accordance with examples as disclosed herein. The positioning manager 2104 and/or other device components may be configured as or otherwise support an apparatus, such as an initiating device, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: configure a sidelink positioning reference signal (PRS) configuration indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration; and transmit the sidelink PRS configuration to one or more receiving devices that utilize the hierarchal resource relationship of the sidelink positioning resource parameters to determine at least one PRS resource for sidelink PRS transmission.

[0112] Additionally, the apparatus (e.g., the initiating device 2102) includes any one or combination of: the sidelink positioning resource parameters of the sidelink PRS configuration comprise one or more of a sidelink positioning frequency layer (PFL), a sidelink bandwidth part (BWP), a sidelink positioning resource pool (PRP), or a sidelink positioning resource set (PRS). The hierarchal resource relationship is configured as the sidelink PFL defined within a sidelink carrier and one or more sidelink PRSs are defined within the sidelink PFL. The hierarchal resource relationship is configured as the sidelink PFL defined within the sidelink BWP and one or more of sidelink PRSs are defined within the sidelink PFL. The hierarchal resource relationship is configured as the sidelink PRP defined within one of the sidelink BWP or the sidelink PFL, and one or more sidelink PRSs are defined within the sidelink PRP. The hierarchal resource relationship is configured as a time domain bitmap comprising sidelink slots and a time period that define the sidelink PFL within one of a sidelink carrier or the sidelink BWP. The processor and the transceiver are configured to cause the apparatus to transmit the sidelink PRS configuration via a location management function (LMF) utilizing LTE positioning protocol (LPP). The processor and the transceiver are configured to cause the apparatus to transmit the sidelink PRS configuration via a next-generation NodeB (gNB) utilizing radio resource control (RRC).

[0113] The positioning manager 2104 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at an initiating device, including configuring a sidelink positioning reference signal (PRS) configuration indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration; and transmitting the sidelink PRS configuration to one or more receiving devices that utilize the hierarchal resource relationship of the sidelink positioning resource parameters to determine at least one PRS resource for sidelink PRS transmission.

[0114] Additionally, wireless communication and/or network signaling at the initiating device includes any one or combination of: transmitting the sidelink PRS configuration via a location management function (LMF) utilizing LTE positioning protocol (LPP). The method further comprising transmitting the sidelink PRS configuration via a next-generation NodeB (gNB) utilizing radio resource control (RRC). The sidelink positioning resource parameters of the sidelink PRS configuration comprise one or more of a sidelink positioning frequency layer (PFL), a sidelink bandwidth part (BWP), a sidelink positioning resource pool (PRP), or a sidelink positioning resource set (PRS). The hierarchal resource relationship is configured as the sidelink PFL defined within a sidelink carrier and one or more sidelink PRSs are defined within the sidelink PFL. The hierarchal resource relationship is configured as the sidelink PFL defined within the sidelink BWP and one or more of sidelink PRSs are defined within the sidelink PFL. The hierarchal resource relationship is configured as the sidelink PRP defined within one of the sidelink BWP or the sidelink PFL, and one or more sidelink PRSs are defined within the sidelink PRP. The hierarchal resource relationship is configured as a time domain bitmap comprising sidelink slots and a time period that define the sidelink PFL within one of a sidelink carrier or the sidelink BWP.

[0115] The processor 2106 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 2106 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 2106. The processor 2106 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 2108) to cause the device 2102 to perform various functions of the present disclosure.

[0116] The memory 2108 may include random access memory (RAM) and read-only memory (ROM). The memory 2108 may store computer-readable, computer-executable code including instructions that, when executed by the processor 2106 cause the device 2102 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 2106 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 2108 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0117] The I/O controller 2114 may manage input and output signals for the device 2102. The I/O controller 2114 may also manage peripherals not integrated into the device 2102. In some implementations, the I/O controller 2114 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 2114 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 2114 may be implemented as part of a processor, such as the processor 2106. In some implementations, a user may interact with the device 2102 via the I/O controller 2114 or via hardware components controlled by the I/O controller 2114.

[0118] In some implementations, the device 2102 may include a single antenna 2116. However, in some other implementations, the device 2102 may have more than one antenna 2116, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The receiver 2110 and the transmitter 2112 may communicate bi-directionally, via the one or more antennas 2116, wired, or wireless links as described herein. For example, the receiver 2110 and the transmitter 2112 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 2116 for transmission, and to demodulate packets received from the one or more antennas 2116.

[0119] FIG. 22 illustrates an example of a block diagram 2200 of a device 2202 that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The device 2202 may be an example of a receiving device, a UE, a network device, or other sidelink-enabled device as described herein. The device 2202 may support wireless communication and/or network signaling with one or more base stations 102, other UEs 104, core network devices and functions (e.g., core network 106), or any combination thereof. The device 2202 may include components for bi-directional communications including components for transmitting and receiving communications, such as a positioning manager 2204, a processor 2206, a memory 2208, a receiver 2210, a transmitter 2212, and an I/O controller 2214. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0120] The positioning manager 2204, the receiver 2210, the transmitter 2212, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the positioning manager 2204, the receiver 2210, the transmitter 2212, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0121] In some implementations, the positioning manager 2204, the receiver 2210, the transmitter 2212, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 2206 and the memory 2208 coupled with the processor 2206 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 2206, instructions stored in the memory 2208).

[0122] Additionally or alternatively, in some implementations, the positioning manager 2204, the receiver 2210, the transmitter 2212, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 2206. If implemented in code executed by the processor 2206, the functions of the positioning manager 2204, the receiver 2210, the transmitter 2212, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0123] In some implementations, the positioning manager 2204 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 2210, the transmitter 2212, or both. For example, the positioning manager 2204 may receive information from the receiver 2210, send information to the transmitter 2212, or be integrated in combination with the receiver 2210, the transmitter 2212, or both to receive information, transmit information, or perform various other operations as described herein. Although the positioning manager 2204 is illustrated as a separate component, in some implementations, one or more functions described with reference to the positioning manager 2204 may be supported by or performed by the processor 2206, the memory 2208, or any combination thereof. For example, the memory 2208 may store code, which may include instructions executable by the processor 2206 to cause the device 2202 to perform various aspects of the present disclosure as described herein, or the processor 2206 and the memory 2208 may be otherwise configured to perform or support such operations.

[0124] For example, the positioning manager 2204 may support wireless communication and/or network signaling at a device (e.g., the receiving device 2202, a UE, or other sidelink-enabled device) in accordance with examples as disclosed herein. The positioning manager 2204 and/or other device components may be configured as or otherwise support an apparatus, such as a receiving device, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: receive a sidelink positioning reference signal (PRS) configuration indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration; process the hierarchal resource relationship of the sidelink positioning resource parameters to allocate at least one PRS resource for sidelink PRS transmission; and transmit the sidelink PRS transmission based at least in part on the received sidelink PRS configuration.

[0125] Additionally, the apparatus (e.g., a receiving device 2202) includes any one or combination of: the processor and the transceiver are configured to cause the apparatus to process the hierarchal resource relationship of the sidelink positioning resource parameters to determine a configured bandwidth in which sidelink positioning measurements are measured for one of absolute or relative positioning accuracy. The sidelink positioning resource parameters of the sidelink PRS configuration comprise one or more of a sidelink positioning frequency layer (PFL), a sidelink bandwidth part (BWP), a sidelink positioning resource pool (PRP), or a sidelink positioning resource set (PRS). The hierarchal resource relationship is configured as the sidelink PFL defined within a sidelink carrier and one or more sidelink PRSs are defined within the sidelink PFL. The hierarchal resource relationship is configured as the sidelink PFL defined within the sidelink BWP and one or more of sidelink PRSs are defined within the sidelink PFL. The hierarchal resource relationship is configured as the sidelink PRP defined within one of the sidelink BWP or the sidelink PFL, and one or more sidelink PRSs are defined within the sidelink PRP. The hierarchal resource relationship is configured as a time domain bitmap comprising sidelink slots and a time period that define the sidelink PFL within one of a sidelink carrier or the sidelink BWP. The processor and the transceiver are configured to cause the apparatus to receive the sidelink PRS configuration via a location management function (LMF) utilizing LTE positioning protocol (LPP). The processor and the transceiver are configured to cause the apparatus to receive the sidelink PRS configuration via a nextgeneration NodeB (gNB) utilizing radio resource control (RRC).

[0126] The positioning manager 2204 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at a receiving device, including receiving a sidelink positioning reference signal (PRS) configuration indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration; processing the hierarchal resource relationship of the sidelink positioning resource parameters to allocate at least one PRS resource for sidelink PRS transmission; and transmitting the sidelink PRS transmission based at least in part on the received sidelink PRS configuration.

[0127] Additionally, wireless communication at the receiving device includes any one or combination of: processing the hierarchal resource relationship of the sidelink positioning resource parameters to determine a configured bandwidth in which sidelink positioning measurements are measured for one of absolute or relative positioning accuracy. The method further comprising receiving the sidelink PRS configuration via a location management function (LMF) utilizing LTE positioning protocol (LPP). The method further comprising receiving the sidelink PRS configuration via a next-generation NodeB (gNB) utilizing radio resource control (RRC). The sidelink positioning resource parameters of the sidelink PRS configuration comprise one or more of a sidelink positioning frequency layer (PFL), a sidelink bandwidth part (BWP), a sidelink positioning resource pool (PRP), or a sidelink positioning resource set (PRS). The hierarchal resource relationship is configured as the sidelink PFL defined within a sidelink carrier and one or more sidelink PRSs are defined within the sidelink PFL. The hierarchal resource relationship is configured as the sidelink PFL defined within the sidelink BWP and one or more of sidelink PRSs are defined within the sidelink PFL. The hierarchal resource relationship is configured as the sidelink PRP defined within one of the sidelink BWP or the sidelink PFL, and one or more sidelink PRSs are defined within the sidelink PRP. The hierarchal resource relationship is configured as a time domain bitmap comprising sidelink slots and a time period that define the sidelink PFL within one of a sidelink carrier or the sidelink BWP.

[0128] The processor 2206 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 2206 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 2206. The processor 2206 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 2208) to cause the device 2202 to perform various functions of the present disclosure.

[0129] The memory 2208 may include random access memory (RAM) and read-only memory (ROM). The memory 2208 may store computer-readable, computer-executable code including instructions that, when executed by the processor 2206 cause the device 2202 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 2206 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 2208 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0130] The I/O controller 2214 may manage input and output signals for the device 2202. The I/O controller 2214 may also manage peripherals not integrated into the device 2202. In some implementations, the I/O controller 2214 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 2214 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 2214 may be implemented as part of a processor, such as the processor 2206. In some implementations, a user may interact with the device 2202 via the I/O controller 2214 or via hardware components controlled by the I/O controller 2214.

[0131] In some implementations, the device 2202 may include a single antenna 2216. However, in some other implementations, the device 2202 may have more than one antenna 2216, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The receiver 2210 and the transmitter 2212 may communicate bi-directionally, via the one or more antennas 2216, wired, or wireless links as described herein. For example, the receiver 2210 and the transmitter 2212 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 2216 for transmission, and to demodulate packets received from the one or more antennas 2216.

[0132] FIG. 23 illustrates a flowchart of a method 2300 that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The operations of the method 2300 may be implemented and performed by a device or its components, such as an initiating device (e.g., a UE 104, gNB, base station 102, or other sidelink-enabled device) as described with reference to FIGs. 1 through 22. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0133] At 2302, the method may include configuring a sidelink PRS configuration indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration. The sidelink positioning resource parameters of the sidelink PRS configuration can include one or more of a sidelink PFL, a sidelink BWP, a sidelink PRP, or a sidelink PRS. The operations of 2302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2302 may be performed by a device as described with reference to FIG. 1.

[0134] At 2304, the method may include transmitting the sidelink PRS configuration to one or more receiving devices that utilize the hierarchal resource relationship of the sidelink positioning resource parameters to determine at least one PRS resource for sidelink PRS transmission. The operations of 2304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2304 may be performed by a device as described with reference to FIG. 1.

[0135] FIG. 24 illustrates a flowchart of a method 2400 that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The operations of the method 2400 may be implemented and performed by a device or its components, such as an initiating device (e.g., a UE 104, gNB, base station 102, or other sidelink-enabled device) as described with reference to FIGs. 1 through 22. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0136] At 2402, the method may include transmitting the sidelink PRS configuration via a LMF utilizing LTE positioning protocol. The operations of 2402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2402 may be performed by a device as described with reference to FIG. 1.

[0137] At 2404, the method may include transmitting the sidelink PRS configuration via a gNB utilizing RRC. The operations of 2404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2404 may be performed by a device as described with reference to FIG. 1.

[0138] At 2406, the method may include configuring the hierarchal resource relationship as the sidelink PFL defined within a sidelink carrier and one or more sidelink PRSs are defined within the sidelink PFL. The operations of 2406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2406 may be performed by a device as described with reference to FIG. 1.

[0139] At 2408, the method may include configuring the hierarchal resource relationship as the sidelink PFL defined within the sidelink BWP and one or more of sidelink PRSs are defined within the sidelink PFL. The operations of 2408 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2408 may be performed by a device as described with reference to FIG. 1.

[0140] At 2410, the method may include configuring the hierarchal resource relationship as the sidelink PRP defined within one of the sidelink BWP or the sidelink PFL, and one or more sidelink PRSs are defined within the sidelink PRP. The operations of 2410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2410 may be performed by a device as described with reference to FIG. 1.

[0141] At 2412, the method may include configuring the hierarchal resource relationship as a time domain bitmap comprising sidelink slots and a time period that define the sidelink PFL within a sidelink carrier or the sidelink BWP. The operations of 2412 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2412 may be performed by a device as described with reference to FIG. 1.

[0142] FIG. 25 illustrates a flowchart of a method 2500 that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The operations of the method 2500 may be implemented and performed by a device or its components, such as a receiving device (e.g., a UE, a network device, or other sidelink-enabled device) as described with reference to FIGs. 1 through 22. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0143] At 2502, the method may include receiving a sidelink PRS configuration indicating a hierarchal resource relationship of sidelink positioning resource parameters of the sidelink PRS configuration. The sidelink positioning resource parameters of the sidelink PRS configuration comprise one or more of a sidelink PFL, a sidelink BWP, a sidelink PRP, or a sidelink PRS. The operations of 2502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2502 may be performed by a device as described with reference to FIG. 1.

[0144] At 2504, the method may include processing the hierarchal resource relationship of the sidelink positioning resource parameters to allocate at least one PRS resource for sidelink PRS transmission. The operations of 2504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2504 may be performed by a device as described with reference to FIG. 1.

[0145] At 2506, the method may include transmitting the sidelink PRS transmission based on the received sidelink PRS configuration. The operations of 2506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2506 may be performed by a device as described with reference to FIG. 1.

[0146] FIG. 26 illustrates a flowchart of a method 2600 that supports sidelink positioning frequency layer configuration in accordance with aspects of the present disclosure. The operations of the method 2600 may be implemented and performed by a device or its components, such as a receiving device (e.g., a UE, a network device, or other sidelink-enabled device) as described with reference to FIGs. 1 through 22. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0147] At 2602, the method may include processing the hierarchal resource relationship of the sidelink positioning resource parameters to determine a configured bandwidth in which sidelink positioning measurements are measured for absolute or relative positioning accuracy. The operations of 2602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2602 may be performed by a device as described with reference to FIG. 1.

[0148] At 2604, the method may include receiving the sidelink PRS configuration via a LMF utilizing LTE positioning protocol. The operations of 2604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2604 may be performed by a device as described with reference to FIG. 1.

[0149] At 2606, the method may include receiving the sidelink PRS configuration via a gNB utilizing RRC. The operations of 2606 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2606 may be performed by a device as described with reference to FIG. 1.

[0150] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined. The order in which the methods are described is not intended to be construed as a limitation, and any number or combination of the described method operations may be performed in any order to perform a method, or an alternate method.

[0151] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0152] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer- readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0153] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non- transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special- purpose processor.

[0154] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer- readable media.

[0155] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Similarly, a list of one or more of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0156] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described example.

[0157] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.