Transmission of position reference signal configuration for wireless communication

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.

Description

Technical Field

[0001] Technical Field This document generally relates to sidelink positioning for wireless communication.

Background Art

[0002] Background In the scenario of sidelink positioning mode 1, different sidelink user devices may have different serving gNBs. There may be one or more mode 1 user devices within 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 positioning reference signal (SL - PRS) configurations in order to avoid contention when transmitting SL - PRS to other sidelink user devices. When different serving gNBs provide SL - PRS configurations to their corresponding user devices, since different gNBs do not adjust their SL - PRS configurations or perform contention resolution with each other, different user devices may receive overlapping SL - PRS configurations (e.g., in the time domain or frequency domain), thereby causing interference when the user devices transmit SL - PRS. Therefore, a method for avoiding overlapping SL - PRS configurations may be desirable.

Summary of the Invention

Means for Solving the Problems

[0003] Summary This document relates to methods, systems, apparatus, and devices for wireless communication. In some implementations, a method for wireless communication includes performing an interaction associated with at least one sidelink positioning reference signal (SL-PRS) configuration using a location management function (LMF) and at least one radio access network (RAN) node, and transmitting multiple non-overlapping SL-PRS configurations to multiple user devices based on the interaction using the LMF or at least one RAN node.

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

[0005] In several other implementations, a computer program product is disclosed. The computer program product may include a non-temporary computer-readable program medium in which computer code is stored, causing one or more processors to perform any of the methods described above when executed by one or more processors.

[0006] The above and other embodiments and their implementations are described in more detail in the drawings, specification and claims. The present invention provides, for example, the following items: (Item 1) A method for wireless communication, wherein the above method is Using a Location Management Function (LMF) and at least one Radio Access Network (RAN) node, perform an interaction associated with at least one Sidelink Positioning Reference Signal (SL-PRS) configuration, Using the above LMF or at least one of the above RAN nodes, multiple non-overlapping SL-PRS configurations are transmitted to multiple user devices based on the above interaction. Methods that include... (Item 2) The method according to item 1, wherein the at least one SL-PRS configuration includes at least one of the following: a priority index of an SL-PRS resource or set of SL-PRS resources, a muting pattern of the SL-PRS resource or set of SL-PRS resources, a slot or symbol offset of the SL-PRS resource or set of SL-PRS resources, a comb offset of the SL-PRS resource or set of SL-PRS resources, and a start physical resource block (PRB) or start subchannel of the SL-PRS resource or set of SL-PRS resources. (Item 3) The method involves determining whether a user device is configured to adopt mode 1 or mode 2 using the above-mentioned LMF or at least one RAN node, wherein in mode 1, the user device transmits SL-PRS according to the SL-PRS configuration transmitted by the LMF or at least one RAN node, and in mode 2, the user device transmits SL-PRS without the SL-PRS configuration transmitted by the LMF or at least one RAN node. Using the above LMF or at least one of the above RAN nodes, the indication of the above decision is transmitted to the above user device. The method described in item 1, further including the method described in item 1. (Item 4) Using the above LMF or at least one of the above RAN nodes, determine whether the user device is configured to perform sidelink positioning, wherein the performance of sidelink positioning includes at least one of performing sidelink positioning measurements, transmitting SL-PRS, or receiving SL-PRS. Using the above LMF or at least one of the above RAN nodes, the indication of the above decision is transmitted to the above user device. The method described in item 1, further including the method described in item 1. (Item 5) Performing the above interaction means To communicate a message from the LMF to the at least one RAN node requesting the at least one RAN node to transmit to the LMF the SL-PRS configuration of at least one user device. The method described in item 1, including the method described in item 1. (Item 6) Performing the above interaction means To communicate a message from at least one RAN node to the LMF, including at least one SL-PRS configuration of at least one user device. The method described in item 1, further including the method described in item 1. (Item 7) Using the above LMF, modify at least one of the above SL-PRS configurations, The LMF communicates a message containing the at least one SL-PRS configuration of the at least one user device to the at least one RAN node. The method described in item 6, further including the method described in item 6. (Item 8) Performing the above interaction means The LMF communicates a message containing at least one SL-PRS configuration for all of the above multiple user devices in the same positioning session to at least one RAN node. The method described in item 1, further including the method described in item 1. (Item 9) The method according to item 1, wherein transmitting the above-mentioned multiple non-overlapping SL-PRS configurations includes transmitting at least one of the above-mentioned multiple non-overlapping SL-PRS configurations to at least one user device via a Long-Term Evolution Positioning Protocol (LPP) message using the above-mentioned LMF. (Item 10) The method according to item 1, wherein transmitting the above-mentioned multiple non-overlapping SL-PRS configurations includes transmitting at least one of the above-mentioned multiple non-overlapping SL-PRS configurations to at least one user device via radio resource control (RRC) signaling using the above-mentioned at least one RAN node. (Item 11) Performing the above interaction means The LMF communicates a message to the at least one RAN node to trigger the at least one RAN node to deliver at least one of the multiple non-overlapping SL-PRS configurations to at least one user device. The method described in item 1, including the method described in item 1. (Item 12) Performing the above interaction means To communicate a message containing radio resources from the above LMF to at least one of the above RAN nodes. The method described in item 1, including the method described in item 1. (Item 13) The method according to item 12, wherein the at least one RAN node has one or more RAN nodes that have SL-PRS resource contention with one or more other RAN nodes. (Item 14) Performing the above interaction means Communicating a message from the LMF to at least one of the RAN nodes, 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 multiple user devices. The method described in item 1, including the method described in item 1. (Item 15) The above-mentioned at least one RAN node comprises a first RAN node and a second RAN node, and the above interaction is performed by: The SL-PRS configuration of the first RAN node is transmitted from the first RAN node to the second RAN node identified in the RAN node identification list. The method described in item 14, further including the method described in item 14. (Item 16) Performing the above interaction means Sending a request from the first RAN node to the second RAN node identified in the RAN node identification list to receive the SL-PRS configuration of the second RAN node. The method described in item 14, further including the method described in item 14. (Item 17) The above message includes the identification of the above user device, as described in any of items 5 through 8, 11, 12, or 14. (Item 18) To receive SL-PRS from a second user device using a first user device. The method described in item 1, further including the method described in item 1. (Item 19) The above SL-PRS is scheduled by sidelink control information (SCI) or downlink control information (DCI) as described in item 18. (Item 20) The method described in item 19, wherein the above SL-PRS is scheduled by the above SCI, and the above SCI is scheduled by Downlink Control Information (DCI), Long-Term Evolution Positioning Protocol (LPP) signaling, or Radio Resource Control (RRC) signaling. (Item 21) The method according to item 19, wherein the above SCI is scheduled by the above LPP signaling or the above RRC signaling, and the above LPP signaling or the above RRC signaling includes a time offset between the above transmission of the above LPP signaling or the above RRC signaling and the above transmission of the above SCI. (Item 22) The method according to item 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 the transmission of the DCI and the transmission of the SCI. (Item 23) A wireless communication device comprising a processor and memory, wherein the processor is configured to read code from the memory in order to carry out the method described in any of items 1 to 22. (Item 24) A computer program product comprising a computer-readable program medium that stores and contains code, wherein the code, when executed by a processor, causes the processor to perform any of the methods described in items 1 to 22. [Brief explanation of the drawing]

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

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

