Transmission of position reference signal configurations for wireless communications

By coordinating SL-PRS configurations through an LMF and RAN nodes, the method addresses overlapping issues in sidelink positioning, enhancing communication efficiency and reducing interference among user devices.

JP2025532262AActive Publication Date: 2025-09-29ZTE CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2025518244
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2022-09-29
Publication Date
2025-09-29
Estimated Expiration
2042-09-29

AI Technical Summary

Technical Problem

In sidelink positioning scenarios, different user devices under different gNBs may receive overlapping SL-PRS configurations, leading to interference during transmission due to the lack of coordination among gNBs in providing SL-PRS configurations.

Method used

A method involving a Location Management Function (LMF) and Radio Access Network (RAN) nodes to transmit non-overlapping SL-PRS configurations to user devices, coordinating the configurations to avoid conflicts and interference.

Benefits of technology

The solution effectively prevents overlapping SL-PRS configurations, reducing interference and ensuring seamless sidelink positioning operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025532262000001_ABST
    Figure 2025532262000001_ABST
Patent Text Reader

Abstract

This document generally relates to wireless communications including a location management function (LMF) and at least one radio access network (RAN) node that perform interactions associated with at least one sidelink positioning reference signal (SL-PRS) configuration. The LMF or the at least one RAN node transmits multiple non-overlapping SL-PRS configurations to multiple user devices based on the interactions. In some other implementations, a device, such as a network device, is disclosed.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] Technical Field This document relates generally to sidelink positioning for wireless communications. [Background technology]

[0002] background In a sidelink positioning Mode 1 scenario, different sidelink user devices may have different serving gNBs. There may be one or more Mode 1 user devices under the range or coverage of one gNB, and one or more Mode 1 user devices may interact with this gNB via control signaling. Mode 1 user devices under the same or different gNBs need to receive different or non-overlapping sidelink position reference signal (SL-PRS) configurations to avoid conflicts when transmitting SL-PRS to other sidelink user devices. When different serving gNBs provide SL-PRS configurations to their corresponding user devices, different gNBs do not coordinate their SL-PRS configurations or perform contention resolution with each other, so different user devices may receive overlapping SL-PRS configurations (e.g., in the time domain or frequency domain), which may cause interference when user devices transmit SL-PRS. Therefore, a method to avoid overlapping SL-PRS configurations may be desirable. Summary of the Invention [Means for solving the problem]

[0003] overview This document relates to methods, systems, apparatus, and devices for wireless communications. In some implementations, the method for wireless communications includes performing, with a Location Management Function (LMF) and at least one Radio Access Network (RAN) node, an interaction associated with at least one Sidelink Positioning Reference Signal (SL-PRS) configuration, and transmitting, with the LMF or the at least one RAN node, a plurality of non-overlapping SL-PRS configurations to a plurality of user devices based on the interaction.

[0004] In some other implementations, a device, such as a network device, is disclosed. The device may include one or more processors and one or more memories, where the one or more processors are configured to read computer code from the one or more memories to perform any of the methods described above.

[0005] In yet some other implementations, a computer program product is disclosed. The computer program product may include a non-transitory computer-readable program medium having stored thereon computer code that, when executed by one or more processors, causes the one or more processors to perform any of the methods described above.

[0006] These and other aspects and their implementations are described in more detail in the drawings, specification, and claims. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 shows a block diagram of an example wireless communication system.

[0008] [Figure 2] FIG. 2 shows a block diagram of an example configuration of a wireless access node of the wireless communication system of FIG.

[0009] [Figure 3] FIG. 3 shows a block diagram illustrating a sidelink positioning structure for an in-coverage scenario of the wireless system of FIGS. 1 and 2.

[0010] [Figure 4] FIG. 4 illustrates a flowchart of an example method for wireless communication. DETAILED DESCRIPTION OF THE INVENTION

[0011] Detailed Description The description herein describes various embodiments of systems, apparatuses, devices, and methods for wireless communications associated with sidelink positioning.

[0012] 1 shows a diagram of an exemplary wireless communication system 100 including multiple communication nodes (or simply, nodes) configured to wirelessly communicate with one another. Generally, the communication nodes include at least one user device 102 and at least one wireless access node 104. The exemplary wireless communication system 100 of FIG. 1 is shown as including two user devices 102, including a first user device 102(1) and a second user device 102(2), and one wireless access node 104. However, various other examples of wireless communication systems 100 including any of various combinations of one or more user devices 102 and / or one or more wireless access nodes 104 may be possible.

