RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application Serial No. 63/321,898 filed March 21, 2022 entitled “Sidelink Anchor Device Management,” the disclosure of which is incorporated by reference herein in its entirety. This application also claims priority to U.S. Provisional Application Serial No. 63/322,026 filed March 21, 2022 entitled “Sidelink Positioning Reference Unit Management,” 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 anchor device management.

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] The wireless communications system enables UE-assisted and UE-based positioning methods in the third generation partnership project (3 GPP) positioning framework. However, UE-to- UE range and orientation determinations are not supported, which would facilitate relative positioning applications across other services, such as for vehicle-to-everything (V2X), public safety, industrial Internet of things (IIoT), commercial, and other applications. Anchor devices with known and/or fixed locations in time can serve as positioning nodes depending on the type of positioning technique. In a sidelink scenario, the anchor devices may have varying degrees (low, medium, and high degree) of mobility. However, multiple anchor nodes are not currently managed and coordinated in a centralized and decentralized manner for the purposes of sidelink positioning.

SUMMARY

[0005] The present disclosure relates to methods, apparatuses, and systems that support sidelink anchor device management. By utilizing the described techniques, a device implemented as a configuration entity and a sidelink anchor device are operable to implement various aspects of sidelink anchor device management, as described herein. Either of the devices that are implemented as the configuration entity and/or the sidelink anchor device may be implemented in a wireless communications system as a UE, an anchor UE, a base station, a gNB, a roadside unit, 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 anchor device management. For instance, the configuration entity can communicate or transmit a sidelink positioning capability request to one or more potential sidelink anchor devices. The potential sidelink anchor devices receive the sidelink positioning capability request from the configuration entity and can respond with anchor device capability information and a location of each of the respective sidelink anchor devices. The configuration entity can then select at least one of the potential sidelink anchor devices as an anchor device based on the anchor device capability information and the location of the sidelink device. The configuration entity can then transmit a sidelink positioning reference signal transmission configuration to the selected sidelink anchor device, establishing a sidelink positioning session with a target device.

[0006] Aspects of the disclosure are directed to implementations for anchor and reference devices to be registered, identified, and managed based on the type of positioning method applied, as well as the number of positioning nodes involved in a sidelink positioning session, and taking into account the configuration and reporting of anchor devices for in-coverage, partial coverage, and out-of- coverage scenarios. With reference to sidelink positioning, the selection and configuration of the anchor devices is essential to obtain high absolute and relative positioning accuracy. Several aspects of sidelink positioning are different than traditional positioning, such as adjusting for moving and distributed nodes, varying device mobility, the availability of anchor and non-anchor devices, and so on. Anchor devices with known and/or fixed locations in time can serve as positioning nodes depending on the type of sidelink positioning technique. In a sidelink scenario, it can be expected that the anchor devices may have varying degrees of mobility (e.g., low, medium, and high degrees of mobility). Current traditional positioning techniques do not a provide a mechanism to manage and coordinate multiple anchor nodes in a centralized and decentralized manner for the purposes of sidelink positioning.

[0007] Some implementations of the method and apparatuses described herein may include wireless communication at a device (e.g., a configuration entity), such as a UE, an anchor UE, a base station, a gNB, a roadside unit, or a location server. The device implemented as a configuration entity can transmit a sidelink positioning capability request to one or more sidelink devices as potential sidelink anchor devices. The configuration entity may then receive, from one or more of the sidelink devices, anchor device capability information and a location of each of the respective one or more sidelink devices. The configuration entity can select at least one of the sidelink devices as an anchor device based on the anchor device capability information and the location of the sidelink device. The configuration entity can then transmit a sidelink positioning reference signal transmission configuration to the anchor device, establishing a sidelink positioning session with a target device.

[0008] In some implementations of the method and apparatuses described herein, the device implemented as the configuration entity can select the sidelink device as the anchor device based on a sidelink line-of-sight link quality between the configuration entity and the selected sidelink device, based on a sidelink communication range of the selected sidelink device to the configuration entity, and/or based on a sidelink measurement quality. The configuration entity can receive, from the selected sidelink device, sidelink measurements and the location of the sidelink device, and select the sidelink device as the anchor device based on the sidelink measurements and the location. The configuration entity can also receive, from the anchor device, a status indication that indicates the anchor device is operably configured as the anchor device, or is no longer operable as the anchor device. The configuration entity can receive, from a network device, a candidate list of the potential sidelink anchor devices, and select the anchor device based on a link quality between each of the potential sidelink anchor devices, and/or based on a coverage area of each of the potential sidelink anchor devices. The configuration entity may be implemented as a user equipment (UE), and the anchor device is configured according to a UE-based UE-configured anchor device configuration, a UE-based network-configured anchor device configuration, a UE-assisted UE-configured anchor device configuration, or a UE-assisted network-configured anchor device configuration.

[0009] Some implementations of the method and apparatuses described herein may include wireless communication at a device (e.g., a sidelink anchor device), and the anchor device receives, from a configuration device, a sidelink positioning capability request. The anchor device can then transmit, to the configuration device, anchor device capability information and a location of the anchor device. The anchor device can also receive, as a selected anchor device based on the anchor device capability information and the location of the anchor device, a sidelink positioning reference signal transmission configuration establishing a sidelink positioning session with one or more target devices.

[0010] In some implementations of the method and apparatuses described herein, the sidelink anchor device may be selected based on a sidelink line-of-sight link quality between the apparatus (e.g., sidelink anchor device) and the one or more target devices, based on a sidelink communication range of the apparatus to the one or more target devices, and/or based on a sidelink measurement quality. The anchor device can transmit a sidelink positioning reference signal to the target devices based on the location and mobility of the anchor device. The anchor device can determine a location estimation of the configuration device. The anchor device can also transmit sidelink positioning configuration information to the target devices participating in the sidelink positioning session, as well as transmit the anchor device capability information and the location of the anchor device to the target devices participating in the sidelink positioning session. The anchor device can transmit pre- defined assistance information to the target devices participating in the sidelink positioning session. The anchor device can also transmit, to the configuration device, a status indication that the anchor device is operably configured as the anchor device, or is no longer operable as the anchor device, and may transmit time difference information with respect to itself and one or more additional anchor devices.

[0011] In implementations, the anchor device can be configured according to a UE-based UE- configured anchor device configuration, a UE-based network-configured anchor device configuration, a UE-assisted UE-configured anchor device configuration, or a UE-assisted network- configured anchor device configuration. The anchor device can include an anchor device identifier (ID) that is a layer one ID (LI -ID) derived from a layer two ID (L2-ID), a self-generated ID, or an application ID generated by a sidelink positioning application of the apparatus, and the anchor device can transmit, to the configuration device, the anchor device ID with the anchor device capability information and the location of the apparatus.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Various aspects of the present disclosure for sidelink anchor device management 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 anchor device management in accordance with aspects of the present disclosure.

[0014] FIG. 2 illustrates an example of absolute and relative positioning scenarios as related to sidelink anchor device management in accordance with aspects of the present disclosure.

[0015] FIG. 3 illustrates an example of a multi-cell RTT procedure as related to sidelink anchor device management in accordance with aspects of the present disclosure.

[0016] FIG. 4 illustrates an example of a system for existing relative range estimation as related to sidelink anchor device management in accordance with aspects of the present disclosure. [0017] FIG. 5 illustrates an example of a system for NR beam-based positioning as related to sidelink anchor device management in accordance with aspects of the present disclosure.

[0018] FIG. 6 illustrates an example of an LTE positioning protocol (LPP) request location information message as related to sidelink anchor device management in accordance with aspects of the present disclosure.

[0019] FIG. 7 illustrates an example of a LPP provide location information message as related to sidelink anchor device management in accordance with aspects of the present disclosure.

[0020] FIG. 8 illustrates an example of sidelink anchor devices identification with respect to a target device, which supports sidelink anchor device management in accordance with aspects of the present disclosure.

[0021] FIG. 9 illustrates an example of an implementation for signaling sidelink real time difference (RTD) information, which supports sidelink anchor device management in accordance with aspects of the present disclosure.

[0022] FIG. 10 illustrates an example of anchor device capability exchange that supports sidelink anchor device management in accordance with aspects of the present disclosure.

[0023] FIG. 11 illustrates an example of anchor device capability exchange that supports sidelink anchor device management in accordance with aspects of the present disclosure.

[0024] FIG. 12 illustrates an example of SL timing error corrections using SL PRU as related to sidelink positioning reference unit management.

[0025] FIG. 13 illustrates an example of a type of request and response signaling exchange for reference measurements between a configuration entity or positioning calculation entity and a SL PRU as related to sidelink positioning reference unit management.

[0026] FIG. 14 illustrates an example of another type of request and response signaling exchange for reference measurements between a configuration entity or positioning calculation entity and a SL PRU as related to sidelink positioning reference unit management.

[0027] FIG. 15 illustrates an example of a type of capability exchange for a SL positioning reference unit as related to sidelink positioning reference unit management. [0028] FIG. 16 illustrates an example of another type of capability exchange for a SL positioning reference unit as related to sidelink positioning reference unit management.

[0029] FIG. 17 illustrates an example block diagram of components of a device (e.g., a configuration entity) that supports sidelink anchor device management in accordance with aspects of the present disclosure.

[0030] FIG. 18 illustrates an example block diagram of components of a device (e.g., a sidelink anchor device) that supports sidelink anchor device management in accordance with aspects of the present disclosure.

[0031] FIGs. 19-22 illustrate flowcharts of methods that support sidelink anchor device management in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0032] Implementations of sidelink anchor device management are described, such as related to anchor and reference devices being registered, identified, and managed based on the type of positioning method applied, as well as the number of positioning nodes involved in a sidelink positioning session, and taking into account the configuration and reporting of anchor devices for incoverage, partial coverage, and out-of-coverage scenarios. With reference to sidelink positioning, the selection and configuration of the anchor devices is essential to obtain high absolute and relative positioning accuracy. Aspects of the disclosure include implementations to identify, select, and configure an anchor device for multiple, different sidelink positioning methods. Additionally, the disclosure provides techniques to coordinate and manage multiple anchor devices including reference anchor devices using layer 1 and layer 2 identifiers. The disclosure also provides techniques for sidelink anchor device reporting including the signaling of real time difference information to assist in improved absolute and/or relative location estimation accuracy. Further, the disclosure provides to support anchor device capability exchange with other UEs, devices, and network entities via sidelink (PC5 interface), including the content of anchor device capability information.