[0009] [Figure 3]Figure 3 shows a block diagram illustrating the side-link positioning structure for in-coverage scenarios of the wireless systems shown in Figures 1 and 2.

[0010] [Figure 4] Figure 4 shows a flowchart of an example of a method for wireless communication. [Modes for carrying out the invention]

[0011] Detailed explanation This specification describes various embodiments of systems, apparatus, devices, and methods for wireless communications related to sidelink positioning.

[0012] Figure 1 shows a diagram of an exemplary wireless communication system 100, which includes multiple communication nodes (or simply nodes) configured to communicate wirelessly with one another. Generally, a communication node includes at least one user device 102 and at least one wireless access node 104. The exemplary wireless communication system 100 in Figure 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 the wireless communication system 100 are possible, which may include any of various combinations of one or more user devices 102 and / or one or more wireless access nodes 104.

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

[0014] In addition, generally, the wireless access nodes described herein, such as the wireless access node 104, may include a single electronic device or apparatus, or a plurality of 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 wirelessly communicate with one or more user devices and / or one or more other wireless access nodes 104 over the network. For example, in various embodiments, the wireless access node 104 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 extended 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 a transceiver circuit 114 coupled to an antenna 116, which may include an antenna tower 118, in various ways, for wireless communication with a user device 102 or another wireless access node 104. The transceiver circuit 114 may also be coupled to one or more processors 120, which may be coupled to a memory 122 or other storage device. 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] Figure 2 shows a block diagram of an example configuration of a wireless access node 104. In the 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 Figure 2, may include multiple or n RAN nodes 204(1) to 204(n), where n is 2 or more. The LMF 202 and each RAN node 204 may be configured in hardware or a combination of hardware and software, such as having a processor 120, memory 122, transceiver circuit 114, antenna 116, and / or antenna tower 118, as shown in Figure 1 with respect to the wireless access node 104.

[0016] Furthermore, as shown in Figure 2, the LMF 202 and each RAN node 204 may be configured to communicate with each other (transmit and receive) signals or messages, and may be configured to communicate with one or more user devices 102 directly or indirectly through other components of the wireless access node 104. For example, the LMF 202 may communicate directly with the user device 102. In certain embodiments, the LMF 202 may communicate directly with the user device 102 according to the Long-Term Evolution (LTE) Positioning Protocol (LPP) (i.e., via LPP signaling). Also, the RAN node 204 may communicate directly with the user device 102. In certain embodiments, the RAN node 204 may communicate directly with the user device 102 at least via Radio Resource Control (RRC) signaling. Furthermore, the LMF 202 may communicate directly with each RAN node 204. In certain embodiments, the LMF202 may communicate directly with each RAN node 204 in accordance with the New Radio Positioning Protocol A (NRPPa) (i.e., via NRPPa signaling). Also, in at least some embodiments as shown in Figure 2, each RAN node 204 may include one or more subcomponents. For example, a RAN node 204 may include a gNB and / or at least one transmission / reception point (TRP). Further functionality of the LMF202 and RAN node 204 will be described in more detail below.

[0017] Furthermore, referring back to Figure 1, in various embodiments, two communication nodes within a 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 user devices 102, may be configured to communicate wirelessly with each other within or over a mobile network and / or wireless access network, according to one or more standards and / or specifications. Generally, standards and / or specifications may define rules or procedures that enable communication nodes to communicate wirelessly, and in various embodiments, these may include those for communication in the millimeter (mm) wave band and / or with multi-antenna schemes and beamforming capabilities. In addition to or instead of this, standards and / or specifications may, as non-limiting examples, define radio access technologies and / or cellular technologies such as fourth-generation (4G) Long-Term Evolution (LTE), fifth-generation (5G) New Radio (NR), or New Radio Unlicensed (NR-U).

[0018] Furthermore, in the wireless system 100, communication nodes are configured to wirelessly communicate signals to each other. Generally, communication in the wireless system 100 between two communication nodes can be either transmission or reception, or include both transmission and reception, and generally, both occur simultaneously, depending on the perspective of a particular node in the communication. For example, in a given communication between a first node and a second node, where the first node transmits a signal to the second node and the second node receives a signal from the first node, the first node may be called a source or transmission node or device, the second node may be called a destination or reception node or device, and the communication can be considered transmission for the first node and reception for the second node. Naturally, since communication nodes in the wireless system 100 can transmit and receive signals, a single communication node may be both a transmission / source node and a reception / destination node simultaneously, or may switch between being a source / transmission node and a destination / reception node.

[0019] Furthermore, certain signals may be characterized or defined as uplink (UL) signals, downlink (DL) signals, or sidelink (SL) signals. Uplink signals are signals transmitted from user device 102 to wireless access node 104. Downlink signals are signals transmitted from wireless access node 104 to user device 102. Sidelink signals are signals 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, the first / source user device 102 directly transmits the sidelink signal to the second / destination user device 102 without any transfer of the sidelink signal to the wireless access node 104.

[0020] Furthermore, signals communicated between communication nodes within 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., audio and / or image data), while control signals are signals that carry control information that configures communication nodes in a particular way to communicate with each other, or that control how communication nodes communicate data signals with each other. Also, specific signals may 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 over physical channels. Generally, a physical channel corresponds to a set of time-frequency resources used for transmitting signals. Different types of physical channels may be used to transmit different types of signals. For example, a physical data channel (or simply a data channel) is used to transmit data signals, and a physical control channel (or simply a control channel) is used to transmit control signals. Examples of physical data channel types include, but are not limited to, physical downlink shared channels (PDSCH) used to communicate downlink data signals, physical uplink shared channels (PUSCH) used to communicate uplink data signals, and physical sidelink shared channels (PSSCH) used to communicate sidelink data signals. Furthermore, examples of physical control channel types include, but are not limited to, physical downlink control channels (PDCCH) used to communicate downlink control signals, physical uplink control channels (PUCCH) used to communicate uplink control signals, and physical sidelink control channels (PSCCH) used to communicate sidelink control signals. For the sake of simplification as used herein, unless otherwise specified, a particular type of physical channel is also used to refer to the signals transmitted over that particular type of physical channel, and / or the transmissions over that particular type of transmission. For example, PDSCH refers to the physical downlink shared channel itself, the downlink data signals transmitted over the PDSCH, or the downlink data transmission. Therefore, when a communication node transmits or receives a PDSCH, it means that the communication node is transmitting or receiving signals over the PDSCH.