[0013] In general, a user device described herein, such as user device 102, may include a single electronic device or apparatus or multiple electronic devices or apparatuses (e.g., a network of electronic devices or apparatuses) capable of communicating wirelessly over a network. A user device may comprise or otherwise be referred to as a user terminal, user terminal device, or user equipment (UE). Furthermore, a user device may be or include, but is not limited to, a mobile device (such as a mobile phone, smartphone, smartwatch, tablet, laptop computer, vehicle or other vessel (including, but not limited to, a human-, motor-, or engine-powered vehicle or other vessel, such as an automobile, airplane, train, boat, or bicycle) or a fixed or stationary device (including, but not limited to, an appliance, other relatively heavy device including the Internet of Things (IoT), or a desktop computer or other computing device that is not typically moved for long periods of time, such as a computing device used in a commercial or industrial environment). In various embodiments, user device 102 may include transceiver circuitry 106 coupled to an antenna 108 for wireless communication with wireless access node 104. The transceiver circuitry 106 may also be coupled to a processor 110, which may be coupled to a memory 112 or other storage device. The memory 112 may store instructions or code that, when read and executed by the processor 110, cause the processor 110 to perform various of the methods described herein.

[0014] Additionally, in general, a wireless access node described herein, such as the wireless access node 104, may include a single electronic device or apparatus, or multiple electronic devices or apparatuses (e.g., a network of electronic devices or apparatuses) and may comprise one or more base stations or other wireless network access points that can communicate wirelessly with one or more user devices and / or one or more other wireless access nodes 104 over a network. For example, the wireless access node 104, in various embodiments, may comprise at least one of a 4G LTE base station, a 5G NR base station, a 5G central unit base station, a 5G distributed unit base station, a next generation Node B (gNB), an enhanced Node B (eNB), or other similar or next generation (e.g., 6G) base station, or a Location Management Function (LMF). The wireless access node 104 may include transceiver circuitry 114 coupled to an antenna 116, which may include an antenna tower 118 in various manners, for conducting wireless communication with a user device 102 or another wireless access node 104. The transceiver circuitry 114 may also be coupled to one or more processors 120, which may be coupled to a memory 122 or other storage device. The memory 122 may store instructions or code that, when read and executed by the processor 120, cause the processor 120 to perform one or more of the methods described herein.

[0015] FIG. 2 shows a block diagram of an example configuration of a wireless access node 104. In an exemplary configuration, the wireless access node 104 may include a location management function (LMF) 202 and one or more radio access network (RAN) nodes 204. Some embodiments may include only one RAN node 204. Other embodiments, such as those shown in FIG. 2, may include multiple or n RAN nodes 204(1) through 204(n), where n is 2 or greater. The LMF 202 and each RAN node 204 may each be configured in hardware or a combination of hardware and software, such as by having a processor 120, memory 122, transceiver circuitry 114, antenna 116, and / or antenna tower 118, as shown in FIG. 1 for the wireless access node 104.

[0016] 2, the LMF 202 and each RAN node 204 may be configured to communicate (transmit and receive) with each other, such as signals or messages, and with one or more user devices 102, directly or indirectly via another component of the wireless access node 104. For example, the LMF 202 may communicate directly with the user devices 102. In particular embodiments, the LMF 202 may communicate directly with the user devices 102 in accordance with the Long Term Evolution (LTE) Positioning Protocol (LPP) (i.e., via LPP signaling). The RAN nodes 204 may also communicate directly with the user devices 102. In particular embodiments, the RAN nodes 204 may communicate directly with the user devices 102 via at least Radio Resource Control (RRC) signaling. In addition, the LMF 202 may communicate directly with each RAN node 204. In particular embodiments, the LMF 202 may communicate directly with each RAN node 204 in accordance with the New Radio Positioning Protocol A (NRPPa) (i.e., via NRPPa signaling). Also, for at least some embodiments such as those shown in FIG. 2, each RAN node 204 may include one or more subcomponents. For example, the RAN node 204 may include a gNB and / or at least one transmission / reception point (TRP). Further functionality of the LMF 202 and the RAN node 204 is described in further detail below.

[0017] Further, referring back to FIG. 1 , in various embodiments, two communication nodes in the wireless system 100, such as a user device 102 and a wireless access node 104, two user devices 102 without a wireless access node 104, or two wireless access nodes 104 without a user device 102, may be configured to wirelessly communicate with each other within or over a mobile network and / or wireless access network in accordance with one or more standards and / or specifications. Generally, the standards and / or specifications may define rules or procedures by which the communication nodes can communicate wirelessly, and in various embodiments may include those for communicating in millimeter (mm) wavebands and / or with multi-antenna schemes and beamforming capabilities. Additionally or alternatively, the standards and / or specifications may specify radio access and / or cellular technologies, such as, by way of non-limiting example, Fourth Generation (4G) Long Term Evolution (LTE), Fifth Generation (5G) New Radio (NR), or New Radio Unlicensed (NR-U).

[0018] Further, in wireless system 100, communication nodes are configured to wirelessly communicate signals with one another. Generally, communication in wireless system 100 between two communication nodes can be or include transmission or reception, generally both occurring simultaneously, depending on the perspective of the particular node in the communication. For example, for a given communication between a first node and a second node, where the first node is transmitting a signal to the second node and the second node is receiving a signal from the first node, the first node may be referred to as a source or transmitting node or device, the second node may be referred to as a destination or receiving node or device, and the communication may be viewed as a transmission for the first node and a reception for the second node. Of course, because communication nodes in wireless system 100 can transmit and receive signals, a single communication node may be both a transmitting / source node and a receiving / destination node simultaneously, or may switch between being a source / transmitting node and a destination / receiving node.

[0019] Also, a particular signal may be characterized or defined as either an uplink (UL) signal, a downlink (DL) signal, or a sidelink (SL) signal. An uplink signal is a signal transmitted from a user device 102 to a wireless access node 104. A downlink signal is a signal transmitted from a wireless access node 104 to a user device 102. A sidelink signal is a signal transmitted from one user device 102 to another user device 102 or from one wireless access node 104 to another wireless access node 104. Also, for sidelink transmission, a first / source user device 102 transmits the sidelink signal directly to a second / destination user device 102 without any forwarding of the sidelink signal to the wireless access node 104.

[0020] Additionally, signals communicated between communication nodes in system 100 may be characterized or defined as data signals or control signals. Generally, data signals are signals that contain or carry data, such as multimedia data (e.g., voice and / or image data), while control signals are signals that carry control information that configure communication nodes in a particular way to communicate with each other or that control how communication nodes communicate data signals with each other. Certain signals may also be defined or characterized by combinations of data / control and uplink / downlink / sidelink, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, sidelink control signals, and sidelink data signals.

[0021] In at least some specifications, such as 5G NR, data and control signals are transmitted and / or carried on physical channels. Generally, a physical channel corresponds to a set of time-frequency resources used to transmit signals. Different types of physical channels may be used to transmit different types of signals. For example, a physical data channel (or simply, data channel) is used to transmit data signals, and a physical control channel (or simply, control channel) is used to transmit control signals. Examples of types of physical data channels include, but are not limited to, a physical downlink shared channel (PDSCH) used to communicate downlink data signals, a physical uplink shared channel (PUSCH) used to communicate uplink data signals, and a physical sidelink shared channel (PSSCH) used to communicate sidelink data signals. Furthermore, examples of types of physical control channels include, but are not limited to, a physical downlink control channel (PDCCH) used to communicate downlink control signals, a physical uplink control channel (PUCCH) used to communicate uplink control signals, and a physical sidelink control channel (PSCCH) used to communicate sidelink control signals. As used herein for simplicity, unless otherwise specified, a physical channel of a particular type is also used to refer to a signal transmitted on that physical channel of that particular type and / or a transmission on that transmission of that particular type. By way of example, a PDSCH refers to the physical downlink shared channel itself, a downlink data signal transmitted on the PDSCH, or a downlink data transmission. Thus, a communication node transmitting or receiving a PDSCH means that the communication node is transmitting or receiving a signal on the PDSCH.

[0022] Additionally, for at least some specifications, such as 5G NR, and / or for at least some types of control signals, control signals transmitted by communication nodes may include control information containing information necessary to enable transmission of one or more data signals between communication nodes and / or to schedule one or more data channels (or one or more transmissions on a data channel). For example, such control information may include information necessary for proper reception, decoding, and demodulation of data signals received on a physical data channel during a data transmission, and / or for uplink scheduling grants that inform user devices about the resources and transport formats to use for uplink data transmission. In some embodiments, the control information includes downlink control information (DCI) transmitted in the downlink direction from the wireless access node 104 to the user device 102. In other embodiments, the control information includes uplink control information (UCI) transmitted in the uplink direction from the user device 102 to the wireless access node 104, or sidelink control information (SCI) transmitted in the sidelink direction from one user device 102(1) to another user device 102(2).

[0023] More specifically, in sidelink positioning, the user device 102 may be in different scenarios, such as coverage, partial coverage, or out-of-coverage. In the coverage and partial coverage scenarios, the user device 102 has a network connection with the wireless access node 104 and can communicate (receive and / or transmit) signals / signaling with the wireless access node 104 (e.g., a network) including the RAN node 204 and the LMF 202. At the same time, the user device 102 can interact (communicate (transmit and / or receive) signals / signaling) with other user devices 102. In the out-of-coverage scenario, the user device 102 does not have a connection with the wireless access node 104 (e.g., a network), and the user device 102 can communicate (transmit and / or receive) signals / signaling only with other user devices 102.

[0024] Also, for at least some embodiments, sidelink positioning includes Mode 1 and Mode 2. Mode 1 is for in-coverage and partial-coverage user devices 102 to explicitly receive transmit and / or receive configurations (e.g., transmit (Tx) resource pool, receive (Rx) resource pool, data / signal transmission positioning in the time and frequency domain) from the network 104 without sensing before transmission. Mode 2 is for user devices 102 that need to perform sidelink control information (SCI) sensing before transmitting data to ensure that resources are not occupied by any other user devices 102. In in-coverage scenarios, user devices 102 can operate in Mode 1 or Mode 2, which in some embodiments may rely on explicit signaling from the gNB. User devices 102 can also be configured or operated as target user devices or anchor user devices. In some embodiments, Mode 1 and Mode 2 can also be referred to as Scheme 1 and Scheme 2, respectively.

[0025] Also, for at least some implementations, the initial positioning performed by the user device 102 may use a Mobile Terminal Position Request (MT-LR) structure or a Mobile Originated Position Request (MO-LR) structure. MT-LR is an LMF-triggered position request to the user device 102 and the RAN node 204 at the very beginning of the initial positioning, which may originate at an external location service (LCS) client. Furthermore, with MO-LR, the user device 102 triggers a position request to the LMF 202 at the very beginning of the initial positioning to learn its own location. In at least some implementations, these two structures are applied to sidelink positioning.

[0026] Furthermore, positioning sessions may be set up by higher layers, and each positioning session may correspond to one service type, such as one MT-LR or one MO-LR. In an initial positioning session, communication nodes involved in one positioning session may include one LMF 202, multiple RAN nodes 204, and one user device 102. In a sidelink positioning session, communication nodes involved in one sidelink positioning session may include one LMF 202, multiple NG-RAN nodes, and multiple user devices 102. The multiple user devices 102 may include one target user device 102 and one or more anchor user devices 102 for performing sidelink positioning, or the multiple user devices 102 may include Mode 1 user devices 102, Mode 2 user devices 102, and user devices 102 performing Uu-based positioning. Also, the multiple RAN nodes 204 may include multiple serving RAN nodes 204 for multiple user devices 102 or RAN nodes 204 that support Uu-based positioning.

[0027] Also, as used herein, a sidelink positioning reference signal (SL-PRS) configuration is a set of configured parameters of an SL-PRS for transmitting sidelink signals / signaling by a user device 102. The SL-PRS configuration of a Mode 1 user device 102 (i.e., a user device configured to operate in Mode 1) may include the Tx SL-PRS resource pool of the Mode 1 user device 102.Furthermore, an SL-PRS configuration may include one or more associated SL-PRS resource pools of the SL-PRS configuration (an associated SL-PRS resource pool may be associated with one SL-PRS configuration, or one or more SL-PRS resource sets within the SL-PRS configuration, or one or more SL-PRS resources within the SL-PRS configuration; an SL-PRS resource pool may be a transmitting SL-PRS resource pool or a receiving SL-PRS resource pool), an identification (ID) of the SL-PRS (e.g., an SL-PRS resource ID, an SL-PRS resource set ID, or an SL-PRS resource configuration ID), time domain resources of the SL-PRS (e.g., periodicity of the SL-PRS resource / resource set, system frame number (SFN) offset of one SL-PRS resource / resource set, slot or symbol offset of one SL-PRS resource / resource set, number of symbols of one SL-PRS resource, and so on). or cyclic prefix of the SL-PRS resource / resource set), frequency domain resources for the SL-PRS (e.g., comb size and / or comb offset of the SL-PRS resource, bandwidth of the SL-PRS resource / resource set, starting physical resource block (PRB) of the SL-PRS resource / SL-PRS resource set, point A of the SL-PRS resource / resource set, starting subchannel of the SL-PRS resource / SL-PRS resource set, and / or number of subchannels of the SL-PRS resource / SL-PRS resource set), spatial domain resources for the SL-PRS (e.g., PRS sequence ID, QCL information of the SL-PRS resource / resource set), transmit power of each SL-PRS resource, an indication of whether the SL-PRS resource / resource set is periodic, semi-persistent, or aperiodic, or a priority index of the SL-PRS resource / SL-PRS resource set. Also, the muting pattern may be used per RAN node, or per several RAN nodes, or per SL-PRS resource or SL-PRS resource set.