[0033] Typically, the conventional system supports UE-assisted and UE-based positioning methods in the 3 GPP positioning framework. However, UE-to-UE range and orientation determinations are not supported, which would facilitate relative positioning applications across other services, such as for vehicle-to-everything (V2X), public safety, industrial Internet of things (IIoT), commercial, and other applications. For the described sidelink anchor device management, timely and accurate measurements are essential to obtain high absolute and relative positioning accuracy. Anchor devices with known and/or fixed locations in time can serve as positioning nodes depending on the type of positioning technique. In a sidelink scenario, the anchor devices may have varying degrees (low, medium, and high degree) of mobility. However, multiple anchor nodes are not currently managed and coordinated in a centralized and decentralized manner for the purposes of sidelink positioning.

[0034] Unlike traditional positioning, the described sidelink anchor device management provides techniques for the identification, selection, and configuration of a sidelink anchor device with predefined selection criteria to assist a network entity and/or sidelink positioning UE to define candidate anchor devices. In implementations, anchor device ID management is described in the context of layer 1 and layer 2 IDs. In another implementation, the reporting content and procedures for anchor devices are also outlined. Further, capability information exchange information and signaling with other devices and network entities is implemented. In implementations, sidelink anchor device reporting includes the signaling of real time difference information to assist in improved absolute and relative location estimation accuracy. Additionally, support for anchor device capability exchange with other UEs, devices, and network entities via sidelink (PC5 interface), including content of anchor device capability information is described.

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

[0036] FIG. 1 illustrates an example of a wireless communications system 100 that supports sidelink anchor device management 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.

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

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

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

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

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

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

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

[0044] According to implementations, one or more of a device 116 (e.g., implemented as a configuration entity) and a sidelink anchor device 118 are operable to implement various aspects of sidelink anchor device management, as described herein. Either of the device 116 (e.g., the configuration entity) and/or the sidelink anchor device 118 may be implemented in the wireless communications system 100 as a UE 104, an anchor UE, a base station 102, a gNB, a roadside unit, 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 anchor device management. For instance, the device 116 (e.g., the configuration entity) can communicate or transmit a sidelink positioning capability request 120 to one or more potential sidelink anchor devices 118 via a sidelink communication link 112. The sidelink anchor devices 118 receive the sidelink positioning capability request 120 from the device 116 and can respond with anchor device capability information and a location 122 of each of the respective sidelink anchor devices. Accordingly, the device 116 (e.g., the configuration entity) can then select at least one of the potential sidelink anchor devices 118 as an anchor device based on the anchor device capability information and the location of the sidelink devices. The device 116 (e.g., the configuration entity) can then transmit a sidelink positioning reference signal transmission configuration to the selected sidelink anchor device, establishing a sidelink positioning session with a target device. [0045] According to implementations, one or more SL PRUs and configuration entities are operable to implement various aspects of sidelink positioning reference unit management. For instance, a SL PRU receives a SL positioning reference management configuration, performs SL positioning measuring to collect SL positioning reference measurements that are transmitted to the configuring entity or to a position calculation entity. The SL PRU refers to any device that can perform or collect SL positioning reference measurements, such as a UE 104 or a roadside unit. The configuration entity refers to any device that can transmit a measurement configuration to perform or collect SL positioning measurement measurements, such as a UE 104, a roadside unit, a base station 102, or a location server (or position calculation entity). The position calculation entity refers to any device that can transmit a measurement configuration to perform or collect SL positioning measurement measurements, such as a UE 104, a base station 102, or a location server.

[0046] With reference to new radio (NR) positioning based on NR Uu signals and SA architecture

(e.g., beam-based transmissions), the target use cases also include commercial and regulatory (emergency services) scenarios. The 3 GPP (release 17) defines the positioning performance requirements for commercial and IIoT use cases. For example, the positioning error requirement for end-to-end latency for a position estimate of a UE in a commercial use case is less than 100 ms, and in an IIoT use case is less than 100 ms, within the order of 10 ms being desired. However, these positioning performance requirements do not address sidelink anchor device management.

[0047] The supported positioning techniques (release 16) are listed below in Table Tl, and separate positioning techniques can be currently configured and performed based on the requirements of the location management function (LMF) and UE capabilities. The transmission of positioning reference signals (PRSs) 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. [0048] Table T1 : Supported Rel-16 UE Positioning Methods

[0049] FIG. 2 illustrates an example 200 of absolute and relative positioning scenarios as related to sidelink anchor device management in accordance with aspects of the present disclosure. The network devices described with reference to example 200 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 200 is an overview of absolute and relative positioning scenarios as defined in the architectural (stage 1) specifications using three different co-ordinate systems, including (III) a conventional absolute positioning, fixed coordinate system at 202; (II) a relative positioning, variable and moving coordinate system at 204; and (I) a relative positioning, variable coordinate system at 206. Notably, the relative positioning, variable coordinate system at 206 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 200 also includes a scenario 208 for an out of coverage area in which UEs need to determine relative position with respect to each other. [0050] 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 NG-RAN node assisted. The RAT-dependent positioning techniques that are supported include downlink-time difference of arrival (DL-TDOA), downlink-angle of departure (DL-AoD), multi-round trip time (multi -RTT), new radio enhanced cell-ID (NRE-CID); uplink-time difference of arrival (UL-TDOA); and uplink-angle of arrival (UL-AoA). With reference to the 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.

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

[0052] FIG. 3 illustrates an example 300 of a multi-cell RTT procedure as related to sidelink anchor device management 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 T1.

[0053] FIG. 4 illustrates an example of a system 400 for existing relative range estimation as related to sidelink anchor device management in accordance with aspects of the present disclosure. The system 400 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.

[0054] 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 NR enhanced cell-ID (E-CID) positioning may utilize some of the same measurements as the measurement control system in the radio resource control (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).

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

[0056] FIG. 5 illustrates an example of a system 500 for NR beam-based positioning as related to sidelink anchor device management in accordance with aspects of the present disclosure. The system 500 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 500, which is relatively different when compared to LIE where the PRS was transmitted across the whole cell. The PRS can be locally associated with a PRS Resource ID and Resource Set ID for a base station (TRP). Similarly, UE positioning measurements such as Reference Signal Time Difference (RSTD) and PRS RSRP measurements are made between beams (e.g., between a different pair of DL PRS resources or DL PRS resource sets) as opposed to different cells as was the case in LTE. In addition, there are additional UL positioning methods for the network to exploit in order to compute the target UE’s location.

[0057] The Tables T2 and T3 show the reference signal to measurements mapping for each of the supported RAT-dependent positioning techniques at the UE and gNB, respectively.

[0058] Table T2: UE measurements to enable RAT-dependent positioning techniques. [0059] Table T3: gNB measurements to enable RAT-dependent positioning techniques.

[0060] 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 GNSS, IMU sensor, WLAN, and Bluetooth technologies for performing target device (UE) positioning. Network-assisted GNSS methods make use of UEs that are equipped with radio receivers capable of receiving GNSS signals. In 3GPP specifications the term GNSS encompasses both global and regional/augmentation navigation satellite systems. Examples of global navigation satellite systems include GPS, Modernized GPS, Galileo, GLONASS, and BeiDou Navigation Satellite System (BDS). Regional navigation satellite systems include Quasi Zenith Satellite System (QZSS) while the many augmentation systems, are classified under the generic term of Space Based Augmentation Systems (SB AS) and provide regional augmentation services. Different GNSSs (e.g. GPS, Galileo, etc.) can be used separately or in combination to determine the location of a UE.

[0061] Barometric pressure sensor positioning makes use of barometric sensors to determine the vertical component of the position of the UE. The UE measures barometric pressure, optionally aided by assistance data, to calculate the vertical component of its location or to send measurements to the positioning server for position calculation. This method can be combined with other positioning methods to determine the 3D position of the UE. WLAN positioning makes use of the WLAN measurements (access point (AP) identifiers and optionally other measurements) and databases to determine the location of the UE. The UE measures received signals from WLAN access points, optionally aided by assistance data, to send measurements to the positioning server for position calculation. Using the measurement results and a references database, the location of the UE is calculated. Additionally or alternatively, the UE makes use of WLAN measurements and optionally WLAN AP assistance data provided by the positioning server, to determine its location.

[0062] Bluetooth positioning makes use of Bluetooth measurements (beacon identifiers and optionally other measurements) to determine the location of the UE. The UE measures received signals from Bluetooth beacons. Using the measurement results and a references database, the location of the UE 104 is calculated. The Bluetooth methods may be combined with other positioning methods (e.g., WLAN) to improve positioning accuracy of the UE. TBS positioning consists of a network of ground-based transmitters, broadcasting signals only for positioning purposes. The current type of TBS positioning signals are the MBS (Metropolitan Beacon System) signals and Positioning Reference Signals (PRS). The UE measures received TBS signals, optionally aided by assistance data, to calculate its location or to send measurements to the positioning server for position calculation. Motion sensor positioning makes use of different sensors such as accelerometers, gyros, magnetometers, to calculate the displacement of UE 104. The UE 104 estimates a relative displacement based upon a reference position and/or reference time. The UE 104 sends a report comprising the determined relative displacement which can be used to determine the absolute position. This method can be used with other positioning methods for hybrid positioning.

[0063] With reference to a conceptual overview of the current Uu implementation (release 16), the overall measurement configuration and reporting is performed per configured RAT-dependent positioning method and/or RAT-independent positioning method. FIG. 6 illustrates an example 600 of a LTE positioning protocol (LPP) request location information (RequestLocationlnformation) message as related to sidelink anchor device management, as described herein. The RequestLocationlnformation message body in a LPP message is used by the location server to request positioning measurements or a position estimate from the target device. FIG. 7 illustrates an example 700 of a LPP provide location information (ProvideLocationlnformation) message as related to sidelink anchor device management, as described herein. The ProvideLocationlnformation message body in a LPP message is used by the target device to provide positioning measurements or position estimates to the location server.