[0022] Furthermore, in the case of at least some specifications such as 5G NR, and / or at least some types of control signals, the control signals transmitted by a communication node may include control information that includes information necessary to enable the 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 uplink scheduling grants that inform a user device about the resources and transport formats to be used for proper reception, decoding, and demodulation of data signals received on a physical data channel during data transmission, and / or for uplink data transmission. In some embodiments, the control information includes downlink control information (DCI) transmitted downlink from the wireless access node 104 to the user device 102. In other embodiments, the control information includes uplink control information (UCI) transmitted uplink from the user device 102 to the wireless access node 104, or sidelink control information (SCI) transmitted sidelink from one user device 102(1) to another user device 102(2).

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

[0024] Furthermore, in at least some embodiments, sidelink positioning has two modes: 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 transmit positioning in the time and frequency domains) from the network 104 without sensing them before transmission. Mode 2 is for user devices 102 that need to sense sidelink control information (SCI) before the transmitted data to ensure that resources are not occupied by any other user devices 102. In in-coverage scenarios, user devices 102 may operate in Mode 1 or Mode 2, which in some embodiments may depend on explicit signaling of the gNB. User devices 102 may also be configured or operate as a target user device or an anchor user device. In some embodiments, Mode 1 and Mode 2 may also be referred to as Scheme 1 and Scheme 2, respectively.

[0025] Furthermore, in at least some implementations, the initial positioning performed by the user device 102 may use either a Mobile Terminal Location Request (MT-LR) structure or a Mobile Outgoing Location Request (MO-LR) structure. The MT-LR is an LMF-triggered location request to the user device 102 and the RAN node 204 at the very beginning of the initial positioning, and this location request may be initiated by an External Location Service (LCS) client. In addition, using the MO-LR, the user device 102 triggers a location request to the LMF 202 at the very beginning of the initial positioning to determine 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 a higher layer, and each positioning session may correspond to one service type, for example, one MT-LR or one MO-LR. In initial positioning, the communication nodes involved in one positioning session may include one LMF202, multiple RAN nodes 204, and one user device 102. In sidelink positioning, the communication nodes involved in one sidelink positioning session may include one LMF202, 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 a mode 1 user device 102, a mode 2 user device 102, and a user device 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] Furthermore, as used herein, the Sidelink Positioning Reference Signal (SL-PRS) configuration is a set of configured parameters for the SL-PRS that the user device 102 transmits sidelink signals / signaling. The SL-PRS configuration for 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 for the Mode 1 user device 102.Furthermore, an SL-PRS configuration may include one or more associated SL-PRS resource pools (an associated SL-PRS resource pool may be associated with one SL-PRS configuration, or one or more SL-PRS resource sets within an SL-PRS configuration, or one or more SL-PRS resources within an SL-PRS configuration; an SL-PRS resource pool may be a transmitting-side SL-PRS resource pool or a receiving-side SL-PRS resource pool), an SL-PRS identification (ID) (e.g., SL-PRS resource ID, SL-PRS resource set ID, or SL-PRS resource configuration ID), and time-domain resources of SL-PRS (e.g., periodicity of an SL-PRS resource / resource set, System Frame Number (SFN) 0 offset of an SL-PRS resource / resource set, slot or symbol offset of an SL-PRS resource / resource set, symbol count of an SL-PRS resource, and an SL-PRS resource / resource set). The SL-PRS may include at least one of the following: the number of repetitions (or the cyclic prefix of the SL-PRS resource / resource set), the frequency domain resources of the SL-PRS (e.g., the comb size and / or comb offset of the SL-PRS resource, the bandwidth of the SL-PRS resource / resource set, the starting physical resource block (PRB) of the SL-PRS resource / SL-PRS resource set, point A of the SL-PRS resource / resource set, the starting subchannel of the SL-PRS resource / SL-PRS resource set, and / or the number of subchannels of the SL-PRS resource / SL-PRS resource set), the spatial domain resources of the SL-PRS (e.g., the PRS sequence ID, the QCL information of the SL-PRS resource / resource set), the transmission power of each SL-PRS resource, an indication of whether the SL-PRS resource / resource set is periodic, semi-permanent, or aperiodic, or the priority index of the SL-PRS resource / SL-PRS resource set. Furthermore, the muting pattern may be used for each RAN node, or for several RAN nodes, or for each SL-PRS resource or set of SL-PRS resources.

[0028] Furthermore, the Ranging and Sidelink Positioning Protocol (RSPP), which may also be called the Sidelink Positioning Protocol (SLPP) in various embodiments, is similar to the LPP in 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 transmitted by one or more RSPP messages.

[0029] Furthermore, as used herein, SL-PRS resource contention means that SL-PRS resources transmitted from two Mode 1 user devices 102 have contention (or overlap) in the time domain and / or frequency domain. For example, SL-PRS resource contention can occur when two user devices 102 transmit their respective SL-PRS on the same symbol, the same PRB, or the same subchannel. In some circumstances, SL-PRS contention may cause interference between two Mode 1 user devices 102, particularly when the two Mode 1 user devices 102 are in close proximity 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 a user device that supports the positioning of the target user device 102, for example, by transmitting and / or receiving a reference signal for positioning via the sidelink (SL) interface, providing positioning-related information, etc.

[0031] Furthermore, in sidelink communication, there may be two ways to perform resource allocation with respect to a Mode 1 user device 102. The first method involves dynamic resource allocation, in which user device 102 receives the RRC configuration of the 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 method may be used to allocate dynamic sidelink resources for emergency services. The second method involves configured grant (CG) resource allocation, which may include Type 1 sidelinks (SL CG) and / or Type 2 SL CGs. In a Type 1 SL CG, user device 102 receives a CG configuration, which may include a resource pool ID, a CG configuration ID, CG periodicity, and CG resource allocation, and / or transmits sidelink information according to the indication in the RRC. In a Type 2 SL CG, the user device 102 receives a CG configuration which may include a CG index and CG periodicity, as well as DCI 3-0 scrambled by SL Configuration Scheduling (CS)-RNTI, to obtain time / resource area resources and CG triggers.

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

[0033] Initially, Uu positioning assumes, for example, DL positioning. The Uu positioning procedure may include the following: In a first operation, LMF202 may trigger one or more RAN nodes 204 to provide TRP information, including PRS configuration. In a second operation, one or more RAN nodes 204 may respond to LMF202 and provide TRP information along with PRS configuration. In a third operation, LMF202 transmits the TRP information along with PRS configuration as support data to user device 102. In a fourth operation, LMF202 may trigger user device 102 to perform positioning. In a fifth operation, user device 102 receives PRS from different TRPs (which may belong to different RAN nodes 204) and performs measurements. In a sixth operation, user device 102 reports the measurement results and / or positioning estimates to LMF202. Furthermore, in at least some embodiments, the second operation allows different RAN nodes 204 to independently provide their respective PRS configurations to the LMF 202. Each RAN node 204 does not need to know the PRS configurations of other RAN nodes 204. Each RAN node 204 may have non-overlapping PRS resources within a single RAN node by configuring one or more muting patterns.