[0028] Additionally, in various embodiments, the Ranging and Sidelink Positioning Protocol (RSPP), which may also be referred to as the Sidelink Positioning Protocol (SLPP), is similar to LPP on the uu interface and is a protocol between one user device 102 and another user device 102. In at least some embodiments, sidelink positioning control signaling may be conveyed by one or more RSPP messages.

[0029] Also, as used herein, SL-PRS resource contention means that SL-PRS resources transmitted from two Mode 1 user devices 102 have conflicts (or overlaps) in the time and / or frequency domains. For example, SL-PRS resource contention may occur when two user devices 102 transmit their respective SL-PRSs in the same symbol, the same PRB, or the same subchannel. In some situations, SL-PRS contention may cause two Mode 1 user devices 102 to experience interference, especially when the two Mode 1 user devices 102 are close to each other.

[0030] Furthermore, in sidelink positioning, the target user device 102 is the user device to be positioned, and the anchor user device 102 is the user device that supports positioning of the target user device 102, for example, by transmitting and / or receiving reference signals for positioning, providing positioning-related information, etc., via a sidelink (SL) interface.

[0031] Also, for sidelink communication, there may be two ways to perform resource allocation for a Mode 1 user device 102. The first way involves dynamic resource allocation, in which the user device 102 receives an RRC configuration of a resource pool and receives DCI 3-0 scrambled by the Sidelink Radio Network Temporary Identifier (SL-RNTI) to obtain dynamic sidelink resources for transmitting sidelink information. This first way may be used to allocate dynamic sidelink resources for emergency services. The second way involves configured grant (CG) resource allocation, which may include Type 1 Sidelink (SL CG) and / or Type 2 SL CG. In Type 1 SL CG, the user device 102 receives a CG configuration, which may include a resource pool ID, a CG configuration ID, a CG periodicity, and a CG resource allocation, and / or transmits sidelink information according to the indication in the RRC. In Type 2 SL CG, the user device 102 receives a CG configuration, which may include a CG index and a CG periodicity, and receives DCI 3-0 scrambled by the SL configuration scheduling (CS)-RNTI to obtain time / resource domain resources and a trigger for the CG.

[0032] 2 shows the initial Uu positioning, i.e., the structure between different communication nodes in the initial Uu positioning. In this configuration, one LMF 202 may control several (two or more) RAN nodes 204. In addition, one RAN node may include or be considered as a gNB. Furthermore, each gNB controls one or more TRPs.

[0033] The initial Uu positioning assumes, for example, DL positioning. The Uu positioning procedure may include the following: In a first operation, the LMF 202 may trigger one or more RAN nodes 204 to provide TRP information including PRS configurations. In a second operation, the one or more RAN nodes 204 may respond to the LMF 202 and provide the TRP information together with the PRS configurations. In a third operation, the LMF 202 transmits the TRP information together with the PRS configurations as assistance data to the user device 102. In a fourth operation, the LMF 202 may trigger the user device 102 to perform positioning. In a fifth operation, the user device 102 receives PRSs from different TRPs (which may belong to different RAN nodes 204) and performs measurements. In a sixth operation, the user device 102 reports measurement results and / or positioning estimates to the LMF 202. Also, for at least some embodiments, in the second operation, different RAN nodes 204 may independently provide their respective PRS configurations to the LMF 202. Each RAN node 204 may not be aware of the PRS configurations of other RAN nodes 204. Each RAN node 204 may configure one or more muting patterns to ensure that TRPs within one RAN node have non-overlapping PRS resources.

[0034] FIG. 3 illustrates an example of a sidelink positioning architecture in an in-coverage scenario.

[0035] Furthermore, for at least some embodiments, in a sidelink positioning Mode 1 scenario, different sidelink user devices 102 may have different serving gNBs. There may be one or more Mode 1 user devices 102 under the range or coverage of a single gNB, and these Mode 1 user devices 102 may perform control signaling interactions with this gNB. Mode 1 user devices 102 under the range of the same or different gNBs may receive different or non-overlapping SL-PRS configurations to avoid conflicts when transmitting SL-PRS to other sidelink user devices 102, especially for periodic SL-PRS transmissions. When different serving gNBs provide SL-PRS configurations to corresponding user devices 102, it may be possible for the user devices 102 to receive overlapping SL-PRS configurations (e.g., in the time and / or frequency domains) because the different gNBs may not coordinate their SL-PRS configurations with each other or perform contention resolution. This may cause interference when the user devices 102 transmit their respective SL-PRSs according to the SL-PRS configurations. On the other hand, if the RAN nodes 204 coordinate or otherwise perform contention resolution for their respective SL-PRS configurations, overlapping SL-PRS configurations may be avoided.

[0036] 4 is a flowchart of an example method 400 for wireless communication. At block 402, the LMF 202 and at least one RAN node 204 may perform interactions associated with at least one SL-PRS configuration. At block 404, the LMF 202 or the at least one RAN node 204 may transmit multiple non-overlapping SL-PRS configurations to multiple user devices 102 based on the interactions.

[0037] In some embodiments of method 400, at least one or each of the plurality of non-overlapping SL-PRS configurations includes at least one of a priority index of the SL-PRS resource or SL-PRS resource set, a muting pattern of the SL-PRS resource or SL-PRS resource set, a slot or symbol offset of the SL-PRS resource or SL-PRS resource set, a comb offset of the SL-PRS resource or SL-PRS resource set, a starting physical resource block (PRB) or starting subchannel of the SL-PRS resource or SL-PRS resource set.

[0038] Additionally or alternatively, in some embodiments, the LMF 202 and / or at least one RAN node 204 may determine whether a user device, e.g., one of the plurality of user devices 102, is to employ Mode 1 or Mode 2. In Mode 1, the user device 102 transmits an SL-PRS in accordance with an SL-PRS configuration transmitted by the LMF 202 or at least one RAN node 204. In Mode 2, the user device 102 transmits an SL-PRS without an SL-PRS configuration transmitted by the LMF 202 or at least one RAN node 204. Further, the LMF 202 or at least one RAN node 204 may transmit an indication of the determination to the user device.

[0039] Additionally or alternatively, the LMF 202 and / or the at least one RAN node 204 may determine whether a user device 102 of the plurality of user devices 102 is configured to perform sidelink positioning, where performing sidelink positioning includes at least one of performing sidelink positioning measurements, transmitting an SL-PRS, or receiving an SL-PRS, and may transmit an indication of the determination to the user device 102.