[0064] 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 T4. 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.

[0065] Table T4: Downlink measurements for downlink-based positioning techniques.

[0066] In aspects of sidelink anchor device management, this disclosure details techniques for anchor and reference devices being registered, identified, and managed based on the type of positioning method applied, as well as the number of positioning nodes involved in a sidelink positioning session, and taking into account the configuration and reporting of anchor devices for incoverage, partial coverage, and out-of-coverage scenarios. With reference to sidelink positioning, the selection and configuration of the anchor devices is essential to obtain high absolute and relative positioning accuracy. Aspects of the disclosure include implementations to identify, select, and configure an anchor device for multiple, different sidelink positioning methods. Additionally, the disclosure provides techniques to coordinate and manage multiple anchor devices including reference anchor devices using layer 1 and layer 2 identifiers. The disclosure also provides techniques for sidelink anchor device reporting including the signaling of real time difference information to assist in improved absolute and/or relative location estimation accuracy. Further, the disclosure provides to support anchor device capability exchange with other UEs, devices, and network entities via sidelink (PC5 interface), including the content of anchor device capability information.

[0067] In terms of the described techniques, an initiating device initiates a sidelink positioning and ranging session, and a responding device responds to the sidelink positioning and ranging session from the initiating device. Additionally, an anchor device facilitates a sidelink positioning session with a known location. Further, the described implementations for sidelink anchor device management may be implemented in combination to support NR RAT- independent positioning over the sidelink (PC5) interface. In this disclosure, 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 positioning reference signals (PRS), or based on existing reference signals, such as a channel state information reference signal (CSI-RS) or a sounding reference signal (SRS). A target-UE may be referred to as the device or network entity to be localized or positioned. In implementations, the term PRS can refer to any signal, such as a reference signal, which may or may not be used primarily for positioning. A target-UE may also be referred to as a UE of interest or any other node of interest, having a position (absolute or relative) that is to be obtained by the network or by the UE itself. Notably, any aspects of the positioning techniques described in this disclosure may be implemented in combination with any additional aspects of the positioning techniques described in the related disclosure: U.S. Patent Application No. 63/322,026 entitled “Sidelink Positioning Reference Unit Management” filed March 21, 2022 (docket no. SMM920210236-US- PSPF).

[0068] In aspects of the present disclosure, an anchor device can be implemented to support various functionality in a network, supporting SL (PC5 interface) positioning. An anchor device configuration can be performed by a configuration device entity, which may be an initiating UE, a roadside unit, a base station, a location server, a gNB-CU/DU, and the like. The configuration entity can configure the anchor device with the time-frequency resources for transmitting the sidelink positioning reference signals (SL PRS), including time duration and interval, in which the SL PRS is to be transmitted. The anchor device may additionally share various types of pre-defined configuration and/or assistance information with other devices that are participating or involved in a sidelink positioning session. The pre-defined configuration and/or assistance information may include 2D/3D latitude and longitude information; velocity estimates including an indication of mobility (e.g., high, medium, or low); the type of anchor device (e.g., roadside unit, UE); antenna and panel related information, including antenna panel locations, orientations, or the like. In the case of SL-TDOA, the anchor node may additionally share an indication as to whether it is a reference anchor node.

[0069] Anchor device identification, selection, and configuration can include procedures to identify and configure nearby anchors with respect to a target device. A network entity, such as a gNB or location server (e.g., a LMF) may provide a list of candidate anchor devices to the target device. The network entity may be aware of an anchor device via capability signaling, such as via RRC, LPP, MAC CE or the like, as described in more detail below. Any network entity, such as a gNB or LMF may act as a client or consumer of sidelink positioning information and request that a plurality of devices, such as UEs, signal their anchor device related parameters as mentioned above, if available. A network entity may also configure normal sidelink UEs and/or devices to operate as anchor devices based on the relative location with respect to the target device, which provides the most spatial diversity. This may be based on one or more selection and/or configuration criteria, as described following with reference to FIG. 8.

[0070] FIG. 8 illustrates an example 800 of sidelink anchor devices identification with respect to a target device, which supports sidelink anchor device management in accordance with aspects of the present disclosure. In this example, several sidelink UEs, identified as SL UE-1 through SL UE-6, may be sidelink anchor device candidates with respect to a target device 802. Anchor devices can be selected and configured based on received sidelink positioning measurements, such as from the target device 802, and the received sidelink positioning measurements indicate whether an anchor device (or anchor device candidate) has a line-of-sight (LOS) or no line-of-sight (NLOS) link with respect to the target device. In this case, the network entity may preferably configure anchor devices with a LOS link to the target device. In an implementation, the target device 802 may indicate a preferred list of anchor devices to the network based on the sidelink positioning measurements by the target UE, or may explicitly separately indicate individual devices to the network. In another implementation, the target device 802 may indicate identified anchors to the network based on ProSe discovery model A and model B communications. The trigger in this case may be received from higher layers (e.g., ProSe Application layer). The anchor devices may also be selected based on a sidelink communication range 804 with respect to the target device (target UE), where candidate or potential devices outside the sidelink communication range will be less preferred as anchor nodes when compared to devices within the sidelink communication range.

[0071] A network entity may also configure normal sidelink UEs and/or devices based on the positioning technique, which affects the number of anchor nodes required to be selected, such as at least three anchor nodes for SL-TDoA, and at least one anchor node for SL-AoA and SL-RTT. A network entity may also configure normal sidelink UEs and/or devices based on their capabilities as further described below, and/or based on their proximity as described above with reference to selection and/or configuration criteria. For example, the sidelink UEs (e.g., SL UE-1, SL UE-4, and SL UE-5) within the sidelink communication range 804 of the target device 802 can be selected as anchor devices based on the above criteria for TDOA. In another implementation, a gNB and location server may request a list of possible anchor devices via operator administration and maintenance (0AM).

[0072] In an alternative implementation, application functions (AFs) and network functions (NFs) may access a sidelink positioning information service, including anchor list information via a gateway mobile location center (GMLC) in the same trust domain (e.g., in the same PLMN) using the Ngmlc interface or Event Exposure with location information from an AMF in the same trust domain using the Namf interface. In this case, the gNB and/or the LMF may act as LCS clients. In another implementation, the anchor devices may be selected based on the quality of links between each of the sidelink anchor device candidates (e.g., the links between SL UE-1 and SL UE-4, SL UE-4 and SL UE-5, and SL UE-1 and SL UE-5) may be evaluated based on RSS measurement quality, BLER, etc. and used as anchor device selection criteria. This is to ensure that for methods such as SL-TDOA, the transmit time offset between anchor devices is kept to a minimum and the synchronization timing errors are kept as low as possible. In another implementation, the anchor devices may be selected based on the coverage scenario. An indication may be transmitted from the anchor device to applicable sidelink positioning devices (e.g., initiator device or responder devices) whether it is incoverage, partial coverage, or out-of-coverage. The network coverage of the anchor device may also be an additional criterion for selection. In a further extended implementation, the GNSS coverage may also be indicated, and in combination with the network coverage indication, can be used to select one or more of the anchor devices. [0073] Similarly, for a groupcast sidelink positioning, where the group members are known beforehand via higher-layer signaling (e.g. by V2X, ProSe) application layer, the group members may also operate as anchor devices with respect to the target member device within the same group. In this case, anchor devices may be pre-configured and associated with some validity criteria (e.g., if the group disbands then a new list of anchor devices needs to be configured). In another implementation, the target UE or device may request nearby sidelink devices for anchor device indications of an anchor device via PC5 RRC/PC5-S signaling. For example, anchor device selection by UEs or devices participating in a sidelink positioning session including the target device, and a single reference anchor device may be selected from the selected plurality of anchor devices.

[0074] Four scenarios are identified in which to support anchor device identification, selection, and configuration as described herein. The scenarios include a first scenario for UE-based UE- configured anchor device management, in which a UE supporting sidelink positioning performs RAT- dependent and/or RAT- independent positioning based on sidelink measurements received by at least one or more anchor UE or devices (e.g., a UE, reference UE, roadside unit, or the like). In this scenario, the absolute and/or relative positioning calculation entity may be the UE performing the measurements and receiving the measurement reports based on SL PRS transmissions by UE configured anchor devices. The anchor device may be configured by other sidelink devices in proximity and may be beneficial for partial coverage and out-of-coverage UEs.

[0075] A second scenario is UE-based network-configured anchor device management, in which a UE supporting sidelink positioning performs RAT-dependent and/or RAT-independent positioning based on sidelink measurements received by at least one or more anchor UE or devices (e.g., a UE, reference UE, roadside unit, or the like). In this scenario, the absolute and/or relative positioning calculation entity may be the UE performing the measurements and receiving the measurement reports based on SL PRS transmissions by network configured anchor devices. The anchor device may be configured by a network entity in proximity and may be beneficial for partial coverage and in-coverage UEs. The network configuring entity may be base station (e.g., a gNB), a location server, a reference station, reference TRP, a roadside unit, or gNB-CU/DU.

[0076] A third scenario is UE-assisted UE-configured anchor device management, in which a UE supporting sidelink positioning performs RAT-dependent and/or RAT-independent positioning based on sidelink measurements received by at least one or more anchor UE or devices (e.g., a UE, reference UE, roadside unit, or the like). In this scenario, the absolute and/or relative positioning calculation entity may be the network entity (e.g., a gNB or LMF) receiving the Uu/SL measurements and/or receiving the measurement reports based on SL PRS transmissions by the UE configured anchor devices. The anchor device may be configured by other sidelink devices in proximity and may be beneficial for partial coverage and in-coverage UEs.

