Systems and methods for sidelink positioning enhancements

By introducing SL PRS and SCI, combined with high-level and low-level signaling, and adopting a resource allocation mechanism based on time slots and sub-channels, the problem of insufficient positioning accuracy in side-link communication is solved, and more efficient SL PRS resource utilization and improved positioning accuracy are achieved.

CN121844529APending Publication Date: 2026-04-10ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
ZTE CORP
Filing Date
2023-09-28
Publication Date
2026-04-10

AI Technical Summary

Technical Problem

In existing technologies, the positioning accuracy in sidelink communication is insufficient, making it impossible to effectively utilize sidelink resources for high-precision positioning, and there is a lack of effective resource allocation and coordination mechanisms.

Method used

By introducing Side Link Positioning Reference Signal (SL PRS) and Side Link Control Information (SCI), combined with higher and lower layer signaling, SL PRS transmission and resource allocation are realized. SL PRS resource allocation is performed at the granularity of time slots and sub-channels, supporting network-centralized and UE-autonomous resource allocation, congestion control and coordination, and improving positioning accuracy.

Benefits of technology

It improves positioning accuracy in sidelink communication, optimizes SL PRS resource utilization, achieves more efficient positioning and ranging, supports multiple positioning technologies and methods, and enhances the reliability and efficiency of sidelink positioning.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121844529A_ABST
    Figure CN121844529A_ABST
Patent Text Reader

Abstract

Systems and methods for sidelink positioning enhancements are presented. A first wireless communication device (e.g., a UE) may determine information regarding a sidelink positioning reference signal (SL PRS) transmission in response to the first wireless communication device receiving a positioning request. The first wireless communication device may transmit the SL PRS and sidelink control information (SCI) corresponding to the SL PRS based on the information on the SL PRS transmission.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, including but not limited to systems and methods for sidelink location enhancement. Background Technology

[0002] Sidelink (SL) communication refers to wireless radio communication between two or more User Equipment (UEs). In this type of communication, two or more geographically adjacent UEs can communicate without being routed to a Base Station (BS) or core network. Therefore, data transmission in SL communication differs from typical cellular network communication, which involves transmitting data to and from the BS (e.g., uplink transmission) and receiving data from the BS (e.g., downlink transmission). In SL communication, data is transmitted directly from the source UE to the target UE via, for example, a unified air interface (e.g., the PC5 interface), without going through the BS. Summary of the Invention

[0003] The exemplary embodiments disclosed herein relate to solving one or more problems presented in the prior art, and provide additional features that will readily become apparent when taken in conjunction with the accompanying drawings and the following detailed description. According to various embodiments, exemplary systems, methods, apparatuses, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and are not restrictive, and that various modifications can be made to the disclosed embodiments by those skilled in the art who have read this disclosure, while remaining within the scope of this invention.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A first wireless communication device (e.g., a UE) may, in response to receiving a positioning request, determine information regarding the transmission of a Sidelink Positioning Reference Signal (SL PRS). The first wireless communication device may, based on the information regarding the SL PRS transmission, transmit / send / provide / transmit / forward the SL PRS and corresponding Sidelink Control information (SCI).

[0005] In some implementations, the first wireless communication device may receive a location request from at least one of the following: a higher layer of the first wireless communication device; or a second wireless communication device. In some implementations, one or more wireless communication devices may receive / obtain / acquire an SCI and associated SL PRS resources from the second wireless communication device. The first wireless communication device may be one of one or more wireless communication devices. The SCI transmitted by the second wireless communication device may include at least one of the following: broadcast type; source ID; destination ID; and / or SL PRS request field.

[0006] In some implementations, the location request in the SCI transmitted by the second wireless communication device and the SL PRS resources transmitted by the second wireless communication device may share at least one of the following: the same broadcast type; the same source ID; and / or the same destination ID. In some implementations, the location request field in the SCI may be disabled in response to at least one of the following conditions: the SL PRS request field is not pre-configured, configured, or enabled in the resource pool; the broadcast type is indicated as broadcast; and / or the broadcast type is indicated as multicast.

[0007] In some implementations, the SCI may also include / contain a request ID. The request ID may be configured to indicate which of one or more wireless communication devices is requested to transmit SL PRS in response to a location request. In some implementations, the request ID may include at least one of the following: a UE ID indicated by a first higher layer; a source ID indicated by a second higher layer; and / or a member ID of a group broadcast case indicated by a third higher layer and representing a member in the group.

[0008] In some implementations, each of the first to third layers may be a Sidelink Positioning Protocol (SLPP) signaling and / or signaling sent from the application layer. In some implementations, each of the first to third layers may be configured to notify one or more wireless communication devices which wireless communication device is requested to transmit SLPP in response to a positioning request, and include SLPP transmission characteristics.

[0009] In some implementations, SL PRS transmission characteristics may include at least one of the following: location conditions; Quality of Service (QoS) conditions; SL PRS transmission priority of the target wireless communication device; SL PRS configuration; latency conditions; and / or UE ID. In some implementations, if the first wireless communication device and the second wireless communication device are in the same location session, and the first wireless communication device receives a location request from the second wireless communication device, the first wireless communication device may be configured to transmit SL PRS.

[0010] In some implementations, the selection or allocation of resources for SL PRS transmission from a first wireless communication device in the list of wireless communication devices receiving a location request may take into account UE information or group membership information. In some implementations, if the first wireless communication device is in SL PRS resource allocation scheme 2, the first wireless communication device may, in response to a location request, determine one or more SL PRS resource IDs for transmitting SL PRS, taking into account the maximum number of SL PRS resources configured or pre-configured in the resource pool and the UE information or group membership information.

[0011] In some implementations, if the first wireless communication device is in SL PRS resource allocation scheme 2, the first wireless communication device can determine one or more SL PRS resource pool IDs for transmitting SL PRS in response to a location request. In some implementations, the second wireless communication device can use the Side Link Positioning Protocol (SLPP) to recommend or configure different SL PRS features for the first wireless communication device or one or more other wireless communication devices.

[0012] In some implementations, the first wireless communication device may, in response to receiving a location request from the second wireless communication device, transmit / send SL PRS in a unicast, multicast, and / or broadcast manner. The destination of the SL PRS transmission may be configured or pre-configured to include the second wireless communication device. In some implementations, the first wireless communication device may determine to transmit SL PRS on a shared resource pool. Information regarding the SL PRS transmission may include at least one of the following: time resources; frequency resources; SL grant; priority; source ID; destination ID; resource pool ID; bandwidth; sidelink channel occupancy ratio (SL CR) limit; maximum transmission power; SL PRS resource ID; and / or resource reservation interval.

[0013] In some implementations, the first wireless communication device may determine one or more SL PRS transmission parameters based on one or more delay budgets. In some implementations, the one or more delay budgets may each include the remaining delay budget of the SL PRS and the remaining packet delay budget (PDB) of the SL data available in the logical channel, or a unified delay budget. The unified delay budget may be the minimum value between the remaining delay budget of the SL PRS and the remaining PDB of the SL data available in the logical channel.

[0014] In some implementations, information regarding SL PRS transmissions may be related to both the PSSCH transmission parameter list and the SL PRS transmission parameter list. In some implementations, the SL PRS transmission parameter list may be associated with the priority of SL PRS transmissions and Channel Busy Ratio (CBR) measurements.

[0015] In some implementations, the PSSCH transmission parameter list may be associated with the priority of the PSSCH transmission and CBR measurements. In some implementations, information regarding SL PRS transmissions may be associated with at least one of the following: the priority of the SL PRS; the priority of the logical channel used for SL data; the remaining delay budget of the SL data available in the logical channel; and / or the delay budget of the SL PRS.

[0016] In some implementations, the first wireless communication device may select a destination associated with one of unicast, multicast, and / or broadcast that has the highest priority among the priority of the logical channel used for SL data and the priority of the SL PRS for the SCI corresponding to the SL PRS transmission. In some implementations, the first wireless communication device may transmit the SL PRS when there is an SL PRS to be transmitted at the selected destination and the SL PRS to be transmitted meets at least one constraint. The at least one constraint may include at least one of the following: the SL PRS to be transmitted has the highest priority; the SL PRS to be transmitted has the lowest latency budget; and / or the SL PRS to be transmitted in response to a single location request has not been transmitted more than N times or for more than a certain duration.

[0017] In some embodiments, the third wireless communication device may receive SLPRS transmitted by the first wireless communication device. The third wireless communication device may send an indication of at least one of relative distance, angle, or resource pool ID in the location information report. In some embodiments, the first wireless communication device may perform partial sensing to select available resources for SL PRS transmission. At least one of the following may be included: partial sensing may be performed during the inactive time of SL Discontinuous Reception (DRX) based on resource pool configuration; an SL PRS Received Signal Strength Indicator (RSSI) may be used to measure the Channel Busy / Idle Rate (CBR) in the SLPRS resources where the first wireless communication device performs partial sensing; and / or CBR may be used if a threshold is not met, wherein the threshold is calculated by the number of SL PRS resources in the CBR window.

[0018] In some implementations, the first wireless communication device may transmit SL PRS in an unlicensed frequency band. The selection of the cyclic prefix extension (CPE) start position or CPE length may be associated with a priority value for SL PRS transmission.

[0019] In some implementations, a third wireless communication device may receive and measure the SL PRS from one or more other wireless communication devices. The third wireless communication device may perform (or complete) one or more SL PRS measurements during a measurement period, wherein at least one of the following is true: the first wireless communication device may be one of one or more other wireless communication devices; the third wireless communication device may receive a location information request from another wireless communication device or network function via Side Link Positioning Protocol (SLPP) signaling; and / or the third wireless communication device may receive auxiliary data from another wireless communication device or network function via SLPP signaling for measuring the SL PRS.