[0040] Additionally or alternatively, the LMF 202 and / or the at least one RAN node 204 may perform the interaction by communicating a message from the LMF 202 to the at least one RAN node 204 to request the at least one RAN node 204 to transmit to the LMF 202 at least one SL-PRS configuration for the at least one user device 102.

[0041] Additionally or alternatively, the LMF 202 and the at least one RAN node 204 may perform the interaction by communicating a message including at least one SL-PRS configuration for at least one user device from the at least one RAN node 204 to the LMF 202. In some embodiments, the LMF 202 may modify the at least one SL-PRS configuration, and the LMF 202 may communicate a message including the at least one SL-PRS configuration for the at least one user device to the at least one RAN node 204.

[0042] Additionally or alternatively, the LMF 202 and the at least one RAN node 204 may perform the interaction by communicating a message from the LMF 202 to the at least one RAN node 204 that includes at least one SL-PRS configuration for all of the multiple user devices 102 in the same positioning session.

[0043] Additionally or alternatively, the LMF 202 or at least one RAN node 204 may transmit multiple non-overlapping SL-PRS configurations, such as via a Long Term Evolution Positioning Protocol (LPP) message, with the LMF 202 transmitting at least one of the multiple non-overlapping SL-PRS configurations to at least one user device 102.

[0044] Additionally or alternatively, the LMF 202 or at least one RAN node 204 may transmit the multiple non-overlapping SL-PRS configurations, such as via radio resource control (RRC) signaling, whereby the at least one RAN node 204 transmits at least one of the multiple non-overlapping SL-PRS configurations to the at least one user device 102.

[0045] Additionally or alternatively, the LMF 202 and the at least one RAN node 204 may perform the interaction by communicating a message from the LMF 202 to the at least one RAN node 204 to trigger the at least one RAN node 204 to distribute at least one of the multiple non-overlapping SL-PRS configurations to the at least one user device 102.

[0046] Additionally or alternatively, the LMF 202 and the at least one RAN node 204 may perform the interaction by communicating a message including radio resources from the LMF 202 to the at least one RAN node 204. In some of these embodiments, the at least one RAN node 204 includes one or more RAN nodes 204 having SL-PRS resource contention with one or more other RAN nodes 204.

[0047] Additionally or alternatively, the LMF 202 and the at least one RAN node 204 may perform the interaction by communicating, from the LMF 202 to the at least one RAN node 204, a message including a RAN node identification list that identifies a set of one or more RAN nodes 204 needed to transmit the at least one SL-PRS configuration to at least one of the plurality of user devices 102. For at least some of these embodiments, the LMF 202 and the at least one RAN node 204 may perform the interaction by transmitting, from a first RAN node 204 to a second RAN node 204 identified in the RAN node identification list, the SL-PRS configuration of the first RAN node 204. Additionally or alternatively, the LMF 202 and the at least one RAN node 204 may perform the interaction by transmitting, from the first RAN node 204 to a second RAN node 204 identified in the RAN node identification list, a request to receive the SL-PRS configuration of the second RAN node 204.

[0048] In any of the various embodiments, the message includes an identification of the user device.

[0049] Additionally or alternatively, a first user device 102 of the plurality of user devices 102 may receive the SL-PRS from a second user device 102 of the plurality of user devices 102. For at least some of these embodiments, the SL-PRS is scheduled by sidelink control information (SCI) or downlink control information (DCI). Also, in some embodiments in which the SL-PRS is scheduled by SCI, the SCI is scheduled by downlink control information (DCI), long-term evolution positioning protocol (LPP) signaling, or radio resource control (RRC) signaling. Additionally or alternatively, if the SCI is scheduled by LPP signaling or RRC signaling, the LPP signaling or RRC signaling includes a time offset between transmission of the LPP signaling or RRC signaling and transmission of the SCI. Additionally or alternatively, for embodiments in which the SL-PRS is scheduled by the SCI, the SCI may be scheduled by downlink control information (DCI), and the DCI may include a time offset between transmission of the DCI and transmission of the SCI.

[0050] Further details of the operation of various aspects or embodiments of the method 400 and / or the components' functionality of the wireless system 100 will now be described.

[0051] Also, in at least some implementations, when the LMF 202 coordinates the SL-PRS configurations of different RAN nodes 204, the LMF may know, determine, or decide the sidelink positioning method of the in-coverage target user device 102, sidelink positioning session information, and whether the target user device 102 and the anchor user device 102 in one sidelink positioning session employ Mode 1 or Mode 2. In certain embodiments, the LMF 202 determines or decides the sidelink positioning method of the target user device 102 and may communicate or notify the user device 102 via LPP, etc., and / or the gNB via NRPPa, etc. Furthermore, the LMF 202 may know and communicate or notify the user device 102 via LPP, etc., and / or the RAN node 204 via NRPPa, etc., about the sidelink positioning session information (e.g., which user devices 102 and / or which RAN nodes 204 are in the same sidelink positioning session). Also, for at least some embodiments, the LMF 202 may determine whether an in-coverage sidelink user device 102 in a sidelink positioning session is to employ Mode 1, Mode 2, or Uu-based positioning, and may communicate or notify the user device 102 via, e.g., LPP, and / or the RAN node 204 via, e.g., NRPPa. Additionally or alternatively, the RAN node 204 may determine whether an in-coverage user device 102 (under the range of the RAN node) in a sidelink positioning session is to employ Mode 1, Mode 2, or Uu-based positioning, and may communicate or notify the user device 102 via, e.g., RRC signaling, and / or the LMF 202 via, e.g., NRPPa.

[0052] Additionally, for at least some implementations, the LMF 202 may determine whether the target user device 102 is adapted to employ only PC5 positioning (e.g., if the target user device 102 transmits and / or receives only SL-PRS and makes SL-PRS measurements, but in an in-coverage scenario, can receive control signaling for sidelink communications from the wireless access node 104), or whether the target user device 102 is adapted to employ a combination of PC5 and Uu positioning (if the target user device 102 performs sidelink positioning over the PC5 interface via RSPP, and the target user device 102 also receives downlink positioning reference signals (DL-PRS) or transmits sounding reference signals (SRS) and makes DL-PRS measurements according to the original LPP / RRC configuration).

[0053] Additionally, for at least some embodiments, the LMF may coordinate based on the implementation of the LMF 202. In particular, after the LMF 202 learns the positioning requirements from the location services (LCS) client (MT-LR) or the target user device 102 (MO-LR) and that sidelink positioning for the target user device 102 may be used or required, the operations performed to obtain the network's configured SL-PRS configuration for the mode 1 user device 102 to transmit SL-PRS may be performed as follows (not necessarily in the order described herein):

[0054] In a first operation, the LMF 202 may send a request message over the NRPPa to trigger each RAN node 204 (involved in this sidelink positioning session) to provide their respective SL-PRS configurations to the Mode 1 user devices 102 under their respective range. In some embodiments, the request message may include the UE identification of the Mode 1 UE.

[0055] In the second operation, each RAN node 204 may receive the request message from the LMF 202 and configure SL-PRS configurations for the Mode 1 user devices 102 under its respective coverage. In addition, each RAN node 204 may consider real-time radio resources to prevent overlapping of SL-PRS configurations for different Mode 1 user devices 102 under the same RAN node 204. Each NG-RAN node 204 may then provide a response message to the LMF 202, where the response message includes the configured / assigned SL-PRS configurations for each Mode 1 user device 102. For example, each RAN node 204 may provide a user device ID list, where each user device ID in the user device ID list corresponds to a respective SL-PRS configuration. In some embodiments, the RAN node 204 may also provide a corresponding update or failure message for the LMF request in the first operation.

[0056] In a third operation, after the LMF 202 receives or acquires all of the SL-PRS configurations of the RAN nodes 204, the LMF 202 may resolve any interference by or in accordance with its implementation. For example, the LMF 202 may remove some of the overlapping SL-PRS resources of some of the RAN nodes 204. The LMF 202 may then provide the non-overlapping SL-PRS configurations to the Mode 1 user device 102, for example, via LPP signaling. The LMF 202 may also provide the Mode 1 user device 102 with the SL-PRS configuration that is the configuration of the serving RAN node 204 of the Mode 1 user device 102.