[0034] Figure 3 shows an example of a side-link positioning structure in an in-coverage scenario.

[0035] Furthermore, in at least some embodiments, in the sidelink positioning mode 1 scenario, different sidelink user devices 102 may have different serving gNBs. One or more mode 1 user devices 102 may exist under the range or coverage of a single gNB, and these mode 1 user devices 102 may perform control signaling interaction (communicate control signals) 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, particularly for periodic SL-PRS transmissions. If different serving gNBs provide SL-PRS configurations to the corresponding user devices 102, it may be possible for user devices 102 to receive overlapping SL-PRS configurations (e.g., in the time domain and / or frequency domain), because the different gNBs may not coordinate their SL-PRS configurations with each other or perform conflict resolution. This can cause interference when user device 102 transmits each SL-PRS of user device 102 according to its SL-PRS configuration. On the other hand, if RAN node 204 adjusts each SL-PRS configuration of RAN node 204 or otherwise performs conflict resolution, overlapping SL-PRS configurations can be avoided.

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

[0037] In some embodiments of Method 400, at least one or each of several non-overlapping SL-PRS configurations includes at least one of the following: a priority index for an SL-PRS resource or SL-PRS resource set; a muting pattern for an SL-PRS resource or SL-PRS resource set; a slot or symbol offset for an SL-PRS resource or SL-PRS resource set; a comb offset for an SL-PRS resource or SL-PRS resource set; and a start physical resource block (PRB) or start subchannel for an SL-PRS resource or SL-PRS resource set.

[0038] In addition to or instead of the above, in some embodiments, the LMF202 and / or at least one RAN node 204 may determine, for example, whether a user device among a plurality of user devices 102 is configured to adopt mode 1 or mode 2. In mode 1, the user device 102 transmits SL-PRS according to an SL-PRS configuration transmitted by the LMF202 or at least one RAN node 204. In mode 2, the user device 102 transmits SL-PRS without an SL-PRS configuration transmitted by the LMF202 or at least one RAN node 204. Furthermore, the LMF202 or at least one RAN node 204 may transmit an indication of the decision to the user device.

[0039] In addition to or instead of this, the LMF202 and / or at least one RAN node 204 may determine, for example, whether one of several user devices 102 is configured to perform sidelink positioning, which includes at least one of performing sidelink positioning measurements, transmitting SL-PRS, or receiving SL-PRS. The LMF202 and / or at least one RAN node 204 may also transmit an indication of the decision to the user device 102.

[0040] In addition to or instead of this, the LMF202 and / or at least one RAN node 204 may perform an interaction by communicating a message from the LMF202 to at least one RAN node 204 requesting the at least one RAN node 204 to transmit at least one SL-PRS configuration of at least one user device 102 to the LMF202.

[0041] In addition to or instead of this, the LMF202 and at least one RAN node 204 may interact by communicating a message from at least one RAN node 204 to the LMF202, which includes at least one SL-PRS configuration of at least one user device. In some embodiments, the LMF202 may modify the at least one SL-PRS configuration, and the LMF202 may communicate a message to at least one RAN node 204, which includes at least one SL-PRS configuration of at least one user device.

[0042] In addition to or instead of this, the LMF202 and at least one RAN node 204 may interact by communicating a message from the LMF202 to at least one RAN node 204 containing all at least one SL-PRS configuration of multiple user devices 102 in the same positioning session.

[0043] In addition to or instead of this, the LMF202 or at least one RAN node 204 may transmit multiple non-overlapping SL-PRS configurations via Long-Term Evolution Positioning Protocol (LPP) messages, etc., by having the LMF202 transmit at least one of multiple non-overlapping SL-PRS configurations to at least one user device 102.

[0044] In addition to or instead of this, the LMF202 or at least one RAN node 204 may transmit multiple non-overlapping SL-PRS configurations by having at least one of the multiple non-overlapping SL-PRS configurations transmitted to at least one user device 102 via radio resource control (RRC) signaling or the like.

[0045] In addition to or instead of this, the LMF202 and at least one RAN node 204 may interact by communicating a message from the LMF202 to at least one RAN node 204 to trigger the at least one RAN node 204 to deliver at least one of several non-overlapping SL-PRS configurations to at least one user device 102.

[0046] In addition to or instead of this, the LMF202 and at least one RAN node 204 may interact by communicating a message containing radio resources from the LMF202 to 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 that have SL-PRS resource contention with one or more other RAN nodes 204.

[0047] In addition to or instead of this, the LMF202 and at least one RAN node 204 may perform interaction by communicating a message from the LMF202 to at least one RAN node 204 that includes a RAN node identification list identifying a set of one or more RAN nodes 204 required to transmit at least one SL-PRS configuration to at least one of a plurality of user devices 102. In at least some of these embodiments, the LMF202 and at least one RAN node 204 may perform interaction by transmitting the SL-PRS configuration of the first RAN node 204 to a second RAN node 204 identified in the RAN node identification list from the first RAN node 204. In addition to or instead of this, the LMF202 and at least one RAN node 204 may perform interaction by transmitting a request to receive the SL-PRS configuration of the second RAN node 204 identified in the RAN node identification list from the first RAN node 204.

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

[0049] In addition to or alternatively, a first user device 102 of a plurality of user devices 102 may receive SL-PRS from a second user device 102 of the plurality of user devices 102. In at least some of these embodiments, SL-PRS is scheduled by sidelink control information (SCI) or downlink control information (DCI). Also, in some embodiments in which SL-PRS is scheduled by SCI, SCI is scheduled by downlink control information (DCI), Long-Term Evolution Positioning Protocol (LPP) signaling, or Radio Resource Control (RRC) signaling. In addition to or alternatively, when SCI is scheduled by LPP signaling or RRC signaling, the LPP signaling or RRC signaling includes a time offset between the transmission of LPP signaling or RRC signaling and the transmission of SCI. In addition to or alternative to the above, in 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 the transmission of the DCI and the transmission of the SCI.

[0050] Various aspects or embodiments of Method 400, and / or further details of the operation of the functions of the components of the wireless system 100 are described here.