[0077] A fourth scenario is UE-assisted network-configured anchor device management, in which a UE supporting sidelink positioning performs RAT-dependent and/or RAT-independent positioning based on sidelink measurements received by at least one or more anchor UE or devices (e.g., a UE, reference UE, roadside unit, or the like). In this scenario, the absolute and/or relative positioning calculation entity may be the network entity (e.g., a gNB or LMF) receiving the Uu/SL measurements and/or receiving the measurement reports based on SL PRS transmissions by network configured anchor devices. The network configuring entity may be a base station (e.g., a gNB), a location server, a reference station, a reference TRP, a roadside unit, or gNB-CU/DU. This may be beneficial for partial coverage and in-coverage UEs.

[0078] In aspects of sidelink anchor device management, an anchor device and a target device may have varying degrees of mobility, and therefore the applicability of the anchor device may be time varying depending on the range and measurement quality with respect to the target device. The switch to another anchor device may be event triggered, which relies on a particular configured threshold provided by the network to be exceeded (e.g., if the SL RSRP of the serving anchor node is lower than a configured threshold then a new anchor device may be selected). The configuration parameters for the anchor handover or switchover may include the measurement value by the device, a hysteresis value to prevent frequent handovers or switchovers, and the threshold value for the event. Additionally, another complementary event may be specified when the measurement value is above or higher than the threshold. Due to the varying number of anchor devices in proximity to a target device, it is proposed that an anchor ID be associated to an anchor device in order to differentiate among different anchors.

[0079] In one implementation, the anchor device may comprise a layer one, LI -ID derived from a layer two, L2-ID. For example, a subset of bits (e.g., most significant bit (MSB) or a least significant bit (LSB)) of the L2-ID may be associated to LI -ID. In this case, both a L2-ID and LI -ID may be associated to an anchor device. In another implementation, the anchor device ID may be a self- generated ID by the device, which may also be different than a source-ID used for sidelink communication, which may also be self-generated. In another implementation, the anchor device ID may be an application ID (APP ID) (e.g., beneficial as a groupcast ID) generated by a sidelink positioning and/or ranging application within the device (e.g., V2X or ProSe application layer). This application ID is applicable to groupcast sidelink positioning and/or ranging sessions, where the application layer is responsible for the creation of the member UE IDs within a group, which may be separately identified by a group ID. In this case, the anchor device ID may be a subset of the group ID, or have an association with respect to the group ID. Furthermore, since the anchor device may continuously change roles depending on whether the target device is within a reasonable coverage of the anchor devices, it is also proposed that the anchor devices provide a further real-time indication as to whether they are operating as anchor devices or not. Note that this is different from the capability signaling (e.g., sidelink capability information transfer procedures of anchor devices) described below, where a device may indicate its capability of being an anchor device. The described procedures include the sharing of IDs, provisioning the network threshold configuration, and a real time indication may be signaled using RRC/PC5 RRC/LPP/PC5-S/MAC CE signaling depending on whether the information is provided or received by a network entity, device, or UE.

[0080] FIG. 9 illustrates an example 900 of an implementation for signaling sidelink real time difference (RTD) information, which supports sidelink anchor device management in accordance with aspects of the present disclosure. In aspects of sidelink anchor device management, an anchor device may also report information via the sidelink interface to other anchor devices, as well as via the network (via Uu interface). An important parameter for reporting includes the RTD offset information between a pair of anchor nodes, such as a reference anchor node and another anchor node, which provides time synchronization information between a reference anchor device and another anchor device (e.g., to enable the sidelink TDoA measurements). The anchor devices may also report such information to a configuration entity or positioning calculation entity. The Table T5 below describes the sidelink RTD information field descriptions shown in the example 900. [0081] Table T5: Sidelink RTD Information Field Descriptions

[0082] The anchor device may report the real time difference between itself and another anchor device. Furthermore, anchor device reporting may support periodical reporting, semi-persistent, or immediate reporting mechanisms via RRC/PC5 RRC/ LPP/PC5-S/MAC CE signaling. In addition, other parameters may be reported, including a validity time of the anchor device based on different time bases, a number of served target devices, a mobility state, and/or an area ID or zone ID (for geographical) associated with the anchor ID. For pre-configuration, anchor devices may be allowed to operate in different areas based on the area ID, a list of camped cells, the zone ID, a PLMN ID, or any other type of geographical region identifier. In another implementation, the anchor device may dynamically update its known location and antenna orientation information based on the applicable mobility. Dynamic location and antenna orientation updates may include 2D/3D location information, including latitude and longitudinal information, antenna locations, distributed antenna (DAS) locations, device antenna panel information, or the like. The location updates may be event triggered based on delta locations compared to the previously reported locations. In other implementation, the anchor device may report the relative timing difference between its SL PRS transmission and other (candidate) anchor devices. [0083] FIG. 10 illustrates an example 1000 of anchor device capability exchange that supports sidelink anchor device management in accordance with aspects of the present disclosure. This example 1000 illustrates a solicited request for anchor device capability information of an anchor device 1002 from a UE 104 via SL (PC5) interface. The anchor device 1002 can provide its capability information indicating an ability to operate as an anchor device via solicited and/or unsolicited signaling to other UEs via the SL (PC5) interface. In another implementation, a dedicated sidelink positioning protocol may be used to signal anchor device capability information. In an extended implementation, the capabilities may also apply to the initiator and/or responder devices participating in a sidelink session. Similarly, FIG. 11 illustrates an example 1100 of anchor device capability exchange that supports sidelink anchor device management in accordance with aspects of the present disclosure. This example 1100 illustrates a solicited request for anchor device capability information of an anchor device 1102 from a gNB or location server 1104 via Uu interface using RRC or LPP signaling. The anchor device 1102 can provide its capability information indicating an ability to operate as an anchor device via solicited and/or unsolicited signaling to network entities, such as to the gNB (e.g., using RRC signaling) and/or to the LMF (e.g., using LPP signaling).

[0084] In aspects of these two types of capability exchange for anchor devices, the anchor device capabilities can include the following described features. Supported sidelink positioning methods, e.g., SL-TDoA, SL-RTT (single-sided and/or double-sided), SL-AoA, etc. Supported hybrid positioning modes including one or more of the above sidelink positioning and/or Uu positioning techniques. The maximum number of PRS resources the anchor device may transmit, which may be according to defined SL PRS resource granularities including sidelink positioning frequency layer, SL PRS Resource Pool, SL PRS Resource Set, SL PRS Resource IDs. Supported positioning modes of the anchor device as detailed above with reference to the identification, selection, and configuration of a sidelink anchor device, including UE-based UE-configured, UE-based network-configured, UE-assisted UE-configured, and UE-assisted network-configured. Supported measurement capabilities, including a list of supported bands including FR1 and FR2. Supported PRS processing capabilities (if applicable), and reporting modes including periodical, semi-persistent, and one-shot reporting. Capable of jointly acting as an anchor device for Uu and sidelink positioning methods. Supported number of per pair of sidelink RSTD measurements if the anchor device is performing measurements. The mobility type of the anchor device as static or mobile. The location source as RAT-dependent or RAT-independent methods, pre-configured, offline, and/or calibration. The anchor device type as a UE, a RSU, a CPE, and the like. An anchor device ID may also be signaled as part of the capability message. An indication that the device may operate in-coverage, out-of- coverage and/or in partial coverage scenarios.

[0085] FIG. 12 illustrates an example 1200 of SL timing error corrections using SL PRU as related to sidelink positioning reference unit management. The SL timing error corrections are the error corrections discussed above. In the example 1200, a legend 1202 is illustrated showing that solid arrows refer to SL PRU measurement reports, large-dashed arrows refer to SL target UE measurement reports, and small-dashed arrows refer to SL PRS. Also in the example 1200 Ant refers to antenna and BB refers to baseband. As illustrated in the example 1200, SL PRS are transferred from the anchor devices to the SL PRU as well as the SL target UE. The SL target UE transmits SL target UE measurement reports to the SL anchor devices, and the SL PRU transmits SL PRU measurement reports to the SL anchor devices.

[0086] In one or more implementations, a SL PRU 116 has an ID. The SL PRU 116 device may have varying degrees of mobility and therefore the applicability of the SL PRU 116 device may be time varying depending on the range and measurement quality with respect to the target device or group of target devices. The switch to another SL PRU 116 device may be event triggered, which relies on a particular configured threshold provided by the network to be exceeded, e.g., if the SL RSRP of the nearby SL PRU 116 node (with respect to the SL target device) is lower than a configured threshold then a new SL PRU 116 device may be selected. The configuration parameters for the SL PRU 116 handover or switchover may include the measurement value by the device, hysteresis value to prevent frequent handovers or switchovers and the threshold value for the event. Additionally or alternatively, another complementary event may be specified when the measurement value is higher than the threshold. Due to the potential variable number of SL PRU 116 devices, in proximity to a target device, it is proposed that an SL PRU ID be associated with an PRU in order to differentiate among different PRUs.

[0087] In one implementation, the SL PRU 116 may comprise a LI -ID derived from L2-ID. For example, a subset of bits (e.g., most-significant bit or least-significant bit ) of the L2-ID may be associated with LI -ID. In this case both a L2-ID and LI -ID may be associated with the SL PRU 116. [0088] Additionally or alternatively, the SL PRU ID may comprise a self-generated ID by the device, which may also be different to as a source-ID used for sidelink communication, which may also be self-generated.

[0089] Additionally or alternatively, the SL PRU ID may comprise of an application ID (APP ID) generated by an SL positioning or ranging application within the device, e.g., in the V2X or proximity service (ProSe) application layer. The is applicable to groupcast SL positioning or ranging sessions, where the application layer is responsible for the creation of the member UE IDs within a group, which may be separately identified by a Group ID. In this case, the SL PRU ID may be a subset of the SL PRU ID or have an association with respect to the group ID.

[0090] Furthermore, since the SL PRU 116 may continuously change roles depending on whether the target device is within a reasonable coverage of the anchor devices, the SL PRU 116 devices may provide a further real-time indication to the network entities or other UEs on whether they are acting as SL PRU 116 or not. It should be noted that this indication is different from the capability signaling discussed herein, where a device may indicate its capability of being an SL PRU 116 device. The described procedures including the sharing of IDs, provisioning of the network threshold configuration and real time indication may be signaled using any of a variety of signaling, such as RRC, PC5 RRC, LPP, PC5-S, or medium access control element (MAC CE) signaling depending on whether the information is provided or received by a network entity or by a device or UE 104.