[0020] In some implementations, the measurement period may be associated with at least one of the following: Quality of Service (QoS) conditions (or requirements); one or more latency budgets for SL PRS transmissions; one or more selection window sizes; one or more periods for SL positioning (configured grant (CG); one or more resource reservation periods for SL PRS; the maximum number of active SL PRS resources processed by one or more wireless communication devices across configured resource pools within a duration; and / or the maximum number of (pre)configured SL PRS resources across configured resource pools within a duration. Attached Figure Description

[0021] Various exemplary embodiments of the present solution are described in detail below with reference to the following figures or drawings. These figures are provided for illustrative purposes only and depict only exemplary embodiments of the present solution to facilitate the reader's understanding of the solution. Therefore, the figures should not be considered as limitations on the breadth, scope, or applicability of the present solution. It should be noted that these figures are not necessarily drawn to scale for clarity and ease of explanation.

[0022] Figure 1 An example cellular communication network that implements the techniques disclosed herein is shown according to embodiments of the present disclosure; Figure 2 Block diagrams of example base station and user equipment apparatuses according to some embodiments of the present disclosure are shown; Figure 3 Example descriptions of the transmission of side link control information (SCI) 1 and SCI 2 according to some embodiments of this disclosure are shown; and Figure 4 A flowchart is shown of an example method for sidelink localization enhancement according to some embodiments of the present disclosure. Detailed Implementation

[0023] 1. Mobile communication technology and environment Figure 1 An example wireless communication network and / or system 100 implementing the techniques disclosed herein is illustrated according to embodiments of this disclosure. In the following discussion, wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes base stations 102 (hereinafter referred to as "BS 102", also called wireless communication nodes) and user equipment 104 (hereinafter referred to as "UE 104", also called wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0024] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which can include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes," which typically practice the methods disclosed herein. According to various embodiments of this scheme, such communication nodes can be capable of wireless and / or wired communication.

[0025] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., Orthogonal Frequency Division Multiplexing (OFDM) / Orthogonal Frequency Division Multiplexing Access (OFDMA) signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative embodiment, system 200 may be used in a wireless communication environment (e.g., as described above). Figure 1 In a wireless communication environment 100, communication (e.g., sending and receiving) data symbols.

[0026] The system 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (Base Station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for the data transmission described herein.

[0027] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any feasible combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described in general terms of their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art described herein can implement such functionality in a suitable manner for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0028] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each of which includes circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that while the downlink transmitter is coupled to downlink antenna 212, the uplink receiver circuitry is coupled to uplink antenna 232 to receive transmissions via wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time, such that while the uplink transmitter is coupled to the uplink antenna 232, the downlink receiver is coupled to the downlink antenna 212 to receive transmissions via the wireless transmission link 250. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0029] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards (e.g., Long Term Evolution (LTE) and emerging 5G standards). However, it should be understood that this disclosure is not necessarily limited to application to a specific standard and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0030] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, UE 204 may be implemented in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The processor may be implemented in this way as a microprocessor, controller, microcontroller, or state machine, etc. The processor may also be implemented as a combination of multiple computing devices, such as a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors incorporating a digital signal processor core, or any other combination of such configurations.

[0031] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Memory modules 216 and 234 can be implemented as random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, removable disks, read-only optical discs (CD-ROMs), or any other form of storage medium known in the art. In this respect, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0032] Network communication module 218 broadly represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or Global Microwave Access Interoperability (WiMAX) services. In a typical deployment, but without limitation, network communication module 218 provides an 802.3 Ethernet interface, enabling base station transceiver 210 to communicate with conventional Ethernet-based computer networks. Thus, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and their various variations, used herein with respect to a specified operation or function, refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0033] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and efficiently describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is another layer.

[0034] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to create and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0035] 2. Systems and methods for improving the accuracy of side-link positioning enhancement In some systems, for the allocation of physical sidelink control channel (PSCCH) and / or physical sidelink shared channel (PSSCH) resources in SL communication, the time granularity can be time slots, and subchannels can be defined as PSSCH frequency resource units, where the size of the subchannels can be configured per resource pool. In some cases, the SL channel busy-idle ratio (CBR) and SL channel occupancy ratio (SL CR) used for SL congestion control can be defined based on the subchannel busy-idle ratio or subchannel occupancy ratio. However, for SL positioning, the SL PRS allocation granularity can apply time slot-based and / or subchannel-based SL PRS resource allocation, sub-time slot-based SL PRS resource allocation, and / or SL PRS resource-based allocation. For example, unlike the PSCCH and / or PSSCH resource allocation in SL communication (where the time granularity is time slot-based and the frequency granularity is subchannel-based), SL PRS resources and / or SL PRS resource sets can be defined and used as the resource allocation granularity.

[0036] In some configurations, aspects supporting sidelink positioning may include / involve, for example, the design of a sidelink positioning reference signal (SL PRS), the measurement and reporting of SL positioning based on various positioning technologies or methods (e.g., round trip time (RTT), time difference of arrival (TDOA), angle-based positioning methods, etc.), and / or resource allocation for SL PRS (e.g., based on at least one or both of a dedicated resource pool and / or a shared resource pool for SL PRS, and / or at least one or both of resource allocation scheme 1 and scheme 2, etc.). Regarding SLPRS resource allocation, at least one or both of scheme 1 (e.g., network-centralized SL PRS resource allocation) and / or scheme 2 (e.g., UE-autonomous SL PRS resource allocation) may be introduced or implemented to support SL positioning and / or ranging.

[0037] In some other aspects, congestion control for SL positioning and inter-UE coordination (IUC) can be configured or designed based on the mechanism of SL PRS sequence configuration. In various implementations, the systems and methods of the technical solutions discussed herein can provide signaling features or operations for sidelink positioning enhancement. In some configurations, UE 104 can be a user's equipment, vehicle, roadside unit (RSU), positioning reference unit (PRU), or other equipment capable of supporting vehicle-to-everything (V2X) services and / or SL communication. UE 104 may or may not have a known location.

[0038] Example Implementation Method 1: Triggering SL PRS In various configurations, to trigger an SL PRS transmission for UE 104 (e.g., UE-B), at least the following example operations can be considered. For example, the higher layers of UE 104 (e.g., UE-B) can trigger an SL PRS transmission at the physical layer. In another example, another UE (e.g., UE-A) can trigger an SL PRS transmission for UE 104 (e.g., UE-B). In various cases, the signaling can be low-layer signaling (e.g., SL PRS signaling, Side Link Control Information (SCI) signaling, Medium Access Control Element (MAC CE) signaling, etc.), high-layer signaling (e.g., Side Link Positioning Protocol (SLPP) signaling, etc.), or both high-layer and low-layer signaling. In some cases, for the two examples used to trigger an SL PRS transmission, the higher layers of UE-B can determine / decide whether to trigger an SL PRS transmission. As discussed herein, depending on the configuration, UE 104 can refer to UE-A or UE-B, as well as other UEs discussed herein. In some implementations, UE-B may correspond to a first UE (e.g., a first wireless communication device), while UE-A may correspond to a second UE (e.g., a second wireless communication device), and vice versa.