[0051] Furthermore, in at least some implementations, when the LMF202 coordinates the SL-PRS configuration of different RAN nodes 204, the LMF may know, determine, or decide the sidelink positioning method of the target user device 102 within coverage, sidelink positioning session information, and whether the target user device 102 and anchor user device 102 within a single sidelink positioning session adopt mode 1 or mode 2. In certain embodiments, the LMF202 may determine or decide the sidelink positioning method of the target user device 102 and communicate or notify the user device 102 via LPP, etc., and / or communicate or notify the gNB via NRPPa, etc. In addition, the LMF202 may know the sidelink positioning session information (e.g., which user devices 102 are in the same sidelink positioning session, and / or which RAN nodes 204 are in the same sidelink positioning session) and communicate or notify the user device 102 via LPP, and / or communicate or notify the RAN node 204 via NRPPa, etc. Furthermore, in at least some embodiments, the LMF202 may determine or decide whether an in-coverage sidelink user device 102 in a sidelink positioning session is configured to adopt mode 1, mode 2, or Uu-based positioning, and communicate or notify the user device 102 via LPP or the like, and / or communicate or notify the RAN node 204 via NRPPa or the like. In addition to or instead of this, the RAN node 204 may determine whether an in-coverage user device 102 (within the range of the RAN node) in a sidelink positioning session is configured to adopt mode 1, mode 2, or Uu-based positioning, and communicate or notify the user device 102 via RRC signaling or the like, and / or communicate or notify the LMF202 via NRPPa or the like.

[0052] Furthermore, for at least some implementations, the LMF202 may determine whether the target user device 102 employs only PC5 positioning (for example, if the target user device 102 transmits and / or receives only SL-PRS and performs SL-PRS measurements, but in an in-coverage scenario, can receive control signaling for sidelink communication from the wireless access node 104), or whether the target user device 102 employs a combination of PC5 positioning and Uu positioning (for example, if the target user device 102 performs sidelink positioning via the PC5 interface using RSPP, and the target user device 102 similarly receives a downlink positioning reference signal (DL-PRS) or transmits a sounding reference signal (SRS) and performs DL-PRS measurements according to the original LPP / RRC configuration).

[0053] Furthermore, with respect to at least some embodiments, the LMF may be adapted based on the implementation of the LMF202. In particular, after the LMF202 learns of the positioning requirements from the Location Service (LCS) client (MT-LR) or the target user device 102 (MO-LR) and learns that its sidelink positioning may be used or required for the target user device 102, the actions performed to obtain the configured SL-PRS configuration for the network 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 the first operation, the LMF202 may send a request message via NRPPa to trigger each RAN node 204 (involved in this sidelink positioning session) and provide each RAN node 204's respective SL-PRS configuration to the Mode 1 user devices 102 under the respective range of each RAN node 204. 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 a request message from the LMF 202 and configure an SL-PRS configuration for the Mode 1 user device 102 under its respective coverage. In addition, each RAN node 204 may consider real-time radio resources to ensure that the SL-PRS configurations of different Mode 1 user devices 102 under the same RAN node 204 do not overlap. Each NG-RAN node 204 may then provide a response message to the LMF 202, which includes the configured / assigned SL-PRS configuration 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 its respective SL-PRS configuration. Also, in some embodiments, the RAN node 204 may provide a corresponding update message or failure message for the LMF request in the first operation.

[0056] In the third operation, after the LMF202 has received or acquired all of the SL-PRS configurations of the RAN node 204, the LMF202 may resolve any interferences by or in accordance with the implementation of the LMF202. For example, the LMF202 may remove some of the overlapping SL-PRS resources of some RAN node 204. The LMF202 may then provide the mode 1 user device 102 with a non-overlapping SL-PRS configuration, for example, via LPP signaling. Alternatively, the LMF202 may provide the mode 1 user device 102 with an SL-PRS configuration that is the configuration of the serving RAN node 204 of the mode 1 user device 102.

[0057] In addition to or instead of this, in some embodiments, the LMF202 coordinates with the gNB. In such embodiments, after the LMF202 learns of the positioning requirements from the LCS client (MT-LR) or target user device 102 (MO-LR) and learns that its sidelink positioning is required for the target user device 102, the actions performed to obtain the configured SL-PRS configuration of the network for the Mode 1 user device 102 to transmit the SL-PRS may be as follows (not necessarily performed in the order described herein):

[0058] In the first operation, the LMF202 may send a request message via NRPPa or the like to trigger each RAN node 204 (involved in this sidelink positioning session) to provide each RAN node 204's respective SL-PRS configuration to the Mode 1 user devices 102 under the respective range of each RAN node 204. In some embodiments, the request message may include the UE identification of the Mode 1 user device 102. In addition to or instead of this, the request message may include a request in which the LMF202 asks the RAN node 204 to deliver the SL-PRS configuration to the corresponding Mode 1 user device 102.

[0059] In the second operation, each RAN node 204 receives a request message from the LMF 202 and may configure an SL-PRS configuration for the Mode 1 user devices 102 under the coverage (range) of the RAN node 204. 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. Then, each RAN node 204 provides the LMF 202 with a response message containing the configured / assigned SL-PRS configuration 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 its respective SL-PRS configuration. In addition, in some embodiments, the RAN node 204 may provide a corresponding update message or failure message to the LMF request in the first operation.

[0060] In a third operation, in some embodiments, after the LMF202 has acquired the entire SL-PRS configuration of the RAN node 204, the LMF202 may recommend some radio resources to some RAN node 204 that have SL-PRS resources that compete with other RAN nodes. The LMF may make recommendations to avoid SL-PRS resource conflicts between RAN node 204. Also, as used herein, “recommendation” may include sending a message. Therefore, when the LMF202 recommends radio resources to a RAN node 204, the LMF202 may make the recommendation by sending a message containing the radio resources to the RAN node 204 via NRPPa signaling or the like. Furthermore, the radio resources that the LMF202 recommends to one RAN node 204 will not overlap with the radio resources of other RAN node 204. In any of the various embodiments, the radio resource may include at least one of the following: the SFN0 offset of the SL-PRS resource / resource set, the slot or symbol offset of the SL-PRS resource / resource set, the periodicity of the SL-PRS resource / resource set, the number of symbols of the SL-PRS resource / resource set, the cyclic prefix of the SL-PRS resource / resource set, the number of repetitions of the SL-PRS resource / resource set, the bandwidth of the SL-PRS resource / resource set, the start PRB of the SL-PRS resource / resource set, point A of the SL-PRS resource / resource set, the comb size of the sidelink PRS resource / resource set, the comb offset of the sidelink PRS resource / resource set, the PRS sequence ID, the pseudo-collocation (QCL) information of the SL-PRS resource / resource set, the power of each SL-PRS resource, the priority index of each SL-PRS resource / resource set, or the muting pattern of each NG-RAN node. The NRPPa message may also include a user device identifier associated with the radio resource.

[0061] In another embodiment of the third operation, once LMF202 has obtained all SL-PRS configurations from RAN node 204, LMF202 may transmit the SL-PRS configurations to a set of RAN nodes (which may include fewer than all of RAN node 204) that LMF202 identifies as having SL-PRS resources that overlap with the SL-PRS resources of one or more other RAN node 204, or all of RAN node 204 that transmit the SL-PRS configurations to mode 1 user device 102.