[0091] In one or more implementations, a SL PRU 116 device may also report information via the SL interface to UEs, devices, or anchor devices as well as the network (via Uu interface). The reference measurements may be separately requested via a separate measurement configuration message and the SL PRU 116 may respond accordingly with a separate reporting message containing the reference measurements. The SL PRU 116 may report such information to either a configuration entity or positioning calculation entity. The request and response signaling of the SL positioning reference measurements may be achieved using, for example, RRC, PC5 RRC, LPP, PC5-S, or MAC CE signaling.

[0092] FIG. 13 illustrates an example 1300 of a type of request and response signaling exchange for reference measurements between a configuration entity or positioning calculation entity and a SL PRU 116 as related to sidelink positioning reference unit management. The example 1300 includes a SL PRU 116 and a UE 104, and shows SL PRU 116 reference measurement and known location exchange with a UE 104 or device as the configuration entity or positioning calculation entity.

[0093] The UE 104 transmits a request 1302 to the SL PRU 116 for SL positioning reference measurements and known location information of the SL PRU 116. The request 1302 is transmitted, for example, using PC5 RRC, SL MAC CE, or SL LPP signaling. The SL PRU 116 collects the requested SL positioning reference measurements and transmits a response 1304 to the UE 104 providing the SL positioning reference measurements and known location information of the SL PRU 116. The response 1304 is transmitted, for example, using PC5 RRC, SL MAC CE, or SL LPP signaling. Additionally or alternatively, a dedicated SL positioning protocol (SL LPP) may be used to signal request and response of SL reference measurements from the SL PRU 116.

[0094] FIG. 14 illustrates an example 1400 of another type of request and response signaling exchange for reference measurements between a configuration entity or positioning calculation entity and a SL PRU 116 as related to sidelink positioning reference unit management. The example 1400 includes a SL PRU 116 and a network entity 1402, and shows a SL PRU 116 reference measurement and known location exchange with a network node as the configuration entity or positioning calculation entity. The network entity 1402 can be any of a variety of network nodes, such as a base station 102 (e.g., gNB).

[0095] The network entity 1402 transmits to the SL PRU 116 a request 1404 for SL positioning reference measurements and known location information of the SL PRU 116. The request 1404 is transmitted, for example, using LPP, RRC, or DL MAC CE signaling. The SL PRU 116 collects the requested SL positioning reference measurements and transmits a response 1406 to the UE 104 providing the SL positioning reference measurements and known location information of the SL PRU 116. The response 1406 is transmitted, for example, using LPP, RRC, or DL MAC CE signaling.

[0096] Returning to FIG. 1, in one or more implementations the SL PRU 116 supports periodical reporting, semi-persistent or immediate reporting mechanisms via, for example, RRC, PC5 RRC, LPP, PC5-S, or MAC CE signaling. In addition, other parameters that may be reported include one or more of validity time of SL PRU 116 device based on different time bases; mobility state; or area ID or zone ID associated with anchor ID, for pre-configuration anchor devices may be allowed to operate in different areas based on area ID, list of camped cells, zone ID, public land mobile network (PLMN) ID, or any geographical region identifier.

[0097] Additionally or alternatively, the SL PRU 116 device may dynamically update its known location and antenna orientation information based on the applicable mobility. Dynamic location and antenna orientation updates may include one or more of 2D or 3D location information, including latitude and longitudinal information, antenna locations, distributed antenna (DAS) locations, device antenna panel information, or the like. The location updates may be event triggered based on delta locations compared to the previously reported locations.

[0098] In one or more implementations, the SL PRU 116 may provide its capability information of acting as an SL PRU 116 to a configuration entity, such as a UE 104, a base station 102, a location server (e.g., LMF), and so forth. The SL PRU 116 may provide its capability information of acting as an SL PRU 116 using via solicited and/or unsolicited signaling to other UEs (SL devices) via the SL (PC5) interface, or via solicited and/or unsolicited signaling to network entities such as the base station 102 (e.g., using RRC signaling) and/or LMF (e.g., using LPP signaling)

[0099] In addition, this capability information may be used to inform the network and/or other UEs 104 or devices that there are SL PRUs in the vicinity and can extend to in-coverage, partial coverage and out-of-coverage scenarios. Dynamic indications may be used via the aforementioned signaling mechanisms to indicate whether a UE 104 or device is acting as a SL PRU 116 at any given time (e.g., as discussed above). Additionally or alternatively, the SL PRU 116 may provide its known location information using the capability information exchange.

[0100] FIG. 15 illustrates an example 1500 of a type of capability exchange for a SL positioning reference unit as related to sidelink positioning reference unit management. The example 1500 includes a SL PRU 116 and a UE 104, and shows a solicited request for SL PRU 116 capability information via SL (PC5) interface. The UE 104 transmits a request 1502 to the SL PRU 116 for SL capability information. The request 1502 is transmitted, for example, using PC5 RRC signaling. The SL PRU 116 transmits a response 1504 to the UE 104 providing the capability information of the SL PRU 116. The response 1504 is transmitted, for example, using PC5 RRC signaling. Additionally or alternatively, a dedicated SL positioning protocol may be used to signal SL PRU 116 device capability information. [0101] FIG. 16 illustrates an example 1600 of another type of capability exchange for a SL positioning reference unit as related to sidelink positioning reference unit management. The example 1600 includes a SL PRU 116 and a network entity 1602 that is a base station 102 (e.g. a gNB) or a location server, and shows a solicited request for SL PRU 116 information via Uu interface using RRC or LPP signaling.

[0102] The network entity 1602 transmits to the SL PRU 116 a request 1604 for SL capability information. The request 1604 is transmitted, for example, using RRC or LPP signaling. The SL PRU 116 transmits a response 1606 to the UE 104 providing the capability information of the SL PRU 116. The response 1606 is transmitted, for example, using RRC or LPP signaling.

[0103] In one or more implementations, the PRU capabilities include supported SL positioning methods, e.g., SL-TDoA, SL-RTT (single-sided and /or double-sided), SL-AoA, and so forth. The PRU capabilities may also include supported hybrid positioning modes including one or more of the above SL positioning and/or Uu positioning techniques. Additionally or alternatively, the PRU capabilities include supported positioning modes of the anchor device as discussed above including UE-based UE-configured, UE-based network- configured, UE-assisted UE-configured, UE-assisted network-configured. Additionally or alternatively, the PRU capabilities include supported SL reference measurement capabilities, e.g., including a list of supported bands including FR1 and FR2. Additionally or alternatively, the SL PRU 116 may also be capable of performing Uu reference measurements in addition to SL reference measurements.

[0104] Additionally or alternatively, the PRU capabilities include supported SL PRS processing capabilities (if applicable). Additionally or alternatively, the PRU capabilities include supported reporting modes including periodical, semi-persistent and one-shot reporting. Additionally or alternatively, the PRU capabilities include capability of jointly acting as a positioning reference unit for Uu and SL positioning methods. Additionally or alternatively, the PRU capabilities include supported number of per pair of SL RSTD measurements.

[0105] Additionally or alternatively, the PRU capabilities include mobility type (e.g., static or mobile). Additionally or alternatively, the PRU capabilities include location source (e.g., RAT- dependent/RAT-independent methods, per-configured/offline/calibration). Additionally or alternatively, the PRU capabilities include anchor device type (e.g., UE, RSU, CPE). Additionally or alternatively, the PRU capabilities include the SL PRU ID (e.g., signaled as part of the capability message). Additionally or alternatively, the PRU capabilities include an indication that the device may operate in-coverage, out-of-coverage and/or in partial coverage scenarios. Additionally or alternatively, the PRU capabilities include known location information as described above.

[0106] FIG. 17 illustrates an example of a block diagram 1700 of a device 1702 that supports sidelink anchor device management in accordance with aspects of the present disclosure. The device 1702 may be an example of a configuration entity, such as a UE, an anchor UE, a base station, a gNB, a roadside unit, a location server, or other type of configuration entity as described herein. Alternatively, or in addition, the device 1702 may be an example of a SL PRU (e.g., a UE 104 or other device) as described herein. The device 1702 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 1702 may include components for bi-directional communications including components for transmitting and receiving communications, such as a positioning and/or communications manager 1704, a processor 1706, a memory 1708, a receiver 1710, a transmitter 1712, and an I/O controller 1714. 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 and/or communications manager 1704, the receiver 1710, the transmitter 1712, 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 and/or communications manager 1704, the receiver 1710, the transmitter 1712, 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 and/or communications manager 1704, the receiver 1710, the transmitter 1712, 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 1706 and the memory 1708 coupled with the processor 1706 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 1706, instructions stored in the memory 1708).

[0109] Additionally or alternatively, in some implementations, the positioning and/or communications manager 1704, the receiver 1710, the transmitter 1712, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 1706. If implemented in code executed by the processor 1706, the functions of the positioning and/or communications manager 1704, the receiver 1710, the transmitter 1712, 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 and/or communications manager 1704 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 1710, the transmitter 1712, or both. For example, the positioning and/or communications manager 1704 may receive information from the receiver 1710, send information to the transmitter 1712, or be integrated in combination with the receiver 1710, the transmitter 1712, or both to receive information, transmit information, or perform various other operations as described herein. Although the positioning and/or communications manager 1704 is illustrated as a separate component, in some implementations, one or more functions described with reference to the positioning and/or communications manager 1704 may be supported by or performed by the processor 1706, the memory 1708, or any combination thereof. For example, the memory 1708 may store code, which may include instructions executable by the processor 1706 to cause the device 1702 to perform various aspects of the present disclosure as described herein, or the processor 1706 and the memory 1708 may be otherwise configured to perform or support such operations.