[0057] Additionally or alternatively, in some embodiments, the LMF 202 coordinates with the gNB. In such embodiments, after the LMF 202 learns the positioning requirements from the LCS client (MT-LR) or the target user device 102 (MO-LR) and that sidelink positioning is required for the target user device 102, the operations performed to obtain the network's configured SL-PRS configuration for the mode 1 user device 102 to transmit SL-PRS may be performed as follows (not necessarily in the order described herein):

[0058] In a first operation, the LMF 202 may send a request message, such as via an NRPPa, to trigger each RAN node 204 (involved in this sidelink positioning session) to provide its respective SL-PRS configuration to the Mode 1 user device 102 under its respective range. In some embodiments, the request message may include the UE identification of the Mode 1 user device 102. Additionally or alternatively, the request message may include a request from the LMF 202 to the RAN node 204 to deliver the SL-PRS configuration to the corresponding Mode 1 user device 102.

[0059] In a second operation, each RAN node 204 may receive the request message of the LMF 202 and configure SL-PRS configurations for the Mode 1 user devices 102 under its coverage. The RAN node 204 may consider real-time radio resources to ensure that the SL-PRS configurations of different Mode 1 user devices 102 do not overlap. Each RAN node 204 then provides a response message to the LMF 202 including the configured / assigned SL-PRS configurations for each Mode 1 user device 102. For example, the RAN node 204 may provide a user device ID list, where each user device ID in the user device ID list corresponds to a respective SL-PRS configuration. Additionally, in some embodiments, the RAN node 204 may provide a corresponding update message or failure message for the LMF request in the first operation.

[0060] In a third operation, for some embodiments, after the LMF 202 obtains all of the SL-PRS configurations of the RAN nodes 204, the LMF 202 may recommend some radio resources to some of the RAN nodes 204 that have SL-PRS resources that conflict with other RAN nodes. The LMF may make the recommendation to avoid SL-PRS resource contention between the RAN nodes 204. Also, as used herein, "recommend" may include sending a message. Thus, when the LMF 202 recommends radio resources to a RAN node 204, the LMF 202 may make the recommendation by sending a message including the radio resources to the RAN node 204 via NRPPa signaling, for example. Also, the radio resources that the LMF 202 recommends to one RAN node 204 do not overlap with the radio resources of other RAN nodes 204. In any of various embodiments, the radio resources may include at least one of the following: SFN0 offset of the SL-PRS resource / resource set, slot or symbol offset of the SL-PRS resource / resource set, periodicity of the SL-PRS resource / resource set, number of symbols of the SL-PRS resource / resource set, cyclic prefix of the SL-PRS resource / resource set, repetition number of the SL-PRS resource / resource set, bandwidth of the SL-PRS resource / resource set, starting PRB of the SL-PRS resource / resource set, point A of the SL-PRS resource / resource set, comb size of the sidelink PRS resource / resource set, comb offset of the sidelink PRS resource / resource set, PRS sequence ID, quasi-co-location (QCL) information of the SL-PRS resource / resource set, power of each SL-PRS resource, priority index of each SL-PRS resource / resource set, or muting pattern for each NG-RAN node. The NRPPa message may also include a user device identification associated with the radio resources.

[0061] In another embodiment of the third operation, once the LMF 202 obtains all of the SL-PRS configurations from the RAN nodes 204, the LMF 202 may transmit the SL-PRS configurations to a set of RAN nodes (which may include less than all of the RAN nodes 204) that include RAN nodes that the LMF 202 identifies as having SL-PRS resources that overlap with the SL-PRS resources of one or more other RAN nodes 204, or that include all of the RAN nodes 204 that transmit SL-PRS configurations to Mode 1 user devices 102.

[0062] In yet another embodiment of the third operation, the LMF 202 may configure the muting pattern according to the SL-PRS configuration of the NG-RAN node. In any of various embodiments, the muting pattern may be configured per RAN node 204 per user device 102, per RAN node 204, or per SL-PRS resource set. The use of the muting pattern is to ensure that each RAN node 204 has a non-overlapping SL-PRS configuration in resources. In at least some embodiments, the muting pattern is a bitmap. In some embodiments of the bitmap, a value of 1 indicates the SL-PRS resource ID or SL-PRS resource set ID that the RAN node 204 configures for one user device 102. The LMF 202 may also transmit the muting pattern to the corresponding NG-RAN node 204. Additionally or alternatively, the muting pattern is part of the SL-PRS configuration.

[0063] In a fourth operation, the RAN node 204 may modify the SL-PRS configuration according to the recommendation of the LMF 204. The RAN node 204 may send a response message to the LMF 202 including the modified SL-PRS configuration for each mode 1 user device 102.

[0064] In a fifth operation, the LMF 202 may distribute the SL-PRS configuration of each RAN node 204 to each Mode 1 user device 102. In some embodiments, the LMF 202 may send a message requesting the RAN node 204 to distribute the SL-PRS configuration to the corresponding Mode 1 user device 102. In at least some embodiments, the request message may be the same as the request message sent in the previous operation. In other embodiments, the request message may be a separate message in the NRPPa signaling. The RAN node 204 may also distribute the modified SL-PRS configuration to each Mode 1 user device 102.

[0065] Furthermore, in some embodiments, the LMF 202 may request that the gNBs coordinate with each other. In doing so, the LMF 202 may need to know or determine the sidelink positioning method of the in-coverage target user device 102, the sidelink positioning session information, and whether the target user device 102 and the anchor user device 102 in a sidelink positioning session are configured to employ Mode 1 or Mode 2. In certain embodiments, the LMF may determine the sidelink positioning method of the target user device 102 and communicate or notify the user device 102 via LPP or the like and / or the NRPPa or the like to the gNB. Additionally or alternatively, the LMF 202 may know the sidelink positioning session information (e.g., which user devices 102 and / or which RAN nodes 204 are in the same sidelink positioning session) and communicate or notify the user device 102 via LPP or the like and / or the RAN node 204 via NRPPa or the like. The LMF 202 may determine whether the sidelink user device 102 should or is to employ Mode 1 or Mode 2 in a sidelink positioning session and communicate or inform the user device 102 via the LPP and / or the NG-RAN node 204 via the NRPPa, etc.

[0066] In some embodiments, the LMF 202 may request coordination from all RAN nodes 202, such that one or more SL-PRS configurations are modified. In such embodiments, after the LMF 202 learns the positioning requirements from the LCS client (MT-LR) or the target user device 102 (MO-LR) and that sidelink positioning is required for the target user device 102, the operations performed to obtain the network's configured SL-PRS configuration for the Mode 1 user device 102 to transmit SL-PRS may be performed as follows (not necessarily in the order described herein):

[0067] In a first operation, the LMF 202 may send a request message, such as via an NRPPa, to trigger each RAN node 204 (involved in this sidelink positioning session) to provide the SL-PRS configuration to the Mode 1 user device 102 under its respective range. In some embodiments, the request message may include the identification of the Mode 1 user device 102.

[0068] In a second operation, the LMF 202 may send a request message to each RAN node 204. The request message may include a RAN node ID list including one or more of the IDs of the RAN nodes 204 to configure the SL-PRS configuration for the Mode 1 user device 102. The request message is to request each RAN node 204 to coordinate the SL-PRS configuration with the RAN nodes 204 in the RAN node ID list, which may avoid SL-PRS resource contention between different RAN nodes 204.

[0069] In a third operation, each RAN node 204 may set up an Xn interface with other RAN nodes 204 indicated in the RAN node ID list. Additionally, in some embodiments, the NG-RAN node 204 may send its own SL-PRS configuration to other RAN nodes over the Xn interface. In other embodiments, the RAN node 204 may send a request message to other RAN nodes 204 in the NG-RAN node list to request that they provide their SL-PRS configuration over the Xn interface.

[0070] In a fourth operation, after the third operation, each RAN node 204 may assume that it has the SL-PRS configuration of the other RAN node 204. In response, each RAN node 204 may modify its SL-PRS configuration so that it does not overlap with one another. For example, if there are a total of two RAN nodes 204 requested by the LMF 202 to coordinate their SL-PRS configurations, the first RAN node 204 may send its SL-PRS configuration to the second RAN node 204, and in response, the second RAN node 204 may determine whether an SL-PRS configuration conflict exists. If so, the second RAN node 204 may modify its SL-PRS configuration. In other embodiments, the second RAN node 204 may send a non-overlapping SL-PRS to the first RAN node 204.