[0062] In yet another embodiment of the third operation, the LMF202 may configure a muting pattern according to the SL-PRS configuration of the NG-RAN node. In any of the various embodiments, the muting pattern may be configured per user device 102 per RAN node 204, 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 its resources. In at least some embodiments, the muting pattern is a bitmap. In some embodiments of the bitmap, the value 1 indicates an SL-PRS resource ID or SL-PRS resource set ID that the RAN node 204 configures for one user device 102. The LMF202 may also transmit the muting pattern to the corresponding NG-RAN node 204. In addition to or instead of this, the muting pattern is part of the SL-PRS configuration.

[0063] In the fourth operation, RAN node 204 may modify the SL-PRS configuration in accordance with LMF204's recommendations. RAN node 204 may send a response message to LMF202 containing the modified SL-PRS configuration for each mode 1 user device 102.

[0064] In the fifth operation, the LMF202 may distribute the SL-PRS configuration of each RAN node 204 to each mode 1 user device 102. In some embodiments, the LMF202 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 operation described above. In other embodiments, the request message may be a separate message in 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 require the gNBs to coordinate with each other. In this case, the LMF 202 may need to know or determine the sidelink positioning method of the target user device 102 in coverage, sidelink positioning session information, and whether the target user device 102 and anchor user device 102 in a single sidelink positioning session are configured to adopt 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, etc., and / or communicate or notify the gNB via NRPPa, etc. In addition to or instead of this, the LMF 202 may know the sidelink positioning session information (e.g., which user devices 102 are in the same sidelink positioning session, and / or which RAN nodes 204 are in the same sidelink positioning session) and communicate or notify the user device 102 via LPP, etc., and / or communicate or notify the RAN nodes 204 via NRPPa, etc. The LMF202 determines whether the sidelink user device 102 should or is configured to adopt mode 1 or mode 2 in a sidelink positioning session, and may communicate or notify the user device 102 via LPP, and / or communicate or notify the NG-RAN node 204 via NRPPa or the like.

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

[0067] In the first operation, the LMF202 may send a request message via NRPPa or the like to trigger each RAN node 204 (involved in this sidelink positioning session) and provide SL-PRS configuration to the mode 1 user devices 102 under the respective range of each RAN node 204. In some embodiments, the request message may include identification of the mode 1 user device 102.

[0068] In the second operation, the LMF202 may send a request message to each RAN node 204. The request message may include a RAN node ID list containing one or more IDs of RAN nodes 204 for configuring the SL-PRS configuration for the mode 1 user device 102. The request message is a request to each RAN node 204 to coordinate the SL-PRS configuration with the RAN nodes 204 in the RAN node ID list, thereby avoiding 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 listed in the RAN node ID list. In addition, in some embodiments, an NG-RAN node 204 may transmit its own SL-PRS configuration to other RAN nodes via the Xn interface. In other embodiments, a RAN node 204 may send a request message to other RAN nodes 204 in the NG-RAN node list via the Xn interface to request them to provide their SL-PRS configuration.

[0070] In the fourth operation, it may be assumed that after the third operation, each RAN node 204 has the SL-PRS configuration of the other RAN node 204. Correspondingly, each RAN node 204 may modify its SL-PRS configuration so as not to overlap with the others. For example, if there are a total of two RAN nodes 204 requested by LMF 202 to coordinate their SL-PRS configurations, 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 determine whether an SL-PRS configuration conflict exists. If one exists, the second RAN node 204 may modify its own SL-PRS configuration. In another embodiment, the second RAN node 204 may send a non-overlapping SL-PRS to the first RAN node 204.

[0071] In the fifth operation, each RAN node 204 may provide LMF202 with a non-overlapping SL-PRS configuration. In the sixth operation, each RAN node 204 may provide the corresponding mode 1 user device 102 with a non-overlapping SL-PRS configuration. In the seventh operation, LMF202 may provide the corresponding mode 1 user device 102 with non-overlapping SL-PRS configurations from different RAN nodes 204.

[0072] Furthermore, in some embodiments, the LMF may request one RAN node to coordinate the SL-PRS configuration. In such embodiments, after the LMF202 learns the positioning requirements from the LCS client (MT-LR) or target user device 102 (MO-LR) and learns that sidelink positioning is required for the target user device 102, the operation to obtain the configured SL-PRS configuration for the network 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 the first operation, the LMF202 may send a request message to one of one or more RAN nodes. The request message may include an NG-RAN node ID list containing one or more NG-RAN node IDs necessary to configure the SL-PRS configuration for the mode 1 user device 102. The request message may request a RAN node 204 to coordinate the SL-PRS configuration with a RAN node 204 in the RAN node ID list in order to avoid SL-PRS resource contention between different RAN nodes 204. The requested RAN node 204 may be the serving RAN node 204 of the target user device 102 (e.g., the serving gNB).

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

[0075] In a third operation, after receiving the SL-PRS configuration of one RAN node, other RAN nodes 204 may configure non-overlapping SL-PRS configurations. For example, if LMF 202 requests coordination with a second RAN node 204 from the first 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 that of the first RAN node 204. In another embodiment, the second RAN node may send a non-overlapping SL-PRS to the first RAN node 204.

[0076] In the fourth operation, the RAN nodes 204 requested in the first operation may provide LMF202 with non-overlapping SL-PRS configurations for all RAN nodes 204. In the fifth operation, each RAN node 204 may provide non-overlapping SL-PRS configurations for its corresponding mode 1 user device 102. In the sixth operation, LMF202 may provide non-overlapping SL-PRS configurations for different RAN nodes 204 for their corresponding mode 1 user devices 102.

[0077] Furthermore, in at least some embodiments, the 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 this determination to the user device 102. In certain embodiments, for dynamic resource allocation, the serving RAN 204 node may provide the mode 1 user device 102 with a first subset of one or more SL-PRS configurations via RRC signaling or the like, or provide the mode 1 user device 102 with a second subset of one or more SL-PRS configurations via DCI. Also, in the case of type 1 SL PRS CG, the serving RAN node 204 or LMF 202 may transmit the whole or complete set of SL-PRS configurations to the mode 1 user device 102. In addition, in the case of 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 via RRC signaling or the like, and may provide a fourth subset of one or more SL-PRS configurations to the Mode 1 user device via DCI or the like. In other embodiments, in the case of Type 2 SL-PRS CG, the serving RAN node 204 may provide the Mode 1 user device 102 with the whole or complete set of SL-PRS configurations and CG configurations and trigger the user device 102 to transmit each of its SL-PRS via DCI or the like.

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