[0111] For example, the positioning manager 1704 may support wireless communication and/or network signaling at a device (e.g., the device 1702, a configuration entity) in accordance with examples as disclosed herein. The positioning manager 1704 and/or other device components may be configured as or otherwise support an apparatus, such as a device implemented as a configuration entity, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: transmit a sidelink positioning capability request to one or more sidelink devices as potential sidelink anchor devices; receive, from the one or more sidelink devices, anchor device capability information and a location of the respective one or more sidelink devices; select at least one of the one or more sidelink devices as an anchor device based at least in part on the anchor device capability information and the location of the at least one sidelink device; and transmit a sidelink positioning reference signal transmission configuration to the anchor device establishing a sidelink positioning session with a target device.

[0112] Additionally, the apparatus (e.g., a device implemented as a configuration entity) includes any one or combination of: the location of the at least one sidelink device is designated as a fixed location in time. The processor is configured to cause the apparatus to select the at least one sidelink device as the anchor device based at least in part on a sidelink line-of-sight link quality between the apparatus and the at least one sidelink device. The processor is configured to cause the apparatus to select the at least one sidelink device as the anchor device based at least in part on a sidelink communication range of the at least one sidelink device to the apparatus. The processor is configured to cause the apparatus to select the at least one sidelink device as the anchor device based at least in part on a sidelink measurement quality. The processor and the transceiver are configured to cause the apparatus to receive, from the at least one sidelink device, one or more sidelink measurements and the location of the at least one sidelink device; and select the at least one sidelink device as the anchor device based at least in part on the one or more sidelink measurements and the location. The apparatus comprises at least one of a user equipment (UE), an anchor UE, a base station, a next-generation NodeB (gNB), a roadside unit, or a location server. The processor and the transceiver are configured to cause the apparatus to receive, from a network device, a candidate list of the potential sidelink anchor devices. The processor is configured to cause the apparatus to select the anchor device based at least in part on a link quality between each of the potential sidelink anchor devices. The processor is configured to cause the apparatus to select the anchor device based at least in part on a coverage area of each of the potential sidelink anchor devices. The apparatus comprises a user equipment (UE), and wherein the processor is configured to cause the apparatus to configure the anchor device according to at least one of a UE-based UE-configured anchor device configuration, a UE-based network-configured anchor device configuration, a UE-assisted UE-configured anchor device configuration, or a UE-assisted network-configured anchor device configuration. The processor and the transceiver are configured to cause the apparatus to receive, from the anchor device, a status indication as one of the anchor device is operably configured as the anchor device or is no longer operable as the anchor device.

[0113] The positioning manager 1704 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at a device, including transmitting a sidelink positioning capability request to one or more sidelink devices as potential sidelink anchor devices; receiving, from the one or more sidelink devices, anchor device capability information and a location of the respective one or more sidelink devices; selecting at least one of the one or more sidelink devices as an anchor device based at least in part on the anchor device capability information and the location of the at least one sidelink device; and transmitting a sidelink positioning reference signal transmission configuration to the anchor device establishing a sidelink positioning session with a target device.

[0114] Additionally, wireless communication and/or network signaling at the device includes any one or combination of: the location of the at least one sidelink device is designated as a fixed location in time. The selecting the at least one sidelink device as the anchor device is based at least in part on a sidelink line-of-sight link quality between a configuration entity and the at least one sidelink device. The selecting the at least one sidelink device as the anchor device is based at least in part on a sidelink communication range of the at least one sidelink device to a configuration entity. The selecting the at least one sidelink device as the anchor device is based at least in part on a sidelink measurement quality. The method further comprising receiving, from the at least one sidelink device, one or more sidelink measurements and the location of the at least one sidelink device, and wherein the selecting the at least one sidelink device as the anchor device is based at least in part on the one or more sidelink measurements and the location. A configuration entity comprises at least one of a user equipment (UE), an anchor UE, a base station, a next-generation NodeB (gNB), a roadside unit, or a location server. The method further comprising receiving, from a network device, a candidate list of the potential sidelink anchor devices. The selecting the anchor device is based at least in part on a link quality between each of the potential sidelink anchor devices. The selecting the anchor device is based at least in part on a coverage area of each of the potential sidelink anchor devices. The anchor device is configured according to at least one of a UE-based UE-configured anchor device configuration, a UE-based network-configured anchor device configuration, a UE-assisted UE-configured anchor device configuration, or a UE-assisted network-configured anchor device configuration. The method further comprising receiving, from the anchor device, a status indication as one of the anchor device is operably configured as the anchor device or is no longer operable as the anchor device.

[0115] For example, the communications manager 1704 may support wireless communication and/or network signaling at a device (e.g., the device 1702, a SL PRU 116 such as a UE 104) in accordance with examples as disclosed herein. The communications manager 1704 and/or other device components may be configured as or otherwise support an apparatus, such as a UE, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: receive, from a configuration entity, a measurement configuration to perform sidelink positioning reference measurements; collect one or more sidelink positioning reference measurements; and transmit, to the configuration entity, the one or more sidelink positioning reference measurements and a known location of the apparatus.

[0116] Additionally, the apparatus (e.g., a SL PRU) includes any one or combination of: where the one or more sidelink positioning reference measurements include at least one of a timing-based reference measurement or an angular-based reference measurement; where the one or more sidelink positioning reference measurements include at least one of a SL-RSTD reference measurement, a SL UE Rx-Tx time difference reference measurement, a SL ToF reference measurement, a ToA reference measurement, a SL-angle-of-arrival measurement, a SL TDoA reference measurement, a SL RTT reference measurement, or a SL AoA reference measurement; where the known location of the apparatus includes one or more of 2D or 3D latitude and longitude information, height or altitude information, a velocity estimate, an antenna and panel related location information and reference points, or an uncertainty value or a confidence interval associated with the known location; where the configuration entity comprises a UE, and where the processor and the transceiver are further configured to cause the apparatus to: receive, from the UE, a request for the one or more sidelink positioning reference measurements and the known location of the apparatus; and transmit, to the UE in response to the request, the one or more sidelink positioning reference measurements and a known location of the apparatus; where the configuration entity comprises a network entity, and where the processor and the transceiver are further configured to cause the apparatus to: receive, from the network entity, a request for the one or more sidelink positioning reference measurements and the known location of the apparatus; and transmit, to the network entity in response to the request, the one or more sidelink positioning reference measurements and a known location of the apparatus; where the apparatus comprises a UE, and where the processor and the transceiver are further configured to cause the apparatus to operate in at least one of a UE-based UE-configured positioning mode, a UE-based network-configured positioning mode, a UE-assisted UE-configured positioning mode, or a UE-assisted network-configured positioning mode; where the processor and the transceiver are further configured to cause the apparatus to collect the one or more sidelink positioning reference measurements in a FR1 band or a FR2 band; where the processor and the transceiver are further configured to cause the apparatus to: collect one or more NR Uu interface positioning reference measurements; and transmit, to a base station, the one or more NR Uu positioning reference measurements and the known location of the apparatus; where the apparatus includes an ID that is at least one of a LI -ID derived from a L2-ID, a self-generated ID, or an application ID generated by a sidelink positioning application of the apparatus, and where the processor and the transceiver are further configured to cause the apparatus to: transmit, to the configuration entity, the apparatus ID with the one or more sidelink positioning reference measurements and the known location of the apparatus; where the processor and the transceiver are further configured to cause the apparatus to: receive, from a UE, a request for capability information regarding the apparatus acting as a sidelink positioning reference unit; and transmit, to the UE in response to the request, capability information regarding the apparatus acting as a sidelink positioning reference unit; where the processor and the transceiver are further configured to cause the apparatus to: receive, from a network entity, a request for capability information regarding the apparatus acting as a sidelink positioning reference unit; and transmit, to the network entity in response to the request, capability information regarding the apparatus acting as a sidelink positioning reference unit; where the processor and the transceiver are further configured to cause the apparatus to: dynamically update the known location and antenna orientation information of the apparatus, where the updated known location and antenna orientation information is based at least in part on delta locations compared to one or more previously reported locations.

[0117] The communications manager 1704 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at a SL PRU, including receiving, from a configuration entity, a measurement configuration to perform sidelink positioning reference measurements; collecting one or more sidelink positioning reference measurements; and transmitting, to the configuration entity, the one or more sidelink positioning reference measurements and a known location of the PRU. [0118] Additionally, wireless communication and/or network signaling at the SL PRU includes any one or combination of: where the one or more sidelink positioning reference measurements include at least one of a timing-based reference measurement or an angular-based reference measurement; the one or more sidelink positioning reference measurements include at least one of a SL-RSTD reference measurement, a SL UE Rx-Tx time difference reference measurement, a SL ToF reference measurement, a ToA reference measurement, a SL-angle-of-arrival measurement, a SL TDoA reference measurement, a SL RTT reference measurement, or a SL AoA reference measurement; where the known location of the PRU includes one or more of 2D or 3D latitude and longitude information, height or altitude information, a velocity estimate, an antenna and panel related location information and reference points, or an uncertainty value or a confidence interval associated with the known location; where the configuration entity comprises a UE, and further comprises: receiving, from the UE, a request for the one or more sidelink positioning reference measurements and the known location of the PRU; and transmitting, to the UE in response to the request, the one or more sidelink positioning reference measurements and a known location of the PRU; where the configuration entity comprises a network entity, and further comprises: receiving, from the network entity, a request for the one or more sidelink positioning reference measurements and the known location of the PRU; and transmitting, to the network entity in response to the request, the one or more sidelink positioning reference measurements and a known location of the PRU; where the PRU comprises a UE, and further comprises operating in at least one of a UE-based UE-configured positioning mode, a UE-based network-configured positioning mode, a UE-assisted UE-configured positioning mode, or a UE-assisted network-configured positioning mode; further including collecting the one or more sidelink positioning reference measurements in a FR1 band or a FR2 band; further including: collecting one or more NR Uu interface positioning reference measurements; and transmitting, to a base station, the one or more NR Uu positioning reference measurements and the known location of the PRU; where the PRU includes a PRU ID that is at least one of a Ll-IDderived from a L2-ID, a self-generated ID, or an application ID generated by a sidelink positioning application of the PRU, and the method further comprises: transmitting, to the configuration entity, the PRU ID with the one or more sidelink positioning reference measurements and the known location of the PRU; further including: receiving, from a UE, a request for capability information regarding the PRU acting as a sidelink positioning reference unit; and transmitting, to the UE in response to the request, capability information regarding the PRU acting as a sidelink positioning reference unit; further including: receiving, from a network entity, a request for capability information regarding the PRU acting as a sidelink positioning reference unit; and transmitting, to the network entity in response to the request, capability information regarding the PRU acting as a sidelink positioning reference unit; further including: dynamically update the known location and antenna orientation information of an apparatus implementing the method, where the updated known location and antenna orientation information is based at least in part on delta locations compared to one or more previously reported locations.