[0071] In a fifth operation, each RAN node 204 may provide a non-overlapping SL-PRS configuration to the LMF 202. In a sixth operation, each RAN node 204 may provide a non-overlapping SL-PRS configuration to a corresponding Mode 1 user device 102. In a seventh operation, the LMF 202 may provide a non-overlapping SL-PRS configuration of a different RAN node 204 to a corresponding Mode 1 user device 102.

[0072] Additionally, in some embodiments, the LMF may request one RAN node to adjust the SL-PRS configuration. For such embodiments, after the LMF 202 learns the positioning requirements from the LCS client (MT-LR) or the target user device 102 (MO-LR) and learns that sidelink positioning is required for the target user device 102, operations to obtain the network's configured SL-PRS configuration for the mode 1 user device 102 to transmit SL-PRS may be performed as follows (not necessarily in the order described herein):

[0073] In a first operation, the LMF 202 may send a request message to one of one or more RAN nodes. The request message may include an NG-RAN node ID list including one or more IDs of NG-RAN nodes needed to configure the SL-PRS configuration for the Mode 1 user device 102. The request message may be to request the RAN node 204 to coordinate the SL-PRS configuration with the RAN nodes 204 in the RAN node ID list to avoid SL-PRS resource contention between different RAN nodes 204. The requested RAN node 204 may be a serving RAN node 204 (e.g., a serving gNB) of the target user device 102.

[0074] In a second operation, the RAN node 204 may set up an Xn interface with the other RAN nodes 204 indicated in the RAN node ID list, and the RAN node 204 may send its own SL-PRS configuration to the other RAN nodes over the Xn interface. In another embodiment, the RAN node 204 may send a request message to the other RAN nodes 204 in the RAN node list, requesting the other RAN nodes 204 to provide their respective SL-PRS configurations.

[0075] In a third operation, after receiving one RAN node's SL-PRS configuration, the other RAN node 204 may configure a non-overlapping SL-PRS configuration. For example, if the LMF 202 requests the first RAN node 204 to coordinate with the second RAN node 204, the first RAN node 204 may send its own SL-PRS configuration to the second RAN node 204, and in response, the second RAN node 204 may configure a non-overlapping SL-PRS configuration with the first RAN node 204. In other embodiments, the second RAN node may send a non-overlapping SL-PRS to the first RAN node 204.

[0076] In a fourth operation, the RAN nodes 204 requested in the first operation may provide the non-overlapping SL-PRS configurations of all RAN nodes 204 to the LMF 202. In a fifth operation, each RAN node 204 may provide the non-overlapping SL-PRS configurations to their corresponding Mode 1 user devices 102. In a sixth operation, the LMF 202 may provide the non-overlapping SL-PRS configurations of different RAN nodes 204 to their corresponding Mode 1 user devices 102.

[0077] Additionally, for at least some embodiments, SL-PRS transmission by the user device 102 may support at least one of dynamic resource allocation, Type 1 SL CG, or Type 2 SL CG. The gNB may also determine whether the Mode 1 user device 102 is configured to employ dynamic resource allocation, Type 1 SL CG, or Type 2 SL CG and indicate that determination to the user device 102. In particular embodiments, for dynamic resource allocation, the serving RAN 204 node may provide a first subset of one or more SL-PRS configurations to the Mode 1 user device 102 via RRC signaling, etc., and may provide a second subset of one or more SL-PRS configurations to the Mode 1 user device 102 via DCI. In addition, in the case of Type 1 SL PRS CG, the serving RAN node 204 or LMF 202 may transmit the entire or complete set of SL-PRS configurations to the Mode 1 user device 102. Additionally, for a Type-2 SL PRS CG, the serving RAN node 204 may provide a third subset of one or more SL-PRS configurations and a CG configuration to the Mode 1 user device 102, such as via RRC signaling, and may provide a fourth subset of one or more SL-PRS configurations to the Mode 1 user device 102, such as via DCI. In other embodiments, for a Type-2 SL PRS CG, the serving RAN node 204 may provide the entire or complete set of SL-PRS and CG configurations to the Mode 1 user device 102 and trigger the user device 102 to transmit its respective SL-PRS, such as via DCI.

[0078] Also, for at least some embodiments, the CG configuration may include at least one of a CG index, a periodicity of the CG, a time domain resource for the CG, a frequency domain resource for the CG, an associated resource pool ID, and a PUCCH resource for feedback to the network 104. The CG configuration may be dedicated to the SL-PRS, may be different from the CG configuration for the sidelink data, or the CG configuration for the SL-PRS may reuse the CG configuration for the sidelink data.

[0079] Additionally, for at least some embodiments, the DCI may be a DCI format DCI xy, where x and y are both integers, which may be the same as or different from an existing DCI format. The DCI for the Type-2 SL PRS CG may be different or independent from the DCI for dynamic resource allocation, or the two types of DCI may share the same DCI format but with different scrambling. The DCI may include at least one of a time offset between the DCI and the SCI scheduling the SL-PRS, an SL-PRS resource ID / resource set ID on which the user device 102 is indicated to transmit the SL-PRS, one or more triggered CG indices, time domain resources of the SL-PRS / SL-PRS resource set, frequency domain resources of the SL-PRS / SL-PRS resource set, or spatial domain resources of the SL-PRS / SL-PRS resource set. Additionally, in any of the various embodiments, the RAN node 204 may communicate or inform the LMF 202 whether the Mode 1 user device 102 supports dynamic resource allocation, Type 1 SL PRS CG, or Type 2 SL PRS CG.

[0080] Additionally, in embodiments in which the LMF 202 distributes the SL-PRS configuration to each Mode 1 user device, such as via LPP signaling, if the SL-PRS resources are aperiodic, the user device 102 may send an SCI to trigger SL-PRS transmission. Additionally or alternatively, if the SL-PRS resources are periodic, when the user device 102 receives the SL-PRS configuration LPP message, the user device 102 may begin periodic SL-PRS transmission in accordance with the SL-PRS configuration.

[0081] Additionally, Mode 1 may include at least one of: the network 104 assigning a periodic SL-PRS configuration to the user device 102; the gNB assigning a periodic SL-PRS configuration to the user device 102 via RRC; the gNB assigning a semi-persistent or aperiodic SL-PRS configuration to the user device 102 via RRC signaling, medium access control control element (MAC-CE) or DCI triggering an SCI and / or SL-PRS transmission; the LMF 202 assigning a periodic SL-PRS configuration via LPP; the LMF 202 assigning a semi-persistent or aperiodic SL-PRS configuration via LPP or SCI triggering an SL-PRS transmission.

[0082] Additionally or alternatively, in embodiments in which the RAN node 204 distributes the SL-PRS configuration to each Mode 1 user device 102, such as via RRC signaling, the user device 102 may receive a DCI containing a trigger for an SCI to schedule the SL-PRS or containing a trigger for aperiodic SL-PRS if the SL-PRS resources are aperiodic. In other embodiments, the user device 102 may transmit an SCI to trigger the SL-PRS if the SL-PRS resources are aperiodic. In certain of these embodiments, the user device 102 may transmit an SCI without receiving an SCI or a DCI to trigger the SL-PRS. Additionally or alternatively, in embodiments in which the SL-PRS resources are semi-persistent, the user device 102 may receive a medium access control element (MAC-CE) containing a trigger for an SCI to schedule the SL-PRS or containing a trigger for aperiodic SL-PRS. Also, for embodiments in which the SL-PRS resources are periodic, the user device 102 may begin transmitting the SL-PRS in accordance with the periodic SL-PRS configuration immediately after the user device 102 receives the RRC signaling. Additionally, in some embodiments, the LPP signaling or RRC signaling may include a time offset between the LPP signaling or RRC signaling and the SCI transmission.