[0079] Furthermore, in at least some embodiments, the DCI may be a DCI format DCI xy, which may be the same as or different from existing DCI formats, where both x and y are integers. The DCI for Type 2 SL-PRS CG may be different from or independent of the DCI for dynamic resource allocation, or the two types of DCI may share the same DCI format but share different scrambles. The DCI may include at least one of the following: a time offset between the DCI and the SCI that schedules the SL-PRS, an SL-PRS resource ID / resource set ID indicated to the user device 102 for transmitting the SL-PRS, one or more triggered CG indices, a time-domain resource for the SL-PRS / SL-PRS resource set, a frequency-domain resource for the SL-PRS / SL-PRS resource set, or a spatial-domain resource for the SL-PRS / SL-PRS resource set. In addition, in any of the various embodiments, the RAN node 204 may communicate or notify 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] Furthermore, in embodiments in which the LMF202 distributes the SL-PRS configuration to each Mode 1 user device via LPP signaling or the like, if the SL-PRS resource is aperiodic, the user device 102 may send an SCI to trigger the SL-PRS transmission. In addition to or instead of this, if the SL-PRS resource is periodic, when the user device 102 receives the SL-PRS configuration LPP message, the user device 102 may initiate periodic SL-PRS transmission according to the SL-PRS configuration.

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

[0082] In addition to or alternative to this, in embodiments in which the RAN node 204 distributes the SL-PRS configuration to each Mode 1 user device 102 via RRC signaling or the like, if the SL-PRS resource is aperiodic, the user device 102 may receive a DCI that includes a trigger for an SCI scheduling the SL-PRS or a trigger for an aperiodic SL-PRS. In other embodiments in which the SL-PRS resource is aperiodic, the user device 102 may transmit an SCI to trigger the SL-PRS. In certain embodiments of these embodiments, the user device 102 may transmit an SCI without receiving an SCI or a DCI that triggers the SL-PRS. In addition to or alternative to this, in embodiments in which the SL-PRS resource is semi-persistent, the user device 102 may receive a Media Access Control Element (MAC-CE) that includes a trigger for an SCI scheduling the SL-PRS or a trigger for an aperiodic SL-PRS. Furthermore, in embodiments where the SL-PRS resource is periodic, the user device 102 may start transmitting SL-PRS according to the periodic SL-PRS configuration immediately after the user device 102 receives the RRC signaling. In addition, 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 which may be the same as or different from an existing DCI format, where both x and y are integers. If the DCI format is a reuse of an existing DCI format, it may include several new fields. The DCI, SCI, or MAC-CE may include at least one of the following: a resource pool associated with a 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 a first SL-PRS resource / resource set instance, a time offset between the SCI and a first SL-PRS resource / resource set instance, an SL-PRS resource ID / resource set ID indicated to the user device 102 for transmitting 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 may have units of milliseconds, slots, and / or symbols.

[0084] In addition, when the SL-PRS configuration is provided to the Mode 1 user device 102, a priority index for the SL-PRS resources / resource sets may also be provided. The priority index may be a 1-bit value that tells or informs the user device 102 whether or not the SL-PRS resources / resource sets can be transmitted by the user device 102. In some embodiments, the priority index may be configured by the LMF 202 after it has acquired 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 via LPP signaling or the like. In addition to or instead of this, the LMF 202 may transmit the muting patterns of all SL-PRS / SL-PRS resource sets within the RAN node 204 to each RAN node 204 via NRPPa signaling or the like. The NG-RAN node 204 may then transmit the SL-PRS configuration with the priority index to a specific user device 102 via RRC signaling or the like. In other embodiments, the LMF202 may communicate or notify each RAN node 204 of the muting patterns of all SL-PRS / SL-PRS resource sets within the RAN node 204 of a particular user device 102 via NRPPa or the like. The RAN node 204 may then communicate or transmit the SL-PRS configuration, including the priority index, to the user device via RRC signaling or the like. 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 it is intended that the subject matter covered or claimed is not limited to any exemplary embodiments described herein. A reasonably broad range of the subject matter claimed or covered is intended. In particular, for example, the subject matter may be embodied as a method, device, component, system, or non-temporary computer-readable medium for storing computer code. Accordingly, embodiments may take the form of, for example, hardware, software, firmware, storage medium, or any combination thereof. For example, the method embodiments described above may be implemented by a component, device, or system including memory and a processor by executing computer code stored in memory.

[0086] Throughout this specification and the claims, terms may have nuances implied or suggested in context beyond their expressly 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, the claimed subject matter is intended to encompass, in whole or in part, a combination of exemplary embodiments.

[0087] In general, technical terms can be understood, at least in part, from their usage in context. For example, terms such as “and,” “or,” or “and / or” as used herein may have various meanings, at least in part, depending on the context in which such terms are used. Typically, when “or” is used to relate a list such as A, B, or C, it is intended to mean A, B, and C, used here in an inclusive sense, and A, B, or C, used here in an exclusive sense. In addition, the terms “one or more” as used herein may be used, at least in part, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense, depending at least in part, depending on the context. Similarly, terms such as “a,” “an,” or “the” may be understood, at least in part, to convey either a singular or plural usage, depending at least in part, depending on the context. Furthermore, the term "based on" may be understood not necessarily as intended to convey an exclusive set of factors, but rather, depending at least partially on the context, may allow for the presence of additional factors that are not necessarily explicitly described.

[0088] Throughout this specification, references to features, advantages, or similar terms do not imply that all features and advantages that may be realized by the present solution should or will be included in any single implementation thereof. Rather, any terms referring to features and advantages should be understood to mean that certain features, advantages, or characteristics described in relation to the embodiments are included in at least one embodiment of the present solution. Accordingly, descriptions of features and advantages and similar terms throughout this specification may, but not necessarily, refer to the same embodiment.

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

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

[0091] A first aspect includes a method for wireless communication, which includes performing an interaction associated with at least one sidelink positioning reference signal (SL-PRS) configuration using a location management function (LMF) and at least one radio access network (RAN) node, and transmitting a plurality of non-overlapping SL-PRS configurations to a plurality of user devices based on the interaction using the LMF or at least one RAN node.

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

[0093] A third aspect includes either the first or second aspect, and further includes determining, using an LMF or at least one RAN node, whether a user device is configured to adopt mode 1 or mode 2, wherein in mode 1, the user device transmits SL-PRS according to an SL-PRS configuration transmitted by the LMF or at least one RAN node, and in mode 2, the user device transmits SL-PRS without an SL-PRS configuration transmitted by the LMF or at least one RAN node, and further includes transmitting an indication of the determination to the user device using the LMF or at least one RAN node.

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

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

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

[0097] The seventh aspect includes the sixth aspect, and further includes modifying at least one SL-PRS configuration using an LMF, and communicating a message from the LMF to at least one RAN node, which includes at least one SL-PRS configuration of at least one user device.

[0098] The eighth aspect includes any of the first to seventh aspects, and further includes performing an interaction which involves communicating a message from the LMF to at least one RAN node containing at least one SL-PRS configuration for all of the multiple user devices in the same positioning session.

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

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

[0101] An eleventh aspect includes any of the first to tenth aspects, further comprising the interaction being performed by communicating a message from the LMF to at least one RAN node to trigger the at least one RAN node to deliver at least one of a plurality of non-overlapping SL-PRS configurations to at least one user device.