[0119] The processor 1706 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 1706 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 1706. The processor 1706 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1708) to cause the device 1702 to perform various functions of the present disclosure.

[0120] The memory 1708 may include random access memory (RAM) and read-only memory (ROM). The memory 1708 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1706 cause the device 1702 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 1706 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 1708 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.

[0121] The I/O controller 1714 may manage input and output signals for the device 1702. The I/O controller 1714 may also manage peripherals not integrated into the device 1702. In some implementations, the I/O controller 1714 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 1714 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 1714 may be implemented as part of a processor, such as the processor 1706. In some implementations, a user may interact with the device 1702 via the I/O controller 1714 or via hardware components controlled by the I/O controller 1714.

[0122] In some implementations, the device 1702 may include a single antenna 1716. However, in some other implementations, the device 1702 may have more than one antenna 1716, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The receiver 1710 and the transmitter 1712 may communicate bi-directionally, via the one or more antennas 1716, wired, or wireless links as described herein. For example, the receiver 1710 and the transmitter 1712 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 1716 for transmission, and to demodulate packets received from the one or more antennas 1716.

[0123] FIG. 18 illustrates an example of a block diagram 1800 of a device 1802 that supports sidelink anchor device management in accordance with aspects of the present disclosure. The device 1802 may be an example of an anchor device as described herein. Alternatively, or in addition, the device 1802 may be an example of a configuration entity or a positioning calculation entity, as described herein. The device 1802 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 1802 may include components for bi-directional communications including components for transmitting and receiving communications, such as a positioning and/or communications manager 1804, a processor 1806, a memory 1808, a receiver 1810, a transmitter 1812, and an VO controller 1814. 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).

[0124] The positioning and/or communications manager 1804, the receiver 1810, the transmitter 1812, 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 and/or communications manager 1804, the receiver 1810, the transmitter 1812, or various combinations or components thereof may support a method for performing one or more of the functions described herein. [0125] In some implementations, the positioning and/or communications manager 1804, the receiver 1810, the transmitter 1812, 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 1806 and the memory 1808 coupled with the processor 1806 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 1806, instructions stored in the memory 1808).

[0126] Additionally or alternatively, in some implementations, the positioning and/or communications manager 1804, the receiver 1810, the transmitter 1812, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 1806. If implemented in code executed by the processor 1806, the functions of the positioning and/or communications manager 1804, the receiver 1810, the transmitter 1812, 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).

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

[0128] For example, the positioning manager 1804 may support wireless communication and/or network signaling at a device (e.g., the device 1802, an anchor device) in accordance with examples as disclosed herein. The positioning manager 1804 and/or other device components may be configured as or otherwise support an apparatus, such as an anchor device, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: receive, from a configuration device, a sidelink positioning capability request; transmit, to the configuration device, anchor device capability information and a location of the apparatus; and receive, as a selected anchor device based at least in part on the anchor device capability information and the location of the apparatus, a sidelink positioning reference signal transmission configuration establishing a sidelink positioning session with one or more target devices.

[0129] Additionally, the apparatus (e.g., an anchor device) includes any one or combination of: the location of the apparatus is designated as a fixed location in time. The apparatus is selected as the anchor device based at least in part on a sidelink line-of-sight link quality between the apparatus and the one or more target devices. The apparatus is selected as the anchor device based at least in part on a sidelink communication range of the apparatus to the one or more target devices. The apparatus is selected as the anchor device based at least in part on a sidelink measurement quality. The processor and the transceiver are configured to cause the apparatus to transmit a sidelink positioning reference signal to the one or more target devices based at least in part on the location of the apparatus and mobility of the apparatus. The processor is configured to cause the apparatus to determine a location estimation of the configuration device. The processor and the transceiver are configured to cause the apparatus to transmit sidelink positioning configuration information to the one or more target devices participating in the sidelink positioning session. The processor and the transceiver are configured to cause the apparatus to transmit the anchor device capability information and the location of the apparatus to the one or more target devices participating in the sidelink positioning session. The processor and the transceiver are configured to cause the apparatus to transmit pre-defined assistance information to the one or more target devices participating in the sidelink positioning session. The processor and the transceiver are configured to cause the apparatus to transmit, to the configuration device, a status indication as one of the apparatus is operably configured as the anchor device or is no longer operable as the anchor device. The apparatus is the anchor device configured according to at least one of a UE-based UE-configured anchor device configuration, a UE-based network-configured anchor device configuration, a UE-assisted UE-configured anchor device configuration, or a UE- assisted network-configured anchor device configuration. The apparatus includes an anchor device identifier (ID) that is at least one of a layer one ID (LI -ID) derived from a layer two ID (L2-ID), a self-generated ID, or an application ID generated by a sidelink positioning application of the apparatus, and wherein the processor and the transceiver are further configured to cause the apparatus to transmit, to the configuration device, the anchor device ID with the anchor device capability information and the location of the apparatus. The processor and the transceiver are configured to cause the apparatus to transmit time difference information with respect to itself and one or more additional anchor devices.

[0130] The positioning manager 1804 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at an anchor device, including receiving, from a configuration device, a sidelink positioning capability request; transmitting, to the configuration device, anchor device capability information and a location; and receiving, as a selected anchor device based at least in part on the anchor device capability information and the location, a sidelink positioning reference signal transmission configuration establishing a sidelink positioning session with one or more target devices.

[0131] Additionally, wireless communication at the anchor device includes any one or combination of: the location is designated as a fixed location in time. The anchor device is selected based at least in part on a sidelink line-of-sight link quality between the anchor device and the one or more target devices. The anchor device is selected based at least in part on a sidelink communication range of the anchor device to the one or more target devices. The anchor device is selected based at least in part on a sidelink measurement quality. The method further comprising transmitting a sidelink positioning reference signal to the one or more target devices based at least in part on the location and mobility of the anchor device. The method further comprising determining a location estimation of the configuration device. The method further comprising transmitting sidelink positioning configuration information to the one or more target devices participating in the sidelink positioning session. The method further comprising transmitting the anchor device capability information and the location to the one or more target devices participating in the sidelink positioning session. The method further comprising transmitting pre-defined assistance information to the one or more target devices participating in the sidelink positioning session. The method further comprising transmitting, to the configuration device, a status indication as one of the anchor device being operably configured as the anchor device or is no longer operable as the anchor device. The anchor device is configured according to at least one of a UE-based UE-configured anchor device configuration, a UE-based network-configured anchor device configuration, a UE-assisted UE-configured anchor device configuration, or a UE-assisted network-configured anchor device configuration. The anchor device includes an anchor device identifier (ID) that is at least one of a layer one ID (LI -ID) derived from a layer two ID (L2-ID), a self-generated ID, or an application ID generated by a sidelink positioning application of the apparatus, and wherein the anchor device ID is transmitted to the configuration device with the anchor device capability information and the location. The method further comprising transmitting, by the anchor device, time difference information with respect to itself and one or more additional anchor devices.

[0132] For example, the communications manager 1804 may support wireless communication and/or network signaling at a device (e.g., the device 1802, such as a configuration entity or a positioning calculation entity) in accordance with examples as disclosed herein. The communications manager 1804 and/or other device components may be configured as or otherwise support an apparatus, such as a configuration entity or a positioning calculation entity, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: receive, from a PRU, one or more sidelink positioning reference measurements and a known location of the PRU; generate measurement error correction information based at least in part on the one or more sidelink positioning reference measurements; and transmit, to a positioning calculation entity, the measurement error correction information.

[0133] Additionally, the apparatus (e.g., a configuration entity or a positioning calculation entity) includes any one or combination of: where the processor and the transceiver are further configured to cause the apparatus to: generate the measurement error correction information by determining a calibration of timing-based and angular-based measurement errors based at least in part on the on the one or more sidelink positioning reference measurements; and transmit, to the PRU as the measurement error correction information, the timing-based and angular-based measurement error correction information; where the measurement error correction information includes at least one of pseudo-range errors, synchronization timing errors, RSTD reference measurements, AOA calibration errors, or time validity duration of the measurement error correction information; where the processor and the transceiver are further configured to cause the apparatus to: transmit, to the PRU, a measurement configuration for the PRU to perform sidelink positioning reference measurements using the one or more sidelink positioning reference measurements; and receive, in response to the measurement configuration, the one or more sidelink positioning reference measurements and the known location of the PRU; where the apparatus is the positioning calculation entity; where the one or more sidelink positioning reference measurements include at least one of a timing-based reference measurement or an angular-based reference measurement; where the one or more sidelink positioning reference measurements include at least one of a SL-RSTD reference measurement, a SL UE Rx-Tx time difference reference measurement, a SL ToF reference measurement, a ToA reference measurement, a SL-angle-of-arrival measurement, a SL TDoA reference measurement, a SL RTT reference measurement, or a SL AoA reference measurement; where the known location of the PRU includes one or more of 2D or 3D latitude and longitude information, height or altitude information, a velocity estimate, an antenna and panel related location information and reference points, or an uncertainty value or a confidence interval associated with the known location; where the apparatus comprises a UE, and where the processor and the transceiver are further configured to cause the apparatus to: transmit, to the PRU, a request for the one or more sidelink positioning reference measurements and the known location of the PRU; and receive, from the PRU in response to the request, the one or more sidelink positioning reference measurements and a known location of the PRU; where the apparatus comprises a network entity, and where the processor and the transceiver are further configured to cause the apparatus to: transmit, to the PRU, a request for the one or more sidelink positioning reference measurements and the known location of the PRU; and receive, from the PRU in response to the request, the one or more sidelink positioning reference measurements and a known location of the PRU; where the PRU includes a PRU ID that is at least one of a LI -ID derived from a L2-ID, a self-generated ID, or an application ID generated by a sidelink positioning application of the PRU, and where the processor and the transceiver are further configured to cause the apparatus to: receive, from the PRU, the PRU ID with the one or more sidelink positioning reference measurements and the known location of the PRU; where the processor and the transceiver are further configured to cause the apparatus to: transmit, to the PRU, a request for capability information regarding the PRU acting as a sidelink positioning reference unit; and receive, from the PRU in response to the request, capability information regarding the PRU acting as a sidelink positioning reference unit.