[0083] Furthermore, in some embodiments, the DCI may have a DCI xy format, where x and y are both integers, which may be the same as or different from an existing DCI format. If the DCI format reuses an existing DCI format, some new fields may be included. The DCI, SCI, or MAC-CE may include at least one of the following: a resource pool associated with the triggered SL-PRS resource / resource set; a time offset between the DCI and the SCI scheduling the SL-PRS; a time offset between the DCI and the first SL-PRS resource / resource set instance; a time offset between the SCI and the first SL-PRS resource / resource set instance; an SL-PRS resource ID / resource set ID on which the user device 102 is indicated to transmit the SL-PRS; a time domain resource of the SL-PRS / SL-PRS resource set; a frequency domain resource of the SL-PRS / SL-PRS resource set; or a spatial domain resource of the SL-PRS / SL-PRS resource set. Furthermore, in any of the various embodiments, the time offset has units of milliseconds, slots, and / or symbols.

[0084] Additionally, when an SL-PRS configuration is provided to a Mode 1 user device 102, a priority index for the SL-PRS resource / resource set may also be provided. The priority index may be a one-bit value that conveys or informs the user device 102 whether the SL-PRS resource / resource set may be transmitted by the user device 102. In some embodiments, the priority index may be configured by the LMF 202 after the LMF 202 acquires all of the SL-PRS configurations of the RAN node 204. Furthermore, the LMF 202 may transmit the priority index associated with each SL-PRS resource / resource set to the user device 102, such as via LPP signaling. Additionally or alternatively, the LMF 202 may convey the muting patterns for all SL-PRS / SL-PRS resource sets in the RAN node 204 to each RAN node 204, such as via NRPPa signaling. The NG-RAN node 204 may then transmit the SL-PRS configuration with the priority index to a particular user device 102, such as via RRC signaling. In other embodiments, the LMF 202 may communicate or inform each RAN node 204, such as via NRPPa, of the muting patterns for all SL-PRS / SL-PRS resource sets within the RAN node 204 for a particular user device 102. The RAN node 204 may then communicate or transmit, such as via RRC signaling, the SL-PRS configuration including the priority index to the user device. In this case, the muting pattern may be the priority index. In other embodiments, the user device may also receive an association between the priority index and the SL-PRS resource ID / resource set ID in the DCI.

[0085] The above description and accompanying drawings provide specific exemplary embodiments and implementations. However, the described subject matter may be embodied in a variety of different forms, and therefore, it is intended that the covered or claimed subject matter not be construed as limited to any exemplary embodiments set forth herein. A reasonably broad scope of claimed or covered subject matter is intended. Among other things, for example, the subject matter may be embodied as a method, device, component, system, or non-transitory computer-readable medium for storing computer code. Accordingly, embodiments may take the form of, for example, hardware, software, firmware, a storage medium, or any combination thereof. For example, the method embodiments described above may be implemented by a component, device, or system including a memory and a processor by executing computer code stored in the memory.

[0086] Throughout this specification and the claims, terms may have nuances that are suggested or implied in context beyond their explicitly stated meaning. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, claimed subject matter is intended to include, in whole or in part, combinations of the example embodiments.

[0087] Generally, terminology can be understood, at least in part, from its usage in context. For example, terms such as "and," "or," or "and / or" as used herein can include a variety of meanings that can depend, at least in part, on the context in which such terms are used. Typically, "or" when used to relate a list such as A, B, or C is intended to mean A, B, and C, which is used here in an inclusive sense, and A, B, or C, which is used here in an exclusive sense. Additionally, the term "one or more" as used herein may be used to describe any feature, structure, or characteristic in a singular sense, or may be used to describe a combination of features, structures, or characteristics in a plural sense, depending, at least in part, on the context. Similarly, terms such as "a," "an," or "the" may be understood to convey singular usage or to convey plural usage, depending, at least in part, on the context. Additionally, the term "based on" may be understood as not intended to convey a necessarily exclusive set of factors, but may instead allow for the existence of additional factors not necessarily explicitly described, depending at least in part on the context.

[0088] References to features, advantages, or similar language throughout this specification do not imply that all of the features and advantages that may be realized by the solution should or are included in any single implementation thereof. Rather, language referring to features and advantages is understood to mean that the particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the solution. Thus, descriptions of features and advantages, and similar language throughout this specification may, but do not necessarily, refer to the same embodiment.

[0089] Furthermore, the described features, advantages, and characteristics of the solution may be combined in any suitable manner in one or more embodiments. As will be appreciated by those skilled in the art in light of the description herein, the solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in particular embodiments that may not be present in all embodiments of the solution.

[0090] The subject matter of the present disclosure may also relate to or include, among other aspects, the following:

[0091] A first aspect includes a method for wireless communications that includes performing, with a Location Management Function (LMF) and at least one Radio Access Network (RAN) node, an interaction associated with at least one Sidelink Positioning Reference Signal (SL-PRS) configuration, and transmitting, with the LMF or the at least one RAN node, multiple non-overlapping SL-PRS configurations to multiple user devices based on the interaction.

[0092] A second aspect includes the first aspect and further includes that the at least one SL-PRS configuration includes at least one of a priority index of the SL-PRS resource or SL-PRS resource set, a muting pattern of the SL-PRS resource or SL-PRS resource set, a slot or symbol offset of the SL-PRS resource or SL-PRS resource set, a comb offset of the SL-PRS resource or SL-PRS resource set, a starting physical resource block (PRB) or a starting subchannel of the SL-PRS resource or SL-PRS resource set.

[0093] A third aspect includes either the first or second aspect and further includes: determining, with the LMF or at least one RAN node, whether a user device is to employ Mode 1 or Mode 2, wherein, for Mode 1, the user device transmits SL-PRS in accordance with the SL-PRS configuration transmitted by the LMF or at least one RAN node, and, for Mode 2, the user device transmits SL-PRS without the SL-PRS configuration transmitted by the LMF or at least one RAN node; and transmitting, with the LMF or at least one RAN node, an indication of the determination to the user device.

[0094] A fourth aspect includes any of the first to third aspects and further includes: determining, with the LMF or at least one RAN node, whether the user device is configured to perform sidelink positioning, where performing sidelink positioning includes at least one of performing sidelink positioning measurements, transmitting an SL-PRS, or receiving an SL-PRS; and transmitting, with the LMF or at least one RAN node, an indication of the determination to the user device.

[0095] A fifth aspect includes any of the first to fourth aspects and further includes: performing the interaction includes communicating a message from the LMF to the at least one RAN node to request the at least one RAN node to transmit at least one SL-PRS configuration for the at least one user device to the LMF.

[0096] A sixth aspect includes any of the first to fifth aspects and further includes wherein performing the interaction further includes communicating, from the at least one RAN node to the LMF, a message including at least one SL-PRS configuration for the at least one user device.

[0097] A seventh aspect includes the sixth aspect and further includes modifying, with the LMF, at least one SL-PRS configuration; and communicating, from the LMF to at least one RAN node, a message including the at least one SL-PRS configuration for the at least one user device.

[0098] An eighth aspect includes any of the first to seventh aspects and further includes wherein performing the interaction further includes communicating a message from the LMF to the at least one RAN node including at least one SL-PRS configuration for all of a plurality of user devices in the same positioning session.

[0099] A ninth aspect includes any of the first to eighth aspects and further includes that transmitting the plurality of non-overlapping SL-PRS configurations includes transmitting at least one of the plurality of non-overlapping SL-PRS configurations to the at least one user device via a Long Term Evolution Positioning Protocol (LPP) message using an LMF.

[0100] A tenth aspect includes any of the first to ninth aspects and further includes transmitting the plurality of non-overlapping SL-PRS configurations includes transmitting, with the at least one RAN node, at least one of the plurality of non-overlapping SL-PRS configurations to the at least one user device via radio resource control (RRC) signaling.

[0101] An eleventh aspect includes any of the first to tenth aspects and further includes: performing the interaction includes communicating a message from the LMF to the at least one RAN node to trigger the at least one RAN node to distribute at least one of the plurality of non-overlapping SL-PRS configurations to the at least one user device.

[0102] A twelfth aspect includes any of the first to eleventh aspects and further includes: performing the interaction includes communicating a message from the LMF to the at least one RAN node that includes the radio resource.

[0103] A thirteenth aspect includes the twelfth aspect and further includes: the at least one RAN node comprises one or more RAN nodes having SL-PRS resource contention with one or more other RAN nodes.