[0039] Example Configuration 1.1: SCI-triggered Destination In various implementations, when the UE-B SL PRS transmission is triggered by the UE-A, at least one of the following example operations / methods should be supported: 1. UE-A can transmit / send / provide an SCI and associated SL PRS. The SCI can be at least one of the following: SCI 1-B used in a dedicated resource pool; and / or SCI 1-A and / or SCI 2-D used in a shared resource pool. The SCI may include an "SL PRS Request" field to trigger one or more other UE 104 SL PRS transmissions. The SCI may include at least one of the following: a broadcast type indicator (e.g., indicating whether the UE-A's transmission is broadcast, multicast, or unicast); a source ID; a destination ID, etc.

[0040] 2. UE-B can be the transmission destination of UE-A. UE-B can receive an "SL PRS request" from UE-A. Subsequently, the higher layers of UE-B can respond to the request from UE-A to transmit SL PRS.

[0041] During the example operations / procedures described above, the SL PRS request transmitted by UE-A and the SL PRS transmission of UE-A can share broadcast type, source ID, and / or destination ID, etc. For example, if the broadcast type of the SL PRS transmission of UE-A is unicast, then a UE-B can receive the "SL PRS request" from that UE-A. In another example, if the broadcast type of the SL PRS transmission of UE-A is multicast, then a group of one or more UE-Bs can transmit SL PRS in response to each UE-B receiving an SL PRS request from that UE-A. In yet another example, if the broadcast type of the SL PRS transmission of UE-A is broadcast, then any one of one or more UE-Bs can receive the SL PRS request. In this case, for example, in response to UE-B successfully decoding UE-A's SCI and SL PRS, UE-B can transmit SL PRS in response to UE-A's SL PRS request.

[0042] In some implementations, for use cases involving SL PRS transmissions triggered by another UE 104, a unicast SL PRS request can be used in the SL RTT method or configuration, which can involve SL PRS transmission round trips between two UEs 104. One or more of the following example conditions / criteria can be met to disable the “SL PRS Request” field in the SCI: The "SL PRS Request" field in SCI may not be (pre) configured or activated / enabled in the resource pool; The broadcast type indicator in SCI can indicate broadcast; and / or The broadcast type indicator in SCI can indicate multicast.

[0043] For example, when the broadcast type is not broadcast and the “SL PRS Request” field in the SCI is configured or activated / enabled in the resource pool, the “SL PRS Request” field can be (or retained) enabled. Otherwise, the UE-B can ignore or disregard the “SL PRS Request” field. If the “SL PRS Request” field in the SCI is configured in the resource pool, but the broadcast type is broadcast, the field (e.g., the “SL PRS Request” field) can be retained.

[0044] In another example, the "SL PRS Request" field can be enabled when the broadcast type is unicast and the "SL PRS Request" field in the SCI is configured in the resource pool. Otherwise, the UE-B can ignore or skip the "SL PRS Request" field. If the "SL PRS Request" field in the SCI is configured in the resource pool, but the broadcast type is not unicast, the field can be retained.

[0045] Example Configuration 1.2: SCI-triggered Destination In some implementations, the SL PRS request transmitted by UE-A and the SL PRS transmission of UE-A may not share the same broadcast type, source ID and / or destination ID, and other information. For example, not all one or more UE-Bs that are matched receivers of SL PRS transmissions from UE-A (e.g., not all UE-Bs receiving SL PRS transmissions) can be configured to respond to an "SL PRS request". In this case, one or more of the following example features may be supported: The SCI may include a "Request ID" field. In this case, the Request ID can be used to indicate a specific UE-B or member UE-B that can transmit SL PRS in response to a request in a multicast or broadcast SL PRS transmission from UE-A. For example, other UEs 104 receiving the SL PRS request from UE-A may not need to trigger their own SL PRS transmissions.

[0046] - The requested ID may include or correspond to a member ID in multicast. The member ID may be indicated by at least one higher-layer signaling. For example, a member ID may be configured for each SLPP session. For example, for an SLPP session, different UEs 104 may have the same destination ID (e.g., multicast and / or broadcast) indicated by different member IDs.

[0047] - The requested ID can be a UE ID, which can be indicated by at least one higher-layer signaling. For example, a UE ID can be configured for each SLPP session. In this case, for an SLPP session, different UEs 104 can have the same destination ID (e.g., multicast or broadcast) indicated by different UE IDs. For multicast or broadcast, the UE ID can be a source ID indicated by higher-layer signaling. Server UEs (e.g., UEs supporting at least one of, but not limited to, the following example functions: location method determination; anchor UE selection; auxiliary data distribution; and / or location calculation), location management functions (LMFs) (e.g., network functions), and / or higher layers (e.g., application layer) and other devices can assign source IDs to UE 104. In some cases, the anchor UE and / or the target UE can be a server UE. In this case, for example, the source ID of UE 104 may not be selected by UE 104 itself, because other UEs 104 can select the same source ID themselves.

[0048] In some cases, the additional “broadcast type indicator”, “source ID” and / or “destination ID” can be used specifically for SL PRS requests in SCI.

[0049] Higher-layer participation can be supported without using SCI. For example, higher-layer interactions between UEs 104 can be supported to notify UE 104 which UE among UEs 104 responded to the request, and SL PRS transport features can be provided for UE-B. Higher-layer signaling can include, but is not limited to, SLPP signaling.

[0050] - Via / through SLPP, UE-A may provide UE-B with at least one of the following example information or conditions: location conditions; Quality of Service (QoS) (e.g., horizontal accuracy, vertical accuracy, response time, speed request, SL PRS latency budget, priority, etc.); priority; SL PRS transmission priority of the target UE; other SL PRS configurations (e.g., symbol count, comb size, comb offset, bandwidth, sequence ID, SL PRS resource ID, resource pool ID, shared resource pool and / or dedicated resource pool); latency conditions (e.g., UE-B may transmit SLPRS within a certain period after receiving an SCI with an SL PRS request); the requested UE ID, etc.

[0051] In some implementations, one or more UEs 104 may be triggered to transmit SL PRS by receiving one or more of the above information and SCI triggers (e.g., SL PRS requests in SCI). For example, in the case of multicast, group members receiving / obtaining higher-layer information (e.g., a group of one or more UEs 104) may be triggered.

[0052] - For example, if one or more UE-Bs do not have a signaling unicast link with UE-A (e.g., an SLPP unicast link), but receive SCI triggers, then the one or more UE-Bs may not be configured to transmit SL PRS.

[0053] In some cases, if UE-A and UE-B (e.g., a first wireless communication device and a second wireless communication device) are in the same location session, and UE-B receives an SCI trigger from UE-A, UE-B may transmit SL PRS in response to a request from UE-A. For example, UE-A and UE-B may share the same SLPP session ID, and / or UE-A and UE-B may be involved in or associated with the same location service (LCS) request. UE-B's SL PRS transmission may follow the SL PRS configuration in the SLPP session (e.g., SL PRS auxiliary data).

[0054] Example Configuration 1.3: Potential Management of a List of One or More UE-Bs Receiving SL PRS Requests If multicast or broadcast SCI-triggered SL PRS requests are supported, in certain scenarios, a group of one or more UE-Bs can select / pick the same SL PRS resource on the same time-frequency resource. In this case, potential conflicts may occur due to UE-A's SCI-triggered SL PRS requests. To mitigate potential conflicts, one or more of the following example operations or features can be supported: 1. You can configure / set certain rules to mitigate potential resource conflicts.

[0055] - In some cases, in response to the same SL PRS request from UE-A, SL PRS transport lists from one or more UE-Bs may share at least one of the following example conditions / standards: for example, SL PRS priority; bandwidth; SL PRS resource ID; number of symbols and / or resource pool index.

[0056] Resource selection / allocation of UE-Bs from a list of one or more UE-Bs that have received SL PRS requests may take into account UE information and / or group membership information (e.g., taking into account UE information and / or group membership information).

[0057] A UE-B from a list of one or more UE-Bs receiving an SL PRS request may select / pick different SL PRS resources, either by considering or based on UE ID information (e.g., U_ID). The UE ID information may be a source ID from / via higher-layer signaling and / or a UE ID. A UE-B may select its own source ID, or in some cases, at least one of the server UE, LMF, and / or higher-layer (e.g., application layer) may assign a source ID to the UE-B.

[0058] A UE-B from a list of one or more UE-Bs receiving an SL PRS request can consider group membership information M_ID to select different SL PRS resources, where the member ID can be indicated by a higher layer. For example, a member ID can be configured for each SLPP session. For example, for an SLPP session, different member IDs can be used to indicate different UEs 104 with the same destination ID (e.g., multicast or broadcast).

[0059] If UE-B is in SL PRS resource allocation scheme 2, UE-B can, in response to an SCI-triggered SLPRS request, determine one or more SL PRS resource IDs for SL PRS transmission as U_ID mod N_(SL PRS), M_ID mod N_(SL PRS), and / or (U_ID + M_ID) mod N_(SL PRS), where N_(SL PRS) can be the total number of configured / pre-configured SL PRS resources in the resource pool. In this case, different UEs 104 can perform sensing on different SL PRS resources.

[0060] In another example, if UE-B is in SL PRS resource allocation scheme 2, different UE-Bs can avoid resource conflicts by transmitting SL PRS in different resource pools. For example, if N_pool can be the total number of configured transmission resource pools (e.g., a dedicated resource pool, a shared resource pool, and both), then UE-B can, in response to an SCI-triggered SL PRS request, determine one or more SLPRS resource IDs for SL PRS transmission as U_ID mod N_pool, M_ID mod N_pool, and / or (U_ID + M_ID) mod N_pool.

[0061] If UE-B is in SL PRS resource allocation scheme 1, UE-B can decide or determine to transmit SL PRS in response to an SL PRS request. Since UE 104 (e.g., UE-B) has SL PRS to transmit, UE 104 can send / transmit / transmit a UL RRC message to BS 102 (e.g., gNB or TRP) to request a configuration grant (CG) or send a UL BSR MACCE to request a dynamic grant (DG). The request signaling from UE 104 to BS 102 can include at least the following: one or more selected resource pool indices; one or more selected SL PRS resource IDs; a destination ID; an SL PRS priority; and / or a buffer size, etc. For example, the resource pool index or SL PRS resource ID selected by UE 104 can follow or conform to the same rules as in resource allocation scheme 2. For example, if BS 102 receives multiple ULMAC CE requests from multiple UEs 104 (where these requests share the same destination and priority), BS 102 can allocate different resources to different UEs 104 (e.g., SL PRS resources, SL PRS resource pools, time resource allocation, frequency resource allocation, and / or CG index, etc.).

[0062] Additionally or alternatively, frequency domain, time domain, and / or time slot offsets. For example, timing offsets may exist between different UE-Bs. The unit of timing offset may be at least one of time slot, symbol, and / or millisecond (ms) or other units.

[0063] 2. In some cases, high-level signaling can be used to mitigate potential resource conflicts.

[0064] For example, UE-A can use SLPP to recommend or configure different SL PRS features for one or more different UE-Bs. SL PRS features may include, but are not limited to, at least one of the following: SL PRS resource ID; resource pool index; comb size; comb offset; number of symbols in a slot; priority; SL PRS transmission slot; SL PRS transmission slot list; bitmap of SL PRS time-domain resources; and / or window for SL PRS transmission.

[0065] -High-level configurations or recommended use cases can be constrained or limited to multicast, broadcast, or a combination of multicast and broadcast.

[0066] Example Configuration 1.4: SL PRS Transmission Target for UE-B In various implementations, UE-B can receive an SCI-based SL PRS trigger from UE-A. In some cases, UE-B can determine to transmit the SL PRS accordingly. In such cases, one or more of the following example scenarios or features can be considered or applied: UE-B can send / transmit SL PRS to UE-A in response to a request from UE-A.

[0067] In response to a request from UE-A (including, for example, source ID, destination ID, and / or broadcast type), UE-B's transmission may be dependent on itself. In this case, UE-A may not be one of the destinations for UE-B's various SL PRS transmissions.

[0068] UE-B can respond to a request from UE-A by transmitting SL PRS in unicast, multicast, or broadcast configuration. The destination of SL PRS transmission from UE-B can include UE-A. In this case, UE-B can have relatively limited flexibility considering the transmission target of SL PRS.

[0069] Example Implementation Method 2: Shared Resource Pool MAC Configuration or Design In various configurations, for SL PRS transmissions in dedicated resource pools and / or shared resource pools, at least one of the following example operations / methods or procedures involving the MAC layer of UE 104 can be configured: 1. UE 104 can receive / obtain SL PRS transmission requests. UE 104 can receive requests from LMF and / or server UE and other network devices via SLPP signaling (or other higher-layer signaling), or UE 104 can receive requests from its own higher layers (e.g., application layer).

[0070] 2. An SL license for SL PRS transmission can be obtained. The following options can be considered: -SL PRS Resource Allocation Scheme 1: UE 104 can request SL authorization from BS 102. For example, UE 104 can send a UL RRC message to BS 102 to request configuration authorization (CG). UE 104 can send a UL MAC CE message to BS 102 to request dynamic authorization (DG).

[0071] -SL PRS resource allocation scheme 2: UE 104 can autonomously (e.g., automatically) select SL authorization (or other types of authorization).

[0072] 3. SL transmission information can be determined, and the SL transmission information can be associated with a selected (e.g., scheme 2) or indicated grant (e.g., scheme 1). In this case, UE 104 can transmit the SL PRS and associated SCI based on the SL grant.

[0073] Example Configuration 2.1: Packet Latency Budget (PDB) In various implementations, the latency budget of SL PRS or SL data may affect the MAC layer of UE 104 in making resource or grant selections. For example, this effect may include at least one of the following: the selection of a resource reservation interval may be associated with the remaining latency budget; in scenarios involving sense-based resource selection, random selection, HARQ retransmission, preemption, and / or reassessment, the MAC layer of UE 104 may randomly select time and frequency resources based on the latency budget; and / or the latency budget may be one of the factors that could lead to a Tx resource reselection check or confirmation.

[0074] In SL communication, each Quality of Service (QoS) can be associated with a Packet Delay Budget (PDB). For resource allocation mode 2, the MAC layer can select time and frequency resources for a transmission opportunity from the resource pool (e.g., randomly or selectively) based on the remaining PDB. For SL PRS resource selection or reselection, a delay budget for the SL PRS can be introduced, which can be associated with a location service condition. Subsequently, considering that SL PRS and SL data can be transmitted in a shared resource pool, how to determine the delay budget in that pool can be taken into account. For example, SL PRS and SL data can share the same SL license. In this case, one or more of the following example operations can be applied or implemented: A uniform delay budget can be defined by considering the delay budget of the SL PRS and the PDB of the SL data available in one or more logical channels. In some cases, a residual uniform delay budget can be defined by considering the residual delay budget of the SL PRS and the residual PDB of the SL data available in one or more logical channels.

[0075] - The remaining uniform delay budget can be the minimum between the remaining PDB of the SL data and the remaining SL PRS delay budget.

[0076] - The unified latency budget can be the minimum between the PDB of the SL data and the latency budget of the SL PRS.

[0077] - The MAC entity can select the following value for the resource reservation interval: this value is relatively greater than the remaining uniform latency budget.

[0078] - For random resource selection, time and frequency resources can be selected from the resource pool for a transmission opportunity (e.g., randomly) based on the remaining uniform delay budget.

[0079] - For sensing-based resource selection, time and frequency resources can be selected for a transmission opportunity (e.g., randomly) from resources indicated by the physical layer, based on the remaining uniform delay budget.

[0080] - If one or more HARQ retransmissions are selected, time and frequency resources can be selected from the resource pool for a transmission opportunity (e.g., randomly) based on the remaining uniform delay budget and the selected number of HARQ retransmissions.

[0081] - For preemption or reassessment, time and frequency resources can be selected from the resources indicated by the physical layer for removed or discarded resources (e.g., randomly) based on the selected number of HARQ retransmissions and the remaining uniform delay budget.

[0082] - If one or more transmissions with the selected sidelink grant cannot achieve / comply / satisfy the remaining uniform delay budget, and the MAC entity selects or determines not to execute one or more transmissions corresponding to a single MAC PDU, then the sidelink grant can be cleared / removed / dropped if the selected sidelink grant associated with the sidelink procedure is available or selected. In some cases, one or more transmission (TX) resources can be (re)selected.

[0083] 3. If the remaining uniform delay budget is not met, the UE implementation can determine whether to execute one or more transmissions corresponding to a single MAC PDU or to perform sidelink resource reselection.

[0084] In some cases, instead of defining a uniform delay budget or a uniform residual delay budget, the selection and / or (re)selection check of SL authorization can at least take into account the residual delay budget of the SL PRS and the residual PDB of the SL data.

[0085] - If there are SL PRS to be transmitted, the SL grant selection and (re)selection checks can take into account the remaining delay budget of the SL PRS.

[0086] - The MAC entity can select the following value for the resource reservation interval: This value can be relatively greater than the remaining delay budget of the SL PRS and the remaining PDB of the SL data (if the SL data is transmitted / sent).

[0087] - For random resource selection, time and frequency resources can be selected from the resource pool for a transmission opportunity (e.g., randomly) based on the remaining delay budget of the SL PRS and the remaining PDB of the SL data (if the SL data is transmitted).

[0088] - For sensing-based resource selection, time and frequency resources can be selected from the resources indicated by the physical layer for a transmission opportunity (e.g., randomly) based on the remaining delay budget of the SL PRS and the remaining PDB of the SL data (if the SL data is transmitted).

[0089] - If one or more HARQ retransmissions are selected, time and frequency resources can be selected from the resource pool for a transmission opportunity (e.g., randomly), for example, based on the remaining delay budget of the SL PRS and the remaining PDB of the SL data (if the SL data is being transmitted) and the selected number of HARQ retransmissions.

[0090] - For preemption or reassessment, time and frequency resources can be selected from the resources indicated by the physical layer for resources to be removed or discarded (e.g., randomly), for example, based on the number of HARQ retransmissions selected and the remaining delay budget of the SL PRS and the remaining PDB of the SL data (if SL data is transmitted).

[0091] - If one or more transmissions with the selected sidelink grant do not meet the remaining delay budget of the SL PRS and the remaining PDB of the SL data (if the SL data is being transmitted), and the MAC entity chooses not to execute one or more transmissions corresponding to a single MAC PDU, then the sidelink grant can be cleared if the selected sidelink grant associated with the sidelink procedure is available. Therefore, a (re)selection of TX resources can be triggered / initiated.

[0092] - In some cases, if the remaining delay budget of the SL PRS and the remaining PDB of the SL data (if the SL data is transmitted) are not met, the UE 104 may determine whether to perform one or more transport and / or sidelink resource reselections corresponding to a single MAC PDU.

[0093] Example Configuration 2.2: Frequency Domain Allocation For shared resource pools in SL positioning, multiple scenarios can be considered, including but not limited to: SL PRS transmitted on the shared resource pool; SL data transmitted on the shared resource pool; and SL data and SLPRS transmitted on the shared resource pool. In some cases, for shared resource pools, a single priority value can be provided from higher layers to the physical layer, for example, when SL PRS and PSSCH are multiplexed in the same time slot of the shared resource pool.

[0094] Based on (pre)configuration, for transmission priority, a list of PSSCH transmission parameters and / or a list of SL PRS transmission parameters can be defined / configured / provided based on CBR measurements. Example configurations can be provided, but are not limited to the following:

[0095] In various cases, if SL PRS is transmitted over a shared resource pool, frequency resources can be selected based on or against a list of SL PRS transmission parameters associated with priority and CBR measurements (e.g., the minimum and / or maximum number of sub-channels that can be used for SLPRS transmission).

[0096] If SL data is transmitted on a shared resource pool, frequency resources can be selected based on the default SL data transmission configuration associated with priority (e.g., the minimum and / or maximum number of sub-channels that can be used for PSSCH transmission).

[0097] If SL PRS and SL data are transmitted on a shared resource pool, a list of PSSCH transmission parameters and a list of SL PRS transmission parameters associated with priority and CBR measurements can be provided. Transmission parameters in the shared resource pool may include at least one of the following: maximum number of PSSCH or SL PRS transmissions; maximum transmission power; minimum and maximum modulation and coding scheme (MCS) values ​​for transmission; minimum and maximum number of sub-channels; and / or CR limits, etc.

[0098] In some implementations, at least one of the following features or operations may be implemented or applied: SL licensing can be selected based on the PSSCH transmission parameter list and the SL PRS transmission parameter list. In some cases, the bandwidth of SL PRS can be the same as that of PSSCH. The transmission power of SL PRS can be the same as that of PSSCH.

[0099] The intersection of two frequency domain ranges (e.g., the minimum and maximum number of subchannels) can be obtained from the PSSCH transmission parameter list and / or the SL PRS transmission parameter list.

[0100] The juxtaposition of two frequency domain ranges (e.g., the minimum and maximum number of subchannels) can be obtained from the PSSCH transmission parameter list and the SL PRS transmission parameter list.

[0101] The maximum number between the maximum transmission power of SL PRS and the maximum transmission power of PSSCH can be obtained.

[0102] The minimum value between the maximum transmission power of SL PRS and the maximum transmission power of PSSCH can be obtained.

[0103] The maximum number between the CR limit of SL PRS and the CR limit of PSSCH can be obtained.

[0104] The minimum value between the CR limit of SL PRS and the CR limit of PSSCH can be obtained.

[0105] The intersection of two MCS ranges (e.g., the minimum and maximum number of MCS values) can be obtained from the PSSCH transmission parameter list and the SL PRS transmission parameter list.

[0106] The juxtaposition of two MCS domain ranges (e.g., the minimum and maximum number of MCS values) can be obtained from the PSSCH transfer parameter list and the SL PRS transfer parameter list.

[0107] In some cases, when selecting SL authorization, UE 104 may consider the SL PRS transport parameter list or the PSSCH transport parameter list.

[0108] In some cases, based on the PSSCH transmission parameter list and the SL PRS transmission parameter list, UE 104 can determine how to select the appropriate SL grant. For example, UE 104 can be configured with appropriate technology to determine how to select the appropriate SL grant.

[0109] By configuring (e.g., pre-configuring), the default PSSCH transport configuration and the default SL PRS transport configuration can be defined / configured / set for transport priorities if CBR measurements are unavailable or invalid.

[0110] Additionally or alternatively, for shared resource pools, if there is no defined (e.g., default or affected by CBR measurement and priority) dedicated list of SL PRS parameters, one or more of the following example operations or characteristics may be applied or considered: If SL data is being transferred in a shared resource pool, the choice of SL authorization can take into account (e.g., the default or a list of PSSCH parameters influenced by CBR measurements and priorities).

[0111] If SL PRS is being transmitted in a shared resource pool, and no SL data is being transmitted in the same time slot, one or more of the following examples can be applied: - If there is no SL data to be transmitted, UE 104 can perform multiplexing and assembly and generate a MAC PDU, which, instead of the actual data, may include an SL-SCH subheader and padding bits. UE 104's MAC layer may assume that the priority of the "virtual" SL data (e.g., padding) is the same as the priority of the SL PRS and determine the list of transmission parameters accordingly.

[0112] Because UE 104 can receive SL PRS requests that may include location conditions, UE 104 can obtain bandwidth (or the number of sub-channels) based on conditions / parameters (e.g., sometimes referred to as requirements).

[0113] - For example, when selecting bandwidth (or number of sub-channels) for SL PRS transmission, the corresponding location requirements and the minimum and maximum limits on the number of sub-channels for PSSCH (e.g., virtual SL data) can be taken into account.

[0114] If SL PRS and SL data are transmitted in a shared resource pool, since a bandwidth, priority, and / or transmission power can exist for SL PRS and SL data in the shared resource pool, the selection of SL authorization for SL PRS and SL data can consider (e.g., a default or CBR-measured and priority-influenced list of PSSCH parameters). This priority can be the highest priority value between the priority of SL PRS and the priority of SL data. Additionally or alternatively, the selection of bandwidth can consider the corresponding location requirements of SL PRS transmission and the minimum and maximum limits on the number of sub-channels in the PSSCH.

[0115] Reuse and / or LCP considerations In some cases, methods for determining the selected destination may be considered. For example, several factors may be considered during multiplexing, including but not limited to at least one of the following: the priority of the SL PRS; the priority of the logical channel used for SL data; the remaining delay budget of the SL data available in one or more logical channels; and / or the delay budget of the SL PRS.

[0116] One or more of the following non-restrictive example features or operations may be applied: Select a destination associated with one of unicast, multicast, and / or broadcast, that has the lowest latency budget among the PDB of SL data available in the logical channel and / or the latency budget of one or more SL PRS, and / or the highest priority among the priority of the logical channel used for SL data and the priority of one or more SL PRS.

[0117] Select a destination associated with one of unicast, multicast, and / or broadcast that satisfies the following conditions: having the lowest latency budget among the PDBs of SL data available in each logical channel and the highest priority among the priorities of the logical channels used for SL data.

[0118] The selected destination may prioritize SL data and take into account SL data, for example, by selecting at least one of the following destinations associated with unicast, multicast or broadcast: the destination has at least one of the highest priority MAC CE or logical channels for SL data.

[0119] When SL PRS and SL data are transmitted in a shared resource pool, or when SL PRS is transmitted in a shared resource pool, the selected destination may consider at least one or both of SL PRS and SL data. A destination associated with unicast, multicast, or broadcast may be selected that has the highest priority among the logical channels for SL data and the highest priority among one or more SL PRS. A list of SL PRS to be transmitted may exist, and different SL PRS may be transmitted in response to different location requests. In some cases, a list of logical channels for SL data to be transmitted may exist.

[0120] Select a destination associated with one of unicast, multicast, or broadcast, that has at least one of a MAC CE for SL data and a logical channel with the lowest latency budget.

[0121] The selected destination may consider at least one or both of SL PRS and / or SL data. In this case, a destination associated with one of unicast, multicast, or broadcast may be selected that has the lowest latency budget among the PDB of SL data available in the logical channel and the latency budget of one or more SL PRS.

[0122] If the destination has an SL PRS to be transmitted, multiplexing and assembling for constructing a MAC PDU associated with the SL license between the SL PRS and LCH data and / or one or more MAC CEs can be considered or implemented. UE 104 may support one or more of the following example implementations for multiplexing and assembling: When there is an SL PRS to be transmitted at the selected destination, the SL PRS can be transmitted.

[0123] The SL PRS can be transmitted when it has both the highest priority and the lowest latency budget at the selected destination.

[0124] The SL PRS can be transmitted when it is the highest priority under the selected destination.

[0125] The SL PRS can be transmitted when it is the lowest latency budget for the selected destination.

[0126] SLPRS can be transmitted when SL-SCH data with a higher priority than SL PRS is allocated in the MAC PDU.

[0127] An SL PRS can be transmitted when it exists at the selected destination and meets one or more predefined constraints. These constraints can apply to high-priority and / or low-priority SL PRS, low-latency budget SL PRS, and / or high-latency budget SL PRS. In some cases, an SL PRS transmission in response to a single location request may be transmitted no more than N times or for a duration T. The numbers N and T can be (pre)configured. Additionally or alternatively, if an SL PRS transmission in response to a single location request is transmitted more than N times or for a duration T, the priority of that SL PRS transmission may be downgraded in certain circumstances.

[0128] At least one of the following non-restrictive example processes can be applied to resource selection: Select one or more resources or destinations that meet the high priority and lowest latency budget for transmission. This transmission can be an SL PRS transmission and / or an SL data transmission.

[0129] If the conditions are not met, one or more resources or destinations that meet the higher priority transmission are selected. In this case, the transmission can be an SL PRS transmission and / or an SL data transmission.

[0130] In some cases, one or more resources or destinations can be selected to meet the low-latency budget.

[0131] If this condition is not met, for example when there may not be a sufficient number of resources available / selectable, UE 104 can be configured to select one or more resources or destinations.

[0132] When the MAC layer triggers the physical layer to perform sensing and report candidate resources, the MAC layer can provide the physical layer with: a resource pool; priority; latency budget; resource reservation period; a list of resources for preemption and re-evaluation; and / or a set of one or more SL PRS resource IDs. In this case, one or more of the following example configurations can be utilized: Priority can be considered from at least one of the priority of the SL PRS to be transmitted and the priority of the SL data to be transmitted, or both.

[0133] The latency budget may take into account at least one or both of the latency budgets of the PDB of the SL data to be transmitted and / or the SL PRS to be transmitted.

[0134] After selecting the SL authorization and reusing and assembling, for each PSCCH duration on the shared resource pool, the MAC entity can perform at least one of the following example procedures: Set the resource reservation period to the selected value, where the resource reservation period can be greater than the latency budget; Set the source ID and destination ID corresponding to SL PRS transmission, SL data transmission, and / or both SL PRS and SL data transmission; and / or Set the priority to the highest value between the priority indicated by the higher layer of the selected SL PRS (e.g., the application layer or via higher layer signaling) and / or the priority of the selected logical channel.

[0135] Example Implementation Method 3: Measurement Report of SL Positioning In various configurations, for SL positioning, absolute positioning, relative positioning, and / or ranging can be supported. For relative positioning and / or ranging, after SL PRS transmission, UE 104 or LMF (e.g., network function) may expect to estimate / calculate / determine the distance and / or angle of the target UE relative to another UE. In this case, for UE-based positioning, UE 104 may report the relative distance and angle to the LMF or another UE (e.g., server UE) via SLPP signaling (or other types of signaling).

[0136] In some implementations, consideration may be given to whether to report the "resource pool ID" in the measurement report, when to report the SLPRS resource ID, or how the LMF / UE can use the reported resource ID. In this case, the following non-limiting example operations or features may be applied or implemented: For example, for LMF-based SL localization: - For dedicated resource pools, UE 104 can report the SL PRS resource ID and resource pool ID together in the measurement report.

[0137] For shared resource pools, UE 104 can report the SL PRS resource ID, resource pool ID, and SL PRS frequency domain allocation or bandwidth together in the measurement report. SL PRS resources can be identified by the SL PRS resource ID and / or SL PRS frequency domain allocation.

[0138] - To enable the LMF to determine how to use the resource pool ID and SL PRS resource ID, the LMF can obtain the SLPRS resource pool configuration information for each UE. For example, one or more of the following example methods can be used or implemented: 4. BS 102 can send the SL PRS resource pool configuration information for each UE to the LMF via, for example, NR positioning protocol A (NRPPa), which may include the UE ID.

[0139] 5. UE 104 (e.g., itself) may send the SL PRS resource pool configuration information of each UE to the LMF via SLPP signaling or other types of signaling.

[0140] 6. The server UE can send the SL PRS resource pool configuration information for each UE to the LMF via SLPP signaling or other types of signaling. For example, the SL PRS resource pool configuration information for each UE can be used to report the UE ID.

[0141] For UE-based SL positioning: - If the UE 104 performing the calculation is the UE 104 involved in the SL PRS transmission (e.g., anchor UE or target UE), then the resource ID of that UE 104 may not be reported in the measurement report (or may be configured to skip reporting).

[0142] - If the UE 104 performing the calculation is neither the anchor UE nor the target UE, the resource pool configuration of the anchor UE and the target UE can be reported to the serving UE 104 via auxiliary data, including the reporting of the resource pool ID.

[0143] Example Implementation Method 4: Energy Saving In various configurations, depending on the power-saving scenario of UE 104, partial sensing and / or SL DRX can be provided for SL positioning in a dedicated resource pool. In various cases, one or more of the following non-limiting example features or operations can be supported: In some cases, periodic-based partial sensing (PBPS) and / or contiguous partial sensing (CPS) may be permitted in a dedicated resource pool.

[0144] Whether UE 104 performs SL PRS reception for partial sensing on time slots during SL DRX inactivity can be activated / disabled according to the (pre)configuration for each dedicated resource pool. For example, the configuration made according to each dedicated source pool can indicate whether UE 104 can perform SL PRS reception for partial sensing on time slots during SL DRX inactivity.

[0145] CBR related: - The SL PRS RSSI of the CBR can be measured in the SL PRS resource, where the UE 104 can perform partial sensing if partial sensing can be performed based on (pre)configuration.

[0146] - The (pre)configured SL PRS threshold can be the number of SL PRS resources. If the number of SL PRS resources in the CBR window is greater than the threshold, UE 104 can determine that the CBR measurement is valid.

[0147] - (Pre)configured CBR, if some sensing in the dedicated resource pool cannot meet / satisfy the threshold.

[0148] - A (pre-)configured CBR in a dedicated resource pool for random resource selection.

[0149] Example Implementation 5: CPE Configuration / Design for SL Positioning on Unlicensed Spectrum In various configurations, CP extension (CPE) can be supported for SL positioning in shared channels (e.g., unlicensed bands). For dedicated resource pools, the CPE can be transmitted from its start position within the channel occupancy time (COT), prior to PSCCH and / or SL PRS transmissions. The CPE can be transmitted within one or more symbols, for example, relative (e.g., immediately or just before) the next AGC symbol, where the AGC symbol can be either the AGC symbol prior to PSCCH transmission or the AGC symbol prior to each SL PRS resource. One or more symbols can be associated with an SCS; for example, based on (pre)configuration, for a 15 kHz SCS, the CPE can be transmitted within one symbol exactly before the next AGC symbol, and for a 30 kHz or 60 kHz SCS, the CPE can be transmitted within two symbols exactly before the next AGC symbol. Regarding the CPE used for SL positioning, including its start position and / or other configurations, one or more of the following example features or operations can be applied or implemented: A single CPE start position or CPE length can be (pre-)configured for SL positioning. In this case, the probability of successful channel access for UE 104 can be relatively more equal for either channel access type 1 or channel access type 2. For example, if different UEs 104 share the same CPE start position and / or CPE length, there can be no listen-before-talk (LBT) interference / blocking caused by different CPEs. In an example scenario, LBT blocking can refer to, for example, once UE 104 with a relatively long CPE length occupies the channel, it can prevent other UEs from accessing the channel due to channel congestion.

[0150] Additionally or alternatively, at least one CPE start position and / or CPE length for SL positioning can be (pre)configured. The selection of the CPE start position and / or CPE length can be associated with a priority value. The priority value can be the priority of SL PRS transmission and / or a channel access priority class (CAPC) value. In some implementations, one or more CPE start positions or CPE lengths can be (pre)configured according to each priority value. In this case, UE 104 can select at least one CPE configuration based on its SL PRS transmission priority and / or CAPC value (e.g., randomly). For example, in some arrangements, a longer CPE length increases the probability of successful channel access.

[0151] For example, for an SL PRS configuration in a shared channel, one or more start symbols can be (pre-)configured in a time slot. In this case, if UE 104 fails to access the channel in one time slot, there may be another opportunity or chance to access the channel in a second (or third) start symbol. The number and position of one or more start symbols in a time slot can be (pre-)configured in each resource pool. The number and position of one or more start symbols in time slots from multiple resource pools can be aligned. The number and position of one or more start symbols in a time slot can be (pre-configured) by BWP, by carrier, and / or by unlicensed frequency band. In each resource pool, a PSCCH configuration can be associated with one or more SL PRS resources. Different PSCCH configurations can be associated with the same one or more SL PRS resources. In some cases, there may be no mapping between SL PRS resources and PSCCH configurations. In this case, for example, based on different transmission priorities of UE 104, a relatively higher priority can access the channel and transmit SL PRS relatively quickly.

[0152] For example, Figure 3 Example description 300 illustrates the transmission of Side Link Control Information (SCI) 1 and SCI 2. As shown, consider a scenario where UE 1 and UE 2 (e.g., UE-A or UE-B respectively, or vice versa) successfully access the channel, UE 1 transmits SCI 1, and UE 2 transmits SCI 2. Based on the resource pool (pre)configuration, SCI 1 and SCI 2 can be associated with SL PRS 1 and SL PRS 2. In this case, if UE 1's transmission priority is relatively greater than / higher than UE 2's, UE 1 can access the channel before UE 2 and transmit SL PRS 1, while UE 2 can transmit SL PRS 2 (e.g., without transmitting SL PRS 1) due to the relatively short CPE length.

[0153] In this scenario, determining / determining the SL PRS resource ID field in the SCI can be challenging for a transmit (Tx) UE, as the selection process and competition with other devices can be flexible for Tx UEs. In such cases, for example in side-link positioning on unlicensed spectrum, a shared resource pool may be supported, while a dedicated resource pool for SL PRS may not be.

[0154] Example Implementation 6: SL Positioning Measurement Cycle Conditions (e.g., Requirements) In various configurations, for SL positioning purposes, UE 104 may receive location information requests and auxiliary data from another UE and / or LMF via SLPP signaling (or other signaling). UE 104 may be able to measure multiple SL positioning measurements during a measurement period. These multiple SL positioning measurements can be reported in response to a location information request. These multiple SL positioning measurements may be at least one of the following: one or more SL PRS reference signal time difference (RSTD) measurements; one or more SL PRS relative time of arrival (RTOA) measurements; one or more SL PRS Rx-Tx (e.g., receive and transmit) time difference measurements for the SL RTT method; one or more SL PRS reference signal received power (RSRP) measurements; one or more SL PRS reference signal received path power (RSRPP) measurements; SL angle of arrival (AoA), etc.

[0155] In some cases, UE 104 may report its capability for at least one of the following: the maximum number of active or occupied SL PRS resources in all configured resource pools that UE 104 can process within a duration (e.g., the duration may be a time slot or expressed in ms, etc.); the minimum time that UE 104 takes to complete SL-PRS resource processing and prepare a location measurement report after the time slot carrying the SL-PRS resources ends, for example assuming that the active or occupied SL-PRS resources during the duration do not exceed the reporting capability, and assuming that the maximum SL PRS bandwidth is in MHz; the number of PSCCH resources and / or SL PRS resources that UE 104 can process within a duration, where the duration may be a time slot expressed in ms, etc.; and / or the number of SL PRS symbols that UE 104 can process within a second duration.

[0156] In some cases, the LMF or server UE 104 may request UE 104 to report location information. The request signaling may include, but is not limited to, at least one of the following: whether to request UE 104 to measure the same SL PRS resource using multiple Rx timing error groups (TEGs); requesting UE 104 to use the number of Rx TEGs to measure the SL PRS resource; whether to request UE 104 to measure the same SL PRS resource using multiple Rx antenna reference points (ARPs); requesting UE 104 to use the number of Rx ARPs to measure the SL PRS resource; and / or whether to request UE 104 to receive reports of multiple Rx-Tx measurements for the same SL PRS resource.

[0157] In some implementations, unlike DL PRS which is periodic Uu positioning, various SL PRS transmissions can be aperiodic. For example, for SL PRS resource allocation scheme 2 (e.g., UE autonomous resource selection), UE 104 can select one or more resources based on sensing or random selection. Subsequently, the measurement period required for UE 104 to receive measurement requests can vary depending on whether the Tx UE (e.g., the transmitting UE) successfully selects one or more resources. However, in SL PRS resource allocation scheme 1, SL PRS transmissions can be dynamic, semi-persistent, and / or periodic.

[0158] The measurement period may be associated with at least one or more of the following: Quality of Service (QoS) requirements; SL PRS latency budget; selection window size (e.g., multiple minimum selection window sizes pre-configured across multiple resource pools based on resource pool (pre)configuration and latency budget); periodicity of CG used for SL positioning; least common multiple (LCM) of CG periods; SL PRS resource reservation period; the maximum number of active (or occupied) SL PRS resources processed by UE 104 across all configured resource pools within a duration (e.g., the duration may be a time slot or expressed in ms); the maximum number of SL PRS resources (pre-configured) across various configured resource pools within a duration (e.g., the duration may be a time slot or expressed in ms); the minimum time UE 104 takes to complete SL-PRS resource processing and prepare a positioning measurement report after the end of a time slot carrying SL-PRS resources, assuming or based on the fact that the active or occupied SL-PRS resources during this time period do not exceed the reporting capacity, and according to UE 104 The following parameters can be specified: the maximum SL PRS bandwidth (in MHz) that UE 104 can support and report; the number of UE 104s whose SL PRS will be measured; the number of resource pools to be measured; the number of SL PRS symbols that UE 104 can process within a second duration; the number of samples; the number of PSCCH resources that UE 104 can receive within a duration (which may be a time slot or expressed in ms, etc.); the number of PSCCH resources and / or SL PRS resources that UE 104 can process within a duration (e.g., the duration may be a time slot or expressed in ms); whether UE 104 is requested to measure the same SL PRS resource with multiple Rx Timing Error Groups (TEGs); the number of Rx TEGs that UE 104 can simultaneously (e.g., including whether UE 104 is able to) measure and the number of Rx TEGs requested by UE 104 for measuring SL PRS resources; whether UE 104 is requested to measure the same SL PRS resource with multiple Rx Antenna Reference Points (ARPs); and / or the number of Rx TEGs that UE 104 can simultaneously (e.g., including whether UE 104 is able to) measure. The number of ARPs; and the number of Rx ARPs requested by UE 104 to measure SL PRS resources. In some examples, the measurement period can be related to ceil ( (related to)

[0159] Figure 4 This is a flowchart illustrating an example method 400 for sidelink localization enhancement. Method 500 can be used in conjunction with this document. Figures 1 to 3Method 400 may be implemented by any one or more of the components and devices described in the detailed description. In short, in some embodiments, method 400 may be performed by one or more network devices, such as one or more wireless communication devices (e.g., one or more UEs 104), at least one wireless communication node (e.g., BS, gNB, or TRP), and / or at least one network function (e.g., LMF), etc. Depending on the embodiment, additional operations, fewer operations, or different operations may be performed in method 400. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0160] In operation 402, the first wireless communication device (e.g., UE-B) may, in response to receiving a location request, determine information regarding the transmission of a Side Link Location Reference Signal (SL PRS). In operation 404, the first wireless communication device may, based on the information regarding the SL PRS transmission, transmit / send / provide / transmit / forward the SL PRS and the corresponding Side Link Control Information (SCI).

[0161] In some implementations, the first wireless communication device may receive / obtain / acquire a location request from at least one of the following: a higher layer of the first wireless communication device (e.g., the application layer); and / or a second wireless communication device (e.g., UE-A).

[0162] In some implementations, one or more wireless communication devices may receive an SCI and associated SL PRS resource from a second wireless communication device. For example, in this case, the first wireless communication device may be one of the one or more wireless communication devices. The SCI transmitted by the second wireless communication device may include at least one of the following: broadcast type; source ID; destination ID; and / or SL PRS request field.

[0163] In some implementations, the location request in the SCI, which can be transmitted by the second wireless communication device, and the SL PRS resources, which can be transmitted by the second wireless communication device, may share at least one of the following: the same broadcast type; the same source ID; and / or the same destination ID, etc. In some implementations, the location request field in the SCI may be deactivated / disabled, for example, in response to at least one of the following conditions: the SLPRS request field is not pre-configured, configured, or enabled in the resource pool; the broadcast type is indicated as broadcast; and / or the broadcast type is indicated as multicast.

[0164] In some implementations, the SCI may also include a request ID. The request ID can be configured to indicate which of one or more wireless communication devices is requested to transmit SL PRS in response to a location request. In some implementations, the request ID may include at least one of the following: a UE ID indicated by a first higher layer; a source ID indicated by a second higher layer; and / or a member ID of a multicast case that may be indicated by a third higher layer and represent a member of a group.

[0165] In some implementations, the first through third layers may each be Side Link Positioning Protocol (SLPP) signaling or signaling sent from the application layer. In some implementations, each of the first through third layers may be configured to notify one or more wireless communication devices which wireless communication device is requested to transmit SLPRS in response to a positioning request, and includes SLPRS transmission features.

[0166] In some implementations, SL PRS transmission characteristics may include, but are not limited to, at least one of the following: location conditions; Quality of Service (QoS) conditions; SL PRS transmission priority of the target wireless communication device; SL PRS configuration; latency conditions; and / or UE ID. For example, QoS conditions may include, for instance, at least one of the following: horizontal accuracy; vertical accuracy; response time; rate request; SL PRS latency budget; and / or priority. SL PRS configuration may include, but is not limited to, at least one of the following: symbol count; comb size; comb offset; bandwidth; sequence ID; SL PRS resource ID; resource pool ID; shared resource pool; and / or dedicated resource pool. Latency conditions may include, but are not limited to, the first wireless communication device being configured to transmit SL PRS for a period of time after receiving an SCI with an SLPRS request.

[0167] In some implementations, if the first wireless communication device and the second wireless communication device are in the same location session, and the first wireless communication device receives a location request from the second wireless communication device, the first wireless communication device can be configured to transmit SL PRS. In some implementations, the resource selection or allocation for the SL PRS transmission from the first wireless communication device in the list of wireless communication devices receiving the location request can take into account UE information or group membership information.

[0168] In some implementations, if the first wireless communication device is in SL PRS resource allocation scheme 2, such as that discussed herein, the first wireless communication device may, for example, in response to a location request, determine one or more SL PRS resource IDs for transmitting SL PRS, taking into account the maximum number of SL PRS resources configured or pre-configured in the resource pool and UE information or group membership information. In some implementations, if the first wireless communication device is in SL PRS resource allocation scheme 2, the first wireless communication device may determine one or more SL PRS resource pool IDs for transmitting SL PRS in response to a location request.

[0169] In some implementations, the second wireless communication device may use a Side Link Positioning Protocol (SLPP) to recommend or configure different SL PRS features for the first wireless communication device or one or more other wireless communication devices. In some implementations, the first wireless communication device may, in response to receiving a positioning request from the second wireless communication device, transmit / send SL PRS in a unicast, multicast, and / or broadcast manner. The destination of the SL PRS transmission may be configured or pre-configured to include the second wireless communication device. For example, due to limitations in certain conventional mechanisms, new mechanisms may be implemented for obtaining SL authorization and determining SL transmission information for SL positioning within a shared resource pool.

[0170] In some implementations, the first wireless communication device may determine to transmit SL PRS on a shared resource pool. Information regarding SL PRS transmission may include, but is not limited to, at least one of the following: time resources; frequency resources; SL grant; priority; source ID; destination ID; resource pool ID; bandwidth; sidelink channel occupancy rate (SL CR) limit; maximum transmission power; SLPRS resource ID; and / or resource reservation interval.

[0171] In some implementations, the first wireless communication device may determine one or more SL PRS transmission parameters based on one or more delay budgets. In some implementations, the one or more delay budgets may each include the remaining delay budget of the SL PRS and the remaining packet delay budget (PDB) of the SL data available in the logical channel, or a unified delay budget. The unified delay budget may be the minimum value between the remaining delay budget of the SL PRS and the remaining PDB of the SL data available in the logical channel.

[0172] In some implementations, information regarding SL PRS transmissions may be related to both the PSSCH transmission parameter list and the SL PRS transmission parameter list. In some implementations, the SL PRS transmission parameter list may be associated with the priority of SL PRS transmissions and channel busy-idle rate (CBR) measurements.

[0173] In some implementations, the PSSCH transmission parameter list may be associated with the priority of the PSSCH transmission and CBR measurements. In some implementations, information regarding SL PRS transmissions may be associated with at least one of the following: the priority of the SL PRS; the priority of the logical channel used for SL data; the remaining delay budget of the SL data available in the logical channel; and / or the delay budget of the SL PRS.

[0174] In some implementations, the first wireless communication device may select a destination associated with one of unicast, multicast, and / or broadcast, that has the highest priority among the priority of the logical channel used for SL data and the priority of the SL PRS for the SCI corresponding to the SL PRS transmission. In some implementations, the first wireless communication device may transmit the SL PRS when there is an SL PRS to be transmitted at the selected destination and the SL PRS to be transmitted meets at least one constraint. The at least one constraint may include, but is not limited to, at least one of the following: the SL PRS to be transmitted has the highest priority; the SL PRS to be transmitted has the lowest latency budget; and / or the SL PRS to be transmitted in response to a single location request has not been transmitted more than N times or for more than a duration.

[0175] In some implementations, a third wireless communication device may receive SLPRS transmitted by a first wireless communication device. The third wireless communication device may send an indication of at least one of relative distance, angle, or resource pool ID in the location information report (e.g., providing a detailed location information report for relative positioning and ranging). In some cases, if the resource ID is reported in the measurement report but not the resource pool ID, the SL PRS resource IDs in different SL PRS resource pools may be associated with different numbers of symbols and comb patterns of SL PRS, etc. In some implementations, the first wireless communication device may perform partial sensing to select available resources for SL PRS transmission. At least one of the following, but not limited to: partial sensing may be performed during SL discontinuous reception (DRX) inactive times based on resource pool configuration; the SL PRS Received Signal Strength Indicator (RSSI) may be measured in the SL PRS resources where the first wireless communication device performs partial sensing; and / or CBR may be used if a threshold is not met, wherein the threshold is calculated by the number of SL PRS resources in the CBR window. In this case, the power consumption of the first wireless communication device performing SL positioning can be minimized or reduced.

[0176] In some implementations, the first wireless communication device may transmit SL PRS in an unlicensed frequency band. The choice of the cyclic prefix extension (CPE) start position or CPE length may be associated with a priority value for the SL PRS transmission. In this case, for example, a higher-priority SL PRS transmission may have a relatively higher probability of successfully accessing the channel to perform SL positioning in the unlicensed spectrum.

[0177] In some implementations, a third wireless communication device may receive and measure the SL PRS from one or more other wireless communication devices. The third wireless communication device may perform (or complete) one or more SL PRS measurements during a measurement period, wherein at least one of the following is true: the first wireless communication device may be one of one or more other wireless communication devices; the third wireless communication device may receive a location information request from another wireless communication device or network function via Side Link Positioning Protocol (SLPP) signaling; and / or the third wireless communication device may receive auxiliary data from another wireless communication device or network function via SLPP signaling for measuring the SL PRS.

[0178] In some implementations, the measurement period may be associated with at least one of the following: Quality of Service (QoS) conditions (or requirements); one or more latency budgets for SL PRS transmissions; one or more selection window sizes; one or more periods for SL positioning (Configuration Grant (CG); one or more resource reservation periods for SL PRS; the maximum number of active SL PRS resources processed by one or more wireless communication devices across configured resource pools within a given duration; and / or the maximum number of (pre)configured SL PRS resources across configured resource pools within a given duration. For example, in this case, the wireless communication device may complete / terminate one or more SL PRS measurements within the measurement period requirement to satisfy the QoS conditions (or requirements or criteria).

[0179] While various arrangements of this solution have been described above, it should be understood that these arrangements are provided as examples only and are not intended to be limiting. Similarly, various diagrams may depict example architectures or configurations intended to enable those skilled in the art to understand the example features and functionality of this solution. However, such individuals will understand that the solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, those skilled in the art will understand that one or more features of some arrangements can be combined with one or more features of another arrangement described herein. Therefore, the breadth and scope of this disclosure should not be limited by any of the illustrative arrangements described above.

[0180] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names may be used in this document as a convenient means of distinguishing between two or more elements or two or more instances of an element. Therefore, referring to the first element and the second element does not imply that only two elements can be used, nor does it imply that the first element must somehow precede the second element.

[0181] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, as may be mentioned in the above description, can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0182] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate the interchangeability between hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have generally been described above according to their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not exceed the scope of this disclosure.

[0183] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or executed by integrated circuits, which may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, it may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors coupled with a DSP core, or any other suitable configuration for performing the functions described herein.

[0184] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium capable of transferring computer programs or code from one place to another. Storage media can be any available medium accessible to a computer. For example, but not limited to, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and is accessible to a computer.

[0185] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the associated functions described herein. Furthermore, for illustrative purposes, various modules are described as separate modules; however, as will be apparent to those skilled in the art, two or more modules can be combined to form a single module that performs associated functions according to the arrangement of this solution.

[0186] Furthermore, memory or other storage devices and communication components may be used in the arrangement of this solution. It will be understood that, for clarity, the above description describes the arrangement of this solution according to different functional units and processors. However, it will be apparent that any suitable allocation of functions among different functional units, processing logic elements, or domains can be used without diminishing the effectiveness of this solution. For example, functions shown as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely illustrative of a suitable means of providing said functions and do not imply a strict logical or physical structure or organization.

[0187] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but should be given the broadest scope consistent with the novel features and principles disclosed herein as set forth in the appended claims.

Claims

1. A wireless communication method, comprising: In response to receiving a positioning request, the first wireless communication device determines information regarding the transmission of the side link positioning reference signal (SL PRS). as well as The first wireless communication device transmits the SL PRS and the corresponding side link control information (SCI) based on the information transmitted about the SL PRS.

2. The wireless communication method according to claim 1, wherein, The first wireless communication device receives the location request from at least one of the following: The upper layer of the first wireless communication device; or Second wireless communication device.

3. The wireless communication method according to claim 1, further comprising: One or more wireless communication devices receive SCI and associated SL PRS resources from a second wireless communication device; Wherein, the first wireless communication device is one of one or more wireless communication devices; and The SCI transmitted by the second wireless communication device includes at least one of the following: broadcast type; source ID; destination ID; or SL PRS request field.

4. The wireless communication method according to claim 3, wherein, The location request in the SCI transmitted by the second wireless communication device and the SL PRS resource transmitted by the second wireless communication device share at least one of the following: the same broadcast type; the same source ID; or the same destination ID.

5. The wireless communication method according to claim 4, wherein, The location request field in the SCI is disabled in response to at least one of the following conditions: The SL PRS request field is not pre-configured, not configured, or not enabled in the resource pool; The broadcast type is indicated as broadcast; or The broadcast type is indicated as multicast.

6. The wireless communication method according to claim 3, wherein, The SCI also includes a request ID, wherein the request ID is configured to indicate which of the one or more wireless communication devices is requested to transmit SL PRS in response to the location request.

7. The wireless communication method according to claim 6, wherein, The requested ID includes at least one of the following: a UE ID indicated by a first higher layer; a source ID indicated by a second higher layer; or a member ID for multicast cases indicated by a third higher layer and representing a member in the group.

8. The wireless communication method according to claim 7, wherein, Each of the first to the third higher layers is either Side Link Positioning Protocol (SLPP) signaling or signaling sent from the application layer.

9. The wireless communication method according to claim 3, wherein, Each of the first to the third layer is configured to notify which of the one or more wireless communication devices is requested to transmit SL PRS in response to the location request, and includes SL PRS transmission features.

10. The wireless communication method according to claim 9, wherein, The SL PRS transmission characteristics include at least one of the following: Location conditions; Quality of Service (QoS) conditions; SL PRS transmission priority of the target wireless communication device; SL PRS configuration; Delay conditions; or UE ID.

11. The wireless communication method according to claim 3, wherein, If the first wireless communication device and the second wireless communication device are in the same location session, and the first wireless communication device receives the location request from the second wireless communication device, then the first wireless communication device is configured to transmit the SL PRS.

12. The wireless communication method according to claim 1, wherein, The resource selection or allocation of the SL PRS transmission from the first wireless communication device in the list of wireless communication devices receiving the location request takes into account UE information or group membership information.

13. The wireless communication method according to claim 12, wherein, If the first wireless communication device is in SLPRS resource allocation scheme 2, then in response to the location request, the first wireless communication device determines one or more SLPRS resource IDs for transmitting the SLPRS by considering the maximum number of SLPRS resources (pre-)configured in the resource pool and the UE information or the group membership information.

14. The wireless communication method according to claim 12, wherein, If the first wireless communication device is in SLPRS resource allocation scheme 2, then in response to the location request, the first wireless communication device determines one or more SLPRS resource pool IDs for transmitting the SLPRS.

15. The wireless communication method according to claim 3, wherein, The second wireless communication device may use the Side Link Positioning Protocol (SLPP) to recommend or configure different SLPPS features for the first wireless communication device or one or more other wireless communication devices.

16. The wireless communication method according to claim 2, further comprising: The first wireless communication device, in response to receiving the location request sent from the second wireless communication device, transmits the SL PRS via unicast, multicast, or broadcast. The destination of the SL PRS transmission is configured or pre-configured to include the second wireless communication device.

17. The wireless communication method according to claim 1, further comprising: The first wireless communication device determines that the SL PRS will be transmitted on the shared resource pool; The information regarding the SL PRS transmission includes at least one of the following: time resources; frequency resources; SL authorization; priority; source ID; destination ID; resource pool ID; bandwidth; sidelink channel occupancy rate (SL CR) limit; maximum transmission power; SL PRS resource ID; or resource reservation interval.

18. The wireless communication method according to claim 17, further comprising: The first wireless communication device determines one or more SL PRS transmission parameters based on one or more delay budgets.

19. The wireless communication method according to claim 18, wherein, Each of the one or more delay budgets includes the remaining delay budget of the SL PRS and the remaining packet delay budget (PDB) of the SL data available in the logical channel, or a unified delay budget, wherein the unified delay budget is the minimum between the remaining delay budget of the SL PRS and the remaining PDB of the SL data available in the logical channel.

20. The wireless communication method according to claim 17, wherein, The information regarding the SL PRS transmission is related to both the PSSCH transmission parameter list and the SL PRS transmission parameter list.

21. The wireless communication method according to claim 20, wherein, The SLPRS transmission parameter list is associated with the priority and channel busy-idle rate (CBR) measurement of the SLPRS transmission.

22. The wireless communication method according to claim 20, wherein, The PSSCH transmission parameter list is associated with the priority of PSSCH transmission and CBR measurement.

23. The wireless communication method according to claim 17, wherein, The information regarding the SL PRS transmission is related to at least one of the following: the priority of the SL PRS; the priority of the logical channel used for SL data; the remaining delay budget of the SL data available in the logical channel; or the delay budget of the SL PRS.

24. The wireless communication method according to claim 17, wherein, The first wireless communication device selects a destination associated with one of unicast, multicast, or broadcast, the destination having the highest priority among the priority of the logical channel used for SL data and the priority of the SL PRS used for the SCI corresponding to the SL PRS transmission.

25. The wireless communication method according to claim 24, wherein, The SL PRS is transmitted by the first wireless communication device when there is an SL PRS to be transmitted at the selected destination and the SL PRS to be transmitted satisfies at least one of the following limitations: The SL PRS to be transmitted has the highest priority; The SL PRS to be transmitted has a minimum latency budget; or The SL PRS to be transmitted in response to a single location request was transmitted no more than N times or for no more than a certain duration.

26. The wireless communication method according to claim 1, further comprising: The third wireless communication device receives the SL PRS transmitted by the first wireless communication device, and The third wireless communication device sends an indication of at least one of relative distance, angle, or resource pool ID in the location information report.

27. The wireless communication method according to claim 1, further comprising: The first wireless communication device performs partial sensing to select available resources for the SL PRS transmission, wherein at least one of the following is true: Based on the resource pool (pre) configuration, the partial sensing is performed during the SL discontinuous reception (DRX) inactive time; The SL PRS Received Signal Strength Indicator (RSSI) is measured in the SL PRS resources sensed by the first wireless communication device during the partial sensing; or If the threshold is not met, CBR is used, where the threshold is calculated by the number of SL PRS resources in the CBR window.

28. The wireless communication method according to claim 1, wherein, The first wireless communication device transmits the SL PRS in an unlicensed frequency band, wherein the selection of the cyclic prefix extension (CPE) start position or CPE length is associated with the priority value of the SL PRS transmission.

29. The wireless communication method according to claim 1, further comprising: The SLPRS is received by a third wireless communication device from one or more other wireless communication devices and the SLPRS is measured; and One or more SL PRS measurements are performed by the third wireless communication device during the measurement period, wherein at least one of the following is true: The first wireless communication device is one of the one or more other wireless communication devices; The third wireless communication device receives a location information request from another wireless communication device or network function via Side Link Positioning Protocol (SLPP) signaling; or The third wireless communication device receives auxiliary data from another wireless communication device or network function via SLPP signaling used to measure the SL PRS.

30. The wireless communication method according to claim 29, wherein, The measurement period is associated with at least one of the following: One or more delay budgets for the SL PRS transmission; One or more selection window sizes; One or more cycles of configuration license (CG) used for SL positioning; One or more resource reservation periods for SL PRS; The maximum number of active SL PRS resources across a configured resource pool that one or more wireless communication devices process within a given duration; or The maximum number of SL PRS resources (pre-)configured across the configured resource pool within a given duration.

31. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 30.

32. A computer program product comprising a computer-readable program medium having code stored on the computer-readable program medium, the code, when executed by a processor, causing the processor to perform the method according to any one of claims 1 to 30.