[0134] The communications manager 1804 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at a configuration entity or a positioning calculation entity, including receiving, from a positioning reference unit PRU, one or more sidelink positioning reference measurements and a known location of the PRU; generating measurement error correction information based at least in part on the one or more sidelink positioning reference measurements; and transmitting, to a positioning calculation entity, the measurement error correction information.

[0135] Additionally, wireless communication at the configuration entity or a positioning calculation entity includes any one or combination of: further including: generating the measurement error correction information by determining a calibration of timing-based and angular-based measurement errors based at least in part on the on the one or more sidelink positioning reference measurements; and transmitting, to the PRU as the measurement error correction information, the timing-based and angular-based measurement error correction information; where the measurement error correction information includes at least one of pseudo-range errors, synchronization timing errors, RSTD reference measurements, AOA calibration errors, or time validity duration of the measurement error correction information; further including: transmitting, to the PRU, a measurement configuration for the PRU to perform sidelink positioning reference measurements using the one or more sidelink positioning reference measurements; and receiving, in response to the measurement configuration, the one or more sidelink positioning reference measurements and the known location of the PRU; where the method is implemented in the positioning calculation entity; where the one or more sidelink positioning reference measurements include at least one of a timingbased reference measurement or an angular-based reference measurement; where the one or more sidelink positioning reference measurements include at least one of a SL-RSTD reference measurement, a SL UE Rx-Tx time difference reference measurement, a SL ToF reference measurement, a ToA reference measurement, a SL-angle-of-arrival measurement, a SL TDoA reference measurement, a SL RTT reference measurement, or a SL AoA reference measurement; where the known location of the PRU includes one or more of 2D or 3D latitude and longitude information, height or altitude information, a velocity estimate, an antenna and panel related location information and reference points, or an uncertainty value or a confidence interval associated with the known location; where the method is implemented in a UE, and further comprises: transmitting, to the PRU, a request for the one or more sidelink positioning reference measurements and the known location of the PRU; and receiving, from the PRU in response to the request, the one or more sidelink positioning reference measurements and a known location of the PRU; where the method is implemented in a network entity, and further comprises: transmitting, to the PRU, a request for the one or more sidelink positioning reference measurements and the known location of the PRU; and receiving, from the PRU in response to the request, the one or more sidelink positioning reference measurements and a known location of the PRU; where the PRU includes a PRU ID that is at least one of a LI -ID derived from a L2-ID, a self-generated ID, or an application ID generated by a sidelink positioning application of the PRU, and where the method further comprises: receiving, from the PRU, the PRU ID with the one or more sidelink positioning reference measurements and the known location of the PRU; further including: transmitting, to the PRU, a request for capability information regarding the PRU acting as a sidelink positioning reference unit; and receiving, from the PRU in response to the request, capability information regarding the PRU acting as a sidelink positioning reference unit.

[0136] The processor 1806 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 1806 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 1806. The processor 1806 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1808) to cause the device 1802 to perform various functions of the present disclosure.

[0137] The memory 1808 may include random access memory (RAM) and read-only memory (ROM). The memory 1808 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1806 cause the device 1802 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 1806 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 1808 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.

[0138] The I/O controller 1814 may manage input and output signals for the device 1802. The I/O controller 1814 may also manage peripherals not integrated into the device 1802. In some implementations, the I/O controller 1814 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 1814 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 1814 may be implemented as part of a processor, such as the processor 1806. In some implementations, a user may interact with the device 1802 via the I/O controller 1814 or via hardware components controlled by the I/O controller 1814.

[0139] In some implementations, the device 1802 may include a single antenna 1816. However, in some other implementations, the device 1802 may have more than one antenna 1816, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The receiver 1810 and the transmitter 1812 may communicate bi-directionally, via the one or more antennas 1816, wired, or wireless links as described herein. For example, the receiver 1810 and the transmitter 1812 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 1816 for transmission, and to demodulate packets received from the one or more antennas 1816.

[0140] FIG. 19 illustrates a flowchart of a method 1900 that supports sidelink anchor device management in accordance with aspects of the present disclosure. The operations of the method 1900 may be implemented and performed by a device or its components, such as a configuration entity as described with reference to FIGs. 1 through 18. 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.

[0141] At 1902, the method may include transmitting a sidelink positioning capability request to one or more sidelink devices as potential sidelink anchor devices. The operations of 1902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1902 may be performed by a device as described with reference to FIG. 1.

[0142] At 1904, the method may include receiving, from the one or more sidelink devices, anchor device capability information and a location of the respective sidelink devices. The operations of 1904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1904 may be performed by a device as described with reference to FIG. 1.

[0143] At 1906, the method may include selecting at least one of the sidelink devices as an anchor device based on the anchor device capability information and the location of the sidelink device. An implementation may include selecting the at least one sidelink device as the anchor device based on receiving one or more sidelink measurements from the sidelink device and the location of the sidelink device. The operations of 1906 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1906 may be performed by a device as described with reference to FIG. 1.

[0144] At 1908, the method may include transmitting a sidelink positioning reference signal transmission configuration to the anchor device establishing a sidelink positioning session with a target device. The operations of 1908 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1908 may be performed by a device as described with reference to FIG. 1.

[0145] FIG. 20 illustrates a flowchart of a method 2000 that supports sidelink anchor device management in accordance with aspects of the present disclosure. The operations of the method 2000 may be implemented and performed by a device or its components, such as a configuration entity as described with reference to FIGs. 1 through 18. 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.

[0146] At 2002, the method may include receiving, from a network device, a candidate list of the potential sidelink anchor devices. The operations of 2002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2002 may be performed by a device as described with reference to FIG. 1. [0147] At 2004, the method may include selecting the anchor device based on a link quality between each of the potential sidelink anchor devices. The operations of 2004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2004 may be performed by a device as described with reference to FIG. 1.

[0148] At 2006, the method may include selecting the anchor device based on a coverage area of each of the potential sidelink anchor devices. The operations of 2006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2006 may be performed by a device as described with reference to FIG. 1.

[0149] At 2008, the method may include configuring the anchor device according to a UE-based UE-configured anchor device configuration, a UE-based network-configured anchor device configuration, a UE-assisted UE-configured anchor device configuration, or a UE-assisted network- configured anchor device configuration. The operations of 2008 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2008 may be performed by a device as described with reference to FIG. 1.

[0150] At 2010, the method may include receiving, from the anchor device, a status indication that the anchor device is operably configured as the anchor device or is no longer operable as the anchor device. The operations of 2010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2010 may be performed by a device as described with reference to FIG. 1.

[0151] FIG. 21 illustrates a flowchart of a method 2100 that supports sidelink anchor device management in accordance with aspects of the present disclosure. The operations of the method 2100 may be implemented and performed by a device or its components, such as an anchor device as described with reference to FIGs. 1 through 18. 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.

[0152] At 2102, the method may include receiving, from a configuration device, a sidelink positioning capability request. The operations of 2102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2102 may be performed by a device as described with reference to FIG. 1.

[0153] At 2104, the method may include transmitting, to the configuration device, anchor device capability information and a location. The operations of 2104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2104 may be performed by a device as described with reference to FIG. 1.

[0154] At 2106, the method may include receiving, as a selected anchor device based at least in part on the anchor device capability information and the location, a sidelink positioning reference signal transmission configuration establishing a sidelink positioning session with one or more target devices. The operations of 2106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2106 may be performed by a device as described with reference to FIG. 1.

[0155] FIG. 22 illustrates a flowchart of a method 2200 that supports sidelink anchor device management in accordance with aspects of the present disclosure. The operations of the method 2200 may be implemented and performed by a device or its components, such as an anchor device as described with reference to FIGs. 1 through 18. 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.

[0156] At 2202, the method may include transmitting a sidelink positioning reference signal to the one or more target devices based on the location and mobility of the anchor device. The operations of 2202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2202 may be performed by a device as described with reference to FIG. 1.

[0157] At 2204, the method may include determining a location estimation of the configuration device. The operations of 2204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2204 may be performed by a device as described with reference to FIG. 1. [0158] At 2206, the method may include transmitting sidelink positioning configuration information to the one or more target devices participating in the sidelink positioning session. The operations of 2206 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2206 may be performed by a device as described with reference to FIG. 1.

[0159] At 2208, the method may include transmitting the anchor device capability information and the location to the one or more target devices participating in the sidelink positioning session. The operations of 2208 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2208 may be performed by a device as described with reference to FIG. 1.

[0160] At 2210, the method may include transmitting pre-defined assistance information to the one or more target devices participating in the sidelink positioning session. The operations of 2210 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2210 may be performed by a device as described with reference to FIG. 1.

[0161] At 2212, the method may include transmitting, to the configuration device, a status indication that the anchor device is operably configured as the anchor device or is no longer operable as the anchor device. The operations of 2212 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2212 may be performed by a device as described with reference to FIG. 1.

[0162] At 2214, the method may include transmitting, by the anchor device, time difference information with respect to itself and one or more additional anchor devices. The operations of 2214 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2214 may be performed by a device as described with reference to FIG. 1.

[0163] 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. [0164] 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.

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

[0166] 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 specialpurpose processor.

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

[0168] 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 orBC, 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.

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

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