[0104] A fourteenth aspect includes any of the first to thirteenth aspects and further includes: performing the interaction includes communicating, from the LMF to the at least one RAN node, a message including a RAN node identification list that identifies a set of one or more RAN nodes necessary to transmit at least one SL-PRS configuration to at least one of the plurality of user devices.

[0105] A fifteenth aspect includes the fourteenth aspect and further includes: the at least one RAN node comprises a first RAN node and a second RAN node; and performing the interaction further includes transmitting an SL-PRS configuration of the first RAN node from the first RAN node to the second RAN node identified in the RAN node identification list.

[0106] A sixteenth aspect includes the fourteenth aspect and further includes that performing the interaction further includes sending a request from the first RAN node to a second RAN node identified in the RAN node identification list to receive the SL-PRS configuration of the second RAN node.

[0107] A seventeenth aspect includes any of the fifth to eighth, eleventh, twelfth, or fourteenth aspects and further includes that the message includes an identification of the user device.

[0108] An eighteenth aspect includes any of the first to seventeenth aspects and further includes receiving, with the first user device, an SL-PRS from the second user device.

[0109] A nineteenth aspect includes the eighteenth aspect and further includes that the SL-PRS is scheduled by sidelink control information (SCI) or downlink control information (DCI).

[0110] A twentieth aspect includes the nineteenth aspect and further includes that the SL-PRS is scheduled by the SCI, and the SCI is scheduled by downlink control information (DCI), long-term evolution positioning protocol (LPP) signaling, or radio resource control (RRC) signaling.

[0111] A 21st aspect includes the 19th aspect and further includes that the SCI is scheduled by LPP signaling or RRC signaling, and the LPP signaling or RRC signaling includes a time offset between transmission of the LPP signaling or RRC signaling and transmission of the SCI.

[0112] A 22nd aspect includes the 19th aspect and further includes that the SL-PRS is scheduled by an SCI, the SCI is scheduled by downlink control information (DCI), and the DCI includes a time offset between transmission of the DCI and transmission of the SCI.

[0113] A twenty-third aspect includes a wireless communications apparatus comprising a processor and a memory, the processor configured to read code from the memory to implement any of the first to twenty-second aspects.

[0114] A twenty-fourth aspect includes a computer program product comprising a computer-readable program medium having code stored thereon, the code, when executed by a processor, causing the processor to perform any of the first to twenty-second aspects.

[0115] In addition to the features mentioned in each of the independent aspects listed above, some examples may exhibit, alone or in combination, optional features mentioned in dependent aspects and / or disclosed in the above description and illustrated in the figures.

Claims

1. 1. A method for wireless communication, the method comprising: performing, with a Location Management Function (LMF) and at least one Radio Access Network (RAN) node, interactions associated with at least one Sidelink Positioning Reference Signal (SL-PRS) configuration; using the LMF or the at least one RAN node to transmit multiple non-overlapping SL-PRS configurations to multiple user devices based on the interaction; A method comprising:

2. 2. The method of claim 1, wherein the at least one SL-PRS configuration includes at least one of a priority index of the SL-PRS resource or the SL-PRS resource set, a muting pattern of the SL-PRS resource or the SL-PRS resource set, a slot or symbol offset of the SL-PRS resource or the SL-PRS resource set, a comb offset of the SL-PRS resource or the SL-PRS resource set, and a starting physical resource block (PRB) or starting subchannel of the SL-PRS resource or the SL-PRS resource set.

3. determining, using the LMF or the at least one RAN node, whether a user device is adapted to adopt Mode 1 or Mode 2, wherein in Mode 1, the user device transmits an SL-PRS according to an SL-PRS configuration transmitted by the LMF or the at least one RAN node, and in Mode 2, the user device transmits the SL-PRS without the SL-PRS configuration transmitted by the LMF or the at least one RAN node; transmitting, using the LMF or the at least one RAN node, an indication of the determination to the user device; The method of claim 1 further comprising:

4. determining, using the LMF or the at least one RAN node, whether a user device is adapted to perform sidelink positioning, wherein the performing sidelink positioning includes at least one of performing sidelink positioning measurements, transmitting a sidelink-based PRS, or receiving the sidelink-based PRS; and transmitting, using the LMF or the at least one RAN node, an indication of the determination to the user device; The method of claim 1 further comprising:

5. Executing the interaction includes: communicating a message from the LMF to the at least one RAN node to request the at least one RAN node to transmit at least one SL-PRS configuration of at least one user device to the LMF; The method of claim 1 , comprising:

6. Executing the interaction includes: communicating a message from the at least one RAN node to the LMF, the message including at least one SL-PRS configuration for at least one user device; The method of claim 1 further comprising:

7. modifying the at least one SL-PRS configuration using the LMF; and communicating a message from the LMF to the at least one RAN node, the message including the at least one SL-PRS configuration of the at least one user device; The method of claim 6 further comprising:

8. Executing the interaction includes: communicating a message from the LMF to at least one RAN node, the message including at least one SL-PRS configuration for all of the plurality of user devices in the same positioning session; The method of claim 1 further comprising:

9. 2. The method of claim 1, wherein transmitting the plurality of non-overlapping SL-PRS configurations comprises transmitting at least one of the plurality of non-overlapping SL-PRS configurations to at least one user device via a Long Term Evolution Positioning Protocol (LPP) message using the LMF.

10. 2. The method of claim 1, wherein transmitting the plurality of non-overlapping SL-PRS configurations comprises transmitting, with the at least one RAN node, at least one of the plurality of non-overlapping SL-PRS configurations to at least one user device via radio resource control (RRC) signaling.

11. Executing the interaction includes: communicating a message from the LMF to the at least one RAN node to trigger the at least one RAN node to distribute at least one of the plurality of non-overlapping SL-PRS configurations to at least one user device; The method of claim 1 , comprising:

12. Executing the interaction includes: communicating a message from the LMF to the at least one RAN node, the message including radio resources. The method of claim 1 , comprising:

13. The method of claim 12 , wherein the at least one RAN node comprises one or more RAN nodes having SL-PRS resource contention with one or more other RAN nodes.

14. Executing the interaction includes: communicating a message from the LMF to the at least one RAN node, the message including a RAN node identification list identifying a set of one or more RAN nodes required to transmit at least one SL-PRS configuration to at least one of the plurality of user devices; The method of claim 1 , comprising:

15. The at least one RAN node comprises a first RAN node and a second RAN node, and performing the interaction includes: transmitting an SL-PRS configuration of the first RAN node from the first RAN node to the second RAN node identified in the RAN node identification list; 15. The method of claim 14, further comprising:

16. Executing the interaction includes: sending a request from a first RAN node to a second RAN node identified in the RAN node identification list to receive the SL-PRS configuration of said second RAN node; 15. The method of claim 14, further comprising:

17. 15. The method of claim 5, wherein the message includes an identification of the user device.

18. Receiving, using a first user device, an SL-PRS from a second user device The method of claim 1 further comprising:

19. The method of claim 18, wherein the SL-PRS is scheduled by sidelink control information (SCI) or downlink control information (DCI).

20. 20. The method of claim 19, wherein the SL-PRS is scheduled by the SCI, and the SCI is scheduled by Downlink Control Information (DCI), Long Term Evolution Positioning Protocol (LPP) signaling, or Radio Resource Control (RRC) signaling.

21. 20. The method of claim 19, wherein the SCI is scheduled by the LPP signaling or the RRC signaling, and the LPP signaling or the RRC signaling includes a time offset between the transmission of the LPP signaling or the RRC signaling and the transmission of the SCI.

22. 20. The method of claim 19, wherein the SL-PRS is scheduled by the SCI, the SCI is scheduled by downlink control information (DCI), and the DCI includes a time offset between transmission of the DCI and transmission of the SCI.

23. 23. A wireless communications device comprising a processor and a memory, the processor configured to read code from the memory to implement a method according to any preceding claim.

24. 23. A computer program product comprising a computer readable program medium having stored thereon code which, when executed by a processor, causes the processor to perform a method according to any of claims 1 to 22.

Citation Information

Patent Citations

  • Method and apparatus for user device positioning based on sidelink

    WO2022184240A1

  • Management of resource pools for positioning in sidelink

    WO2022191912A1