[0102] The twelfth aspect includes any of the first to eleventh aspects, and further includes performing an interaction which involves communicating a message containing radio resources from the LMF to at least one RAN node.

[0103] A thirteenth aspect includes the twelfth aspect, further comprising at least one RAN node comprising one or more RAN nodes having SL-PRS resource competition with one or more other RAN nodes.

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

[0105] A 15th aspect includes the 14th aspect, further comprising at least one RAN node comprising a first RAN node and a second RAN node, and performing an interaction which includes transmitting the 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] The sixteenth aspect includes the fourteenth aspect, further comprising performing an interaction which involves 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] The 17th aspect includes any of the 5th to 8th, 11th, 12th, or 14th aspects, and further includes the fact that the message includes the identification of a user device.

[0108] The 18th aspect includes any of the first to 17th aspects, and further includes receiving SL-PRS from a second user device using a first user device.

[0109] The 19th aspect includes the 18th aspect, and further includes the fact that the SL-PRS is scheduled by sidelink control information (SCI) or downlink control information (DCI).

[0110] The 20th aspect includes the 19th aspect, and further includes that the SL-PRS is scheduled by 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] The 21st aspect includes the 19th aspect, further comprising the fact that the SCI is scheduled by LPP signaling or RRC signaling, and the LPP signaling or RRC signaling includes a time offset between the transmission of the LPP signaling or RRC signaling and the transmission of the SCI.

[0112] The 22nd aspect includes the 19th aspect, further comprising the fact that the SL-PRS is scheduled by SCI, the SCI is scheduled by Downlink Control Information (DCI), and the DCI includes a time offset between the transmission of DCI and the transmission of SCI.

[0113] A 23rd embodiment includes a wireless communication device comprising a processor and memory, wherein the processor is configured to read code from the memory in order to carry out any of the first to 22 embodiments.

[0114] The 24th aspect includes a computer program product comprising a computer-readable program medium storing and containing code, wherein the code causes the processor to implement any of the first to 22 aspects when the processor executes it.

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

Claims

1. A method for wireless communication, wherein the method is The first user device receives the Sidelink Positioning Reference Signal (SL-PRS) from the second user device. Includes, The SL-PRS is scheduled by the side link control information (SCI), The method wherein the SCI is triggered by downlink control information (DCI) or radio resource control (RRC) signaling, and the DCI includes a time offset between the DCI and the SCI that schedules the SL-PRS.

2. The aforementioned SCI is To transmit the SL-PRS, the SL-PRS resource identification (ID) shown to the second user device, or Time domain resource of the aforementioned SL-PRS resource The method according to claim 1, comprising at least one of the following.

3. The aforementioned DCI is The SL-PRS transmission resource pool associated with the scheduled SL-PRS resource, or Time offset between the DCI and the first SL-PRS resource instance The method according to claim 1, further comprising at least one of the following.

4. The second user device receives one or more SL-PRS configurations and configured grant (CG) configurations from a wireless access network (RAN) node. The method according to claim 1, further comprising:

5. The method according to claim 4, wherein at least one of the one or more SL-PRS configurations is received via radio resource control (RRC) signaling or the DCI.

6. The method according to claim 4, wherein the one or more SL-PRS configurations include a set of configured parameters for the SL-PRS for the second user device to transmit the SL-PRS.

7. The one or more SL-PRS configurations mentioned above are: One or more associated SL-PRS transmission resource pools of the one or more SL-PRS configurations, Identification (ID) of the SL-PRS resource, The periodicity of the SL-PRS resource, The slot or symbol offset of the SL-PRS resource, The number of symbols in the aforementioned SL-PRS resource, The number of repetitions of the SL-PRS resource, The comb size of the aforementioned SL-PRS resource, The comb offset of the SL-PRS resource, The initial physical resource block (PRB) of the SL-PRS resource, The number of subchannels of the SL-PRS resource, or Transmission power of the SL-PRS resource The method according to claim 6, further comprising at least one of the following.

8. The method according to claim 1, wherein the second user device includes a mode 1 user device.

9. The method according to claim 8, wherein the one or more SL-PRS configurations of the mode 1 user device include an SL-PRS transmission resource pool for the mode 1 user device.

10. A method for wireless communication, wherein the method is The second user device transmits the sidelink positioning reference signal (SL-PRS) to the first user device. Includes, The SL-PRS is scheduled by the side link control information (SCI), The method wherein the SCI is triggered by downlink control information (DCI) or radio resource control (RRC) signaling, and the DCI includes a time offset between the DCI and the SCI that schedules the SL-PRS.

11. The aforementioned SCI is To transmit the SL-PRS, the SL-PRS resource identification (ID) shown to the second user device, or Time domain resource of the aforementioned SL-PRS resource The method according to claim 10, comprising at least one of the following.

12. The aforementioned DCI is The SL-PRS transmission resource pool associated with the scheduled SL-PRS resource, or Time offset between the DCI and the first SL-PRS resource instance The method according to claim 10, further comprising at least one of the following.

13. The method according to claim 10, wherein the second user device transmits the SL-PRS according to a set of configured parameters of one or more SL-PRS configurations.

14. A method for wireless communication, wherein the method is A radio access network (RAN) node transmits to a second user device one or more sidelink positioning reference signal (SL-PRS) configurations and configured grant (CG) configurations, wherein at least one of the one or more SL-PRS configurations is transmitted via downlink control information (DCI) or radio resource control (RRC) signaling, the DCI or RRC triggers sidelink control information (SCI) that schedules the SL-PRS, and the DCI includes a time offset between the DCI and the SCI. Includes, The method wherein the one or more SL-PRS configurations include a set of configured parameters for the second user device for transmitting the SL-PRS to the first user device.

15. The one or more SL-PRS configurations mentioned above are: One or more associated SL-PRS transmission resource pools of the one or more SL-PRS configurations, Identification (ID) of the SL-PRS resource, The periodicity of the SL-PRS resource, The slot or symbol offset of the SL-PRS resource, The number of symbols in the aforementioned SL-PRS resource, The number of repetitions of the SL-PRS resource, The comb size of the aforementioned SL-PRS resource, The comb offset of the SL-PRS resource, The initial physical resource block (PRB) of the SL-PRS resource, The number of subchannels of the SL-PRS resource, or Transmission power of the SL-PRS resource The method according to claim 14, further comprising at least one of the following.

16. The method according to claim 14, wherein the second user device includes a mode 1 user device.

17. A wireless communication device comprising a processor and memory, wherein the processor is configured to read code from the memory in order to carry out the method according to claim 1.

18. A wireless communication device comprising a processor and memory, wherein the processor is configured to read code from the memory in order to carry out the method according to claim 10.

19. A wireless communication device comprising a processor and memory, wherein the processor is configured to read code from the memory in order to carry out the method according to claim 14.

Images