Lateral link positioning assistance

Abstract

Aspects of the present disclosure relate to sidelink positioning assistance. A device transmission, such as a user equipment (UE), includes, for example, a configuration message including an indication that one or more of a sidelink positioning reference signal (SL-PRS) or an SL positioning data message transmission is to be performed, and the configuration message includes one or more SL positioning parameters. The device receives a resource configuration message that includes a set of time-frequency resources in which the one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

Description

[0001] Related applications

[0002] This application claims priority to U.S. Non-Provisional Application No. 18 / 805,183, filed August 14, 2024, entitled "SIDELINK POSITIONING ASSISTANCE," the disclosure of which is incorporated herein by reference in its entirety. This application also claims priority to U.S. Provisional Application No. 63 / 532,984, filed August 16, 2018, entitled "SIDELINK POSITIONING ASSISTANCE," the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to wireless communication, and more specifically to the positioning of devices in wireless communication. Background Technology

[0004] A wireless communication system may include one or more network communication devices (e.g., base stations) that support wireless communication with one or more user communication devices (which may otherwise be referred to as user equipment (UE) or other suitable terms). The wireless communication system can support wireless communication with one or more user communication devices by utilizing its own resources (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system can support wireless communication across various radio access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies besides 5G (e.g., sixth-generation (6G)).

[0005] In wireless communication systems, determining the location of the UE can be critical, for example, for emergency services. However, current positioning technologies can be inaccurate and / or inefficient. Summary of the Invention

[0006] The article “a(a)” preceding an element is not limited and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein and contained in the claims, the use of “or” in a list of items (e.g., a list of items ending with phrases such as “at least one of…”, “one or more of…”, or “one or both of…”) indicates a list of inclusion, such that (for example) a list of at least one of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a set of closing conditions. For example, an example step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein and included in the claims, "group" may comprise one or more elements.

[0007] Some embodiments of the methods and apparatus described herein may further include transmitting from a UE to a network equipment (NE) a configuration message containing an indication to perform one or more of the Side Link Positioning Reference Signal (SL-PRS) or SL Positioning Data Message Transmission, the configuration message containing one or more SL positioning parameters; and receiving from a second device a resource configuration message containing a set of time-frequency resources in which the one or more of the SL-PRS or SL Positioning Data Message Transmission are to be performed.

[0008] In some embodiments of the methods and apparatus described herein, the UE receives a higher-layer trigger to perform one or more of the SL-PRS or SL positioning data message transmissions; the higher-layer trigger comprises one or more of the following: a Sidelink Positioning Protocol (SLPP) layer, a Vehicle-to-Everything (V2X) layer, a ProSe layer, a ranging layer, an SL positioning layer, or a Sidelink Positioning Application layer; the UE receives the higher-layer trigger from another UE via one or more of the following: higher-layer signaling comprising one or more of a Sidelink Positioning Protocol (SLPP) layer, a PC5 Radio Resource Control (RRC), or a PC5-S layer; or lower-layer signaling comprising a Level 1 Sidelink Control Information (SCI), a Level 1 Media Access Control (MAC) Control Element (CE), a Level 2 SCI, or a Level 2 MAC. One or more of the CEs; the configuration message includes one or more of the following: SL positioning quality of service (QoS) profile, at least one delivery QoS profile indicating SL positioning delivery QoS parameters, SL positioning session identifier, SL-PRS transmission characteristics, or one or more UEs discovered for SL positioning.

[0009] In some implementations of the methods and apparatus described herein, the UE receives a system information message containing one or more common SL positioning configurations, wherein the one or more common SL positioning configurations include at least one of the following: an SL positioning radio bearer configuration list, an SL-PRS priority, a positioning message priority, an SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information; the UE includes one or more of the following: a target UE, an anchor UE, a server UE, or a device configured to perform one or more of SL-PRS or SL positioning data message transmissions; the configuration message includes one or more of the following: an SL positioning transmission resource request; an SL positioning receiver unicast, multicast, or broadcast destination list. At least one of the following: SL positioning transmitter or receiver frequency list; SL positioning UE type; one or more SL positioning capabilities; SL positioning transmission resource discovery request; SL positioning destination identifier; SL positioning broadcast type; or coverage status of the discovered UE; the configuration message includes one or more of the SL-PRS dedicated shared pools for at least one of Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more SL-PRS and SL communication data dedicated resource pools for at least one of Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes a set of coverage status indications for the discovered UEs, wherein the coverage status indications include whether each discovered UE is within or outside the coverage area.

[0010] Some embodiments of the methods and apparatus described herein may further include transmitting from the UE to the NE a configuration message containing an indication to perform one or more of the SL-PRS or SL positioning data message transmissions, the configuration message containing one or more SL positioning parameters; and receiving from the NE a resource configuration message containing a set of time-frequency resources in which the one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

[0011] Some embodiments of the methods and apparatus described herein further include receiving a higher-level trigger to perform one or more of the SL-PRS or SL positioning data message transmissions; the higher-level trigger includes one or more of the following: a Sidelink Positioning Protocol (SLPP) layer, a Vehicle-to-Everything (V2X) layer, a ProSe layer, a ranging layer, an SL positioning layer, or a Sidelink Positioning Application layer; receiving the higher-level trigger from the UE via one or more of the following: higher-level signaling, which includes one or more of the Sidelink Positioning Protocol (SLPP), PC5 RRC, or PC5-S; or lower-level signaling, which includes one or more of the following: a Level 1 SCI, a Level 1 MAC CE, a Level 2 SCI, or a Level 2 MAC CE; the configuration message includes one or more of the following: an SL positioning QoS profile, at least one transport QoS profile indicating SL positioning transport QoS parameters, an SL positioning session identifier, SL-PRS transport characteristics, or one or more UEs discovered for SL positioning.

[0012] Some embodiments of the methods and apparatus described herein further include receiving a system information message containing one or more common SL positioning configurations, said one or more common SL positioning configurations including at least one of the following: an SL positioning radio bearer configuration list, SL-PRS priority, positioning message priority, an SL positioning frequency information list, SL-PRS / SL positioning validity configuration information including time-based (e.g., timer, validity period, etc.) and / or area-based validity (e.g., band information, physical cell identifier (PCI), system information block (SIB) area validity, cell identifier (ID)), SL positioning measurement common information, etc.; the UE includes one or more of the following: a target UE, an anchor UE, a server UE, or an apparatus configured to perform one or more of SL-PRS or SL positioning data message transmissions; the configuration message includes the following One or more of the following: SL positioning transmission resource request; at least one of the SL positioning receiver unicast, multicast, or broadcast destination lists; one or more of the SL positioning transmitter or receiver frequency lists; SL positioning UE type; one or more SL positioning capabilities; SL positioning transmission resource discovery request; SL positioning destination identifier; SL positioning broadcast type; or coverage status of the discovered UE; the configuration message includes one or more of the SL-PRS dedicated shared pools for at least one of Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more SL-PRS and SL communication data dedicated resource pools for at least one of Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes a set of discovered UEs, a set of coverage status indications for discovered UEs, and wherein the coverage status indications include whether each discovered UE is within or outside the coverage area.

[0013] Some embodiments of the methods and apparatus described herein may further include a processor transmitting from a first device to a second device a configuration message containing an instruction to perform one or more of the SL-PRS or SL positioning data message transmissions, the configuration message containing one or more SL positioning parameters; and receiving from the second device a resource configuration message containing a set of time-frequency resources in which the one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

[0014] In some embodiments of the methods and apparatus described herein, the processor receives a higher-layer trigger to perform one or more of the SL-PRS or SL positioning data message transmissions; the higher-layer trigger comprises one or more of the following: a Sidelink Positioning Protocol (SLPP) layer, a Vehicle-to-Everything (V2X) layer, a ProSe layer, a ranging layer, an SL positioning layer, or a Sidelink Positioning Application layer; at least one controller is configured to cause the processor to receive the higher-layer trigger from the UE via one or more of the following: higher-layer signaling comprising one or more of the Sidelink Positioning Protocol (SLPP), PC5 Radio Resource Control (RRC), or PC5-S; or lower-layer signaling comprising a first-level SCI, a first-level MACCE, a second-level SCI, or a second-level MAC. One or more of the CEs; the configuration message includes one or more of the following: SL positioning QoS profile, at least one transport QoS profile indicating SL positioning transport QoS parameters, SL positioning session identifier, SL-PRS transport characteristics, or one or more UEs discovered for SL positioning; receiving a system information message containing one or more common SL positioning configurations, the one or more common SL positioning configurations including at least one of the following: SL positioning radio bearer configuration list, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0015] In some embodiments of the methods and apparatus described herein, the first apparatus includes one or more of the following: a target UE, an anchor UE, a server UE, or an apparatus configured to perform one or more of SL-PRS or SL location data message transmissions; the configuration message includes one or more of the following: an SL location transmission resource request; at least one of a list of SL location receiver unicast, multicast, or broadcast destinations; one or more of a list of SL location transmitters or receivers frequencies; an SL location UE type; one or more SL location capabilities; an SL location transmission resource discovery request; an SL location destination identifier; an SL location broadcast type; or the coverage status of the discovered UE; the configuration message includes one or more of the SL-PRS dedicated shared pools for at least one of mode 1 and scheme 1 transmissions or mode 2 and scheme 2 transmissions; the configuration message includes one or more SL-PRS and SL communication data dedicated resource pools for at least one of mode 1 and scheme 1 transmissions or mode 2 and scheme 2 transmissions; the configuration message includes a set of coverage status indications for discovered UEs, wherein the coverage status indications include whether each discovered UE is within or outside the coverage area.

[0016] Some embodiments of the methods and apparatus described herein may further include receiving, at the NE, a configuration message from a second device containing an indication to perform one or more of the SL-PRS or SL positioning data message transmissions, the configuration message containing one or more SL positioning parameters; and transmitting a resource configuration message to the second device, the resource configuration message containing a set of time-frequency resources in which the one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

[0017] In some embodiments of the methods and apparatus described herein, the NE transmission includes system information messages of one or more common SL positioning configurations; the one or more common SL positioning configurations include at least one of the following: an SL positioning radio bearer configuration list, an SL-PRS priority, a positioning message priority, an SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0018] Some embodiments of the methods and apparatus described herein may further include receiving, at the NE, a configuration message from the UE containing an indication to perform one or more of the SL-PRS or SL positioning data message transmissions, the configuration message containing one or more SL positioning parameters; and transmitting a resource configuration message to the UE, the resource configuration message containing a set of time-frequency resources in which the one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

[0019] Some implementations of the methods and apparatus described herein may further include transmitting system information messages containing one or more common SL positioning configurations; the one or more common SL positioning configurations include at least one of the following: an SL positioning radio bearer configuration list, an SL-PRS priority, a positioning message priority, an SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0020] Some implementations of the methods and apparatus described herein may further include generating a semi-static configuration of one or more SL-PRS transport features that include one or more SL positioning or shared resource pools; and transmitting the semi-static configuration to the UE.

[0021] In some embodiments of the methods and apparatus described herein, the semi-static configuration is associated with one or more of a validity period or a valid area; the NE transmits the semi-static configuration as one or more of a request message or a non-request message; the NE transmits an indication to the UE of the unavailability of the SL positioning semi-static configuration; the SL-PRS transmission feature includes one or more of the following: an SL positioning dedicated resource pool identifier for one or more of the Mode 1 or Scheme 1 SL-PRS transmission; an SL positioning dedicated resource pool identifier for one or more of the Mode 1 or Scheme 1 SL positioning transmission; an SL positioning dedicated resource pool identifier for one or more of the Mode 2 or Scheme 2 SL-PRS transmission; and an SL positioning dedicated resource pool identifier for one or more of the Mode 2 or Scheme 2 SL positioning transmission. Pool identifier; SL positioning shared resource pool identifier for one or more of the SL-PRS positioning transmissions in Mode 1 or Scheme 1; SL positioning shared resource pool identifier for one or more of the SL positioning transmissions in Mode 1 or Scheme 1; SL positioning shared resource pool identifier for one or more of the SL-PRS positioning transmissions in Mode 2 or Scheme 2; SL positioning shared resource pool identifier for one or more of the SL positioning transmissions in Mode 2 or Scheme 2; or an SL-PRS resource index containing one or more of the following: SL-PRS bandwidth, SL-PRS comb size, SL-PRS periodicity, SL-PRS resource identifier, SL-PRS identifier, SL positioning session identifier, SL bandwidth portion (BWP) identifier, SL carrier identifier, or SL-PRS repetition count.

[0022] In some implementations of the methods and apparatus described herein, the NE transmits the semi-static configuration via one or more of UE-specific signaling or broadcast signaling; the NE activates the semi-static configuration via one or more of UE-specific signaling or broadcast signaling; and revokes the activation of the semi-static configuration via one or more of UE-specific signaling or broadcast signaling.

[0023] Some implementations of the methods and apparatus described herein may further include generating a semi-static configuration at the NE that includes one or more SL-PRS transport features comprising one or more SL positioning or shared resource pools; and transmitting the semi-static configuration to the UE.

[0024] In some embodiments of the methods and apparatus described herein, the semi-static configuration is associated with one or more of a validity period or a valid area; the semi-static configuration is transmitted as one or more of a request message or a non-request message; an indication of the unavailability of the SL positioning semi-static configuration is transmitted to the UE; the SL-PRS transmission feature includes one or more of the following: an SL positioning dedicated resource pool identifier for one or more of the mode 1 or scheme 1 SL-PRS transmission; an SL positioning dedicated resource pool identifier for one or more of the mode 1 or scheme 1 SL positioning transmission; an SL positioning dedicated resource pool identifier for one or more of the mode 2 or scheme 2 SL-PRS transmission; and an SL positioning dedicated resource pool identifier for one or more of the mode 2 or scheme 2 SL positioning transmission. One or more SL positioning dedicated resource pool identifiers; one or more SL positioning shared resource pool identifiers for Mode 1 or Scheme 1 SL-PRS positioning transmissions; one or more SL positioning shared resource pool identifiers for Mode 1 or Scheme 1 SL positioning transmissions; one or more SL positioning shared resource pool identifiers for Mode 2 or Scheme 2 SL-PRS positioning transmissions; one or more SL positioning shared resource pool identifiers for Mode 2 or Scheme 2 SL positioning transmissions; or an SL-PRS resource index containing one or more of the following: SL-PRS bandwidth, SL-PRS comb size, SL-PRS periodicity, SL-PRS resource identifier, SL-PRS identifier, SL positioning session identifier, SL BWP identifier, SL carrier identifier, or SL-PRS repetition count.

[0025] Some embodiments of the methods and apparatus described herein include transmitting the semi-static configuration via one or more of UE-specific signaling or broadcast signaling; or activating the semi-static configuration via one or more of UE-specific signaling or broadcast signaling; or deactivating the semi-static configuration via one or more of UE-specific signaling or broadcast signaling. Attached Figure Description

[0026] Figure 1 Illustrated examples of wireless communication systems according to various aspects of this disclosure.

[0027] Figure 2 The illustrations illustrate examples of systems for beam-based NR positioning according to various aspects of this disclosure.

[0028] Figure 3 Illustrated examples of absolute and relative positioning scenarios.

[0029] Figure 4 Illustrated examples of multi-cell round-trip time (RTT) procedures according to various aspects of this disclosure.

[0030] Figure 5 The illustration shows an example of a system used for relative range estimation using the gNB RTT positioning framework.

[0031] Figure 6 The illustration shows an example program used to enable the UE to obtain lateral link positioning and / or ranging location results.

[0032] Figure 7 The diagram illustrates a procedure used to enable a Location Services (LCS) client and / or AF to obtain ranging and / or lateral link location results for a group of n UEs.

[0033] Figure 8 Illustrated example procedures for ranging and / or SL positioning control (e.g., for UE-only operation).

[0034] Figure 9 The illustrations illustrate example procedures for a device to initiate a request to a serving gNB for SLPP message data exchange and / or SL-PRS transmission, according to various aspects of this disclosure.

[0035] Figure 10 Illustrated examples of programs that support side-link positioning assistance according to various aspects of this disclosure.

[0036] Figure 11 Illustrated examples of programs that support side-link positioning assistance according to various aspects of this disclosure.

[0037] Figure 12 Illustrated examples of programs that support side-link positioning assistance according to various aspects of this disclosure.

[0038] Figure 13 Illustrated examples of UEs based on various aspects of this disclosure.

[0039] Figure 14 Illustrated examples of processors according to various aspects of this disclosure.

[0040] Figure 15 Illustrated examples of NEs according to various aspects of this disclosure.

[0041] Figure 16 The diagram illustrates a flowchart of a method performed by a UE according to various aspects of this disclosure.

[0042] Figure 17 The diagram illustrates a flowchart of a method performed by an NE according to various aspects of this disclosure.

[0043] Figure 18 The diagram illustrates a flowchart of a method performed by an NE according to various aspects of this disclosure. Detailed Implementation

[0044] The SL positioning framework has been discussed in its support for differentiated target positioning parameters across various use cases. For example, SL positioning is designed for a wide range of use cases, such as V2X, public safety, IIoT, and commercial applications. One objective of SL positioning is to determine the absolute and relative location of the UE using SL positioning methods, such as SL RTT-class methods incorporating single-ended and dual-ended RTT, SL-AoA, and SL Time Difference of Arrival (TDOA) methods. SL positioning can utilize the new SL PRS transmitted via the PC5 interface and is supported in various coverage scenarios (e.g., within coverage, partial coverage, and outside coverage) as well as in standalone PC5 and combined PC5-Uu-based operational scenarios. Furthermore, a new protocol, denoted as SLPP, has been discussed for exchanging SL positioning-related information between UEs via the PC5 interface.

[0045] According to at least one Uu positioning framework, the delivery of positioning-aided data, including downlink positioning reference signal (DL-PRS) configuration, can be managed by a location server (e.g., LMF). The location server can initiate PRS configuration (e.g., using an NRPPa PRS configuration request message) to NG-RAN nodes including the serving and neighboring gNBs to configure PRS resources and receive response messages, such as NRPPa PRS configuration response messages from the applicable gNBs. In various scenarios, this PRS configuration may be semi-static and unlikely to change frequently unless a change is requested using an on-demand NRPPa PRS configuration procedure. Additionally, the location server can request PRS configuration based on its understanding of the received positioning QoS and the subsequently selected positioning method.

[0046] However, various problems may arise due to the distributed nature of SL positioning and its operation under different coverage scenarios and based on legacy SL resource allocation procedures. For example, some SL resource allocation procedures (e.g., those related to Mode 1 / Scheme 1 centralized resource allocation) may involve the gNB and the UE requesting resources for SL-PRS transmission. However, in such scenarios, it remains unclear how the gNB will receive positioning QoS and allocate resources for SL positioning based on factors such as the presence or absence of a location server. Furthermore, the mechanism for SL positioning auxiliary data delivery is therefore unresolved.

[0047] Therefore, this disclosure presents systems, apparatus, and methods for enhanced SL mechanisms and procedures to deliver SL location assistance data in different scenarios with and without location server involvement, and taking into account different types of coverage scenarios. For example, the embodiments discussed herein address scenarios without location server involvement and UE-only operation. In such scenarios, the serving gNB may need to receive information about location QoS and thereby allocate SL-PRS resources based on the number of UEs participating in a particular SL location session and the configured location technology. Furthermore, the disclosed embodiments are applicable to scenarios with location server involvement, and based on the requests and status information received by the location server, the location server can deliver SL-PRS assistance data (e.g., Mode 1 and Mode 2 SL-PRS resources) to the UE in a semi-static manner. Additionally, if the Mode 1 resources are dynamic, the location server can provide SL-PRS assistance data containing information such as validity period to the UE in a non-request manner. In a further embodiment, if the UE requests SL PRS assistance data from the location server, the UE can add an indication of a list of discovered UEs and their status (e.g., whether the discovered UE is within or outside coverage).

[0048] For example, the described technology details how it initiates the sharing of SL positioning information to NG-RAN nodes, including requesting SL-PRS and SL positioning resource configuration based on the desired carrier frequency for SL positioning transmission and reception, the positioning QoS of SL-PRS and / or the delivery QoS profile of SL positioning data messages. Furthermore, the described technology pre-configures semi-static SL positioning assistance data collected from multiple NG-RAN nodes by a location server (e.g., LMF). Additionally, the described technology provides indications of the discovered UEs in the SL positioning session and the associated coverage status of the discovered UEs.

[0049] Therefore, the described technique can adapt to various SL positioning scenarios and improve the accuracy of UE location determination. Various aspects of this disclosure are described in the context of wireless communication systems.

[0050] Figure 1The illustration depicts examples of a wireless communication system 100 according to various aspects of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A advanced network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, an 5G-A advanced network, or a 5G ultra-wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or include other suitable radio access technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G (e.g., 6G). In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0051] One or more NEs 102 may be geographically dispersed to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receiving signaling, transmitting signaling) via a Uu interface.

[0052] NE 102 can provide a geographic coverage area, and NE 102 can support service for one or more UEs 104 within said geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some embodiments, NE 102 can be mobile, such as a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NEs 102.

[0053] One or more UEs 104 may be geographically dispersed throughout the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, Internet of Everything (IoE) device, or Machine-Type Communication (MTC) device, and other instances thereof.

[0054] UE 104 may be able to support direct wireless communication with other UE 104s via a communication link. For example, UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations (such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments), the communication link may be referred to as a sidelink. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0055] NE 102 may support communication with CN 106 or with another NE 102, or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N6, or other network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate indirectly with each other (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components such as an access network entity, which may be an instance of an Access Node Controller (ANC). The ANC may communicate with one or more UE 104 via one or more other access network transport entities (which may be referred to as a radio head, smart radio head, or transmit-receive point (TRP)).

[0056] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management function (AMF)) and user plane entities that route packets to or interconnect to external networks (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access plane (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.), for one or more UEs 104 served by one or more NEs 102 associated with CN 106.

[0057] CN 106 may communicate with a packet data network via one or more backhaul links (e.g., via S1, N2, N6, or other network interfaces). The packet data network may contain an application server. In some implementations, one or more UEs 104 may communicate with the application server. UE 104 may establish a session (e.g., a Protocol Data Unit (PDU) session, etc.) with CN 106 via NE 102. CN 106 may use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0058] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 can support different resource structures. For example, NE 102 and UE 104 can support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 can support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 can support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 can support various frame structures based on one or more parameter sets (numerology).

[0059] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some embodiments, the first parameter set (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular or extended cyclic prefix. A fourth parameter set (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0060] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0061] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz can respectively utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe. Each time slot may contain a certain number (e.g., quantity) of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both regular and extended cyclic prefixes may depend on the parameter set. It should be understood that a reference to the first parameter set (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.

[0062] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, bands, channels, etc., based on frequency or wavelength. By way of example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency ranges specified as FR1 (410MHz–7.125GHz), FR2 (24.25GHz–52.6GHz), FR3 (7.125GHz–24.25GHz), FR4 (52.6GHz–114.25GHz), FR4a or FR4-1 (52.6GHz–71GHz), and FR5 (114.25GHz–300GHz). In some embodiments, NE 102 and UE 104 can perform wireless communication via one or more of the said operating frequency bands. In some embodiments, NE 102 and UE 104, as well as other equipment or devices, can use FR1 for cellular communication services (e.g., control information, data). In some implementations, NE 102 and UE 104, as well as other equipment or devices, may use FR2 for short-range, high-data-rate capabilities.

[0063] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with: a first parameter set (e.g., μ = 0) containing a 15 kHz subcarrier spacing; a second parameter set (e.g., μ = 1) containing a 30 kHz subcarrier spacing; and a third parameter set (e.g., μ = 2) containing a 60 kHz subcarrier spacing. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with: a third parameter set (e.g., μ = 2) containing a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ = 3) containing a 120 kHz subcarrier spacing.

[0064] According to the implementation scheme, one or more of NE 102 and UE 104 are operable to implement various aspects of the technology described with reference to this disclosure. For example, UE 104 transmits a configuration message to NE 102 containing an indication to perform one or more SL-PRS or SL positioning data message transmissions, and the configuration message contains one or more SL positioning parameters. NE 102 may transmit a resource configuration message to UE 104 containing a set of time-frequency resources in which one or more SL-PRS or SL positioning data message transmissions are performed. UE 104 may utilize the time-frequency resources to perform SL positioning, for example, for UE 104 itself and / or for different UEs.

[0065] Referring to the positioning requirements, Release 16 specifies for the first time NR positioning based on NR Uu signals and stand-alone (SA) architectures (e.g., beam-based transmission). Target use cases also include commercial and regulatory (emergency services) scenarios from Release 15. Performance requirements are as follows:

[0066] Positioning error indoor outdoor Horizontal positioning For 80% of UEs, <3m For 80% of UEs, <10m Vertical positioning For 80% of UEs, <3m For 80% of UEs, <3m

[0067] The current 3GPP Release 17 definition defines the positioning performance requirements for commercial and IIoT use cases as follows:

[0068]

[0069] For sidelink localization, version 18 defines various requirements covering a wide range of use cases, listed in the table below:

[0070]

[0071]

[0072] Supported UE positioning technologies are listed in Table 1 below:

[0073]

[0074]

[0075] The standalone positioning techniques indicated in the table above can currently be configured and implemented based on LMF requirements and UE capabilities. Uu (uplink and downlink) PRS transmission enables the UE to perform UE positioning-related measurements to calculate the UE's absolute position estimate, and is configured per Transmitter Receiver Point (TRP), where a TRP may contain one or more beams.

[0076] Figure 2 The illustration depicts an example of a beam-based NR positioning system 200 according to various aspects of this disclosure. System 200 illustrates a UE 104 and a network entity 102 (e.g., a gNB). The PRS can be transmitted by different base stations (serving and neighboring) using narrow beams on FR1 and FR2, as illustrated in example system 200, which is relatively different from LTE, where the PRS is transmitted across the entire cell. The PRS can be locally associated with a PRS resource identifier (ID) and a resource group ID of the base station (e.g., TRP). Similarly, UE positioning measurements, such as Reference Signal Time Difference (RSTD) and PRS Reference Signal Received Power (RSRP) measurements, are performed between beams (e.g., in different pairs of downlink (DL) PRS resources or DL ​​PRS resource groups), which differs from the measurements performed between different cells in LTE. Additionally, there are further uplink positioning methods to be developed to calculate the location of the target UE.

[0077] The table below shows the reference signal (RS) to measurement mapping for each of the supported RAT-dependent positioning technologies at the UE and gNB. RAT-dependent positioning technologies utilize the 3GPP RAT and core network entities to perform UE location estimation, which differs from RAT-independent positioning technologies, which rely on Global Navigation Satellite System (GNSS), Inertial Measurement Unit (IMU) sensors, Wireless Local Area Network (WLAN), and Bluetooth technologies to perform target device (UE) positioning.

[0078] Figure 3 Illustrated example scenario 300 of absolute and relative positioning scenarios. For example, scenario 300 is defined in the system architecture (Level 1) study reported in Technical Report (TR) 22.832 using three different coordinate systems (including absolute positioning (e.g., fixed coordinate system), relative positioning (e.g., variable and moving coordinate system), and relative positioning (e.g., variable coordinate system)).

[0079] Table 2: UE measurements for implementing RAT-dependent positioning technology.

[0080]

[0081] Table 3: gNB measurement for implementing RAT-dependent positioning technology.

[0082]

[0083] Versions 16 and 17 support various RAT-dependent positioning technologies, such as DL-TDoA, DL-AoD, multiple RTT, enhanced cell ID (E-CID) / NR E-CID, uplink (UL)-TDoA, and UL-AoA. The downlink time difference of arrival (DL-TDOA) positioning method utilizes the DL RSTD (and (optionally) DL PRSRSRP) of downlink signals received at the UE from multiple TPs. The UE uses auxiliary data received from the positioning server to measure the DL RSTD (and (optionally) DL PRSRSRP) of the received signals and uses the resulting measurements, along with other configuration information, to locate the UE relative to neighboring TPs.

[0084] The DL AoD positioning method utilizes the measured DL PRSRSRP of downlink signals received at the UE from multiple TPs. The UE uses auxiliary data received from the positioning server to measure the DL PRSRSRP of the received signals and uses the resulting measurements, along with other configuration information, to locate the UE relative to adjacent TPs. The multi-RTT positioning method utilizes the UE Rx-Tx measurements and DL PRSRSRP of downlink signals received from multiple TRPs, measured by the UE, and the measured gNB Rx-Tx measurements and UL probe reference signal (SRS)-RSRP of uplink signals transmitted from the UE at multiple TRPs.

[0085] Figure 4 The diagram illustrates an example 400 of a multi-cell RTT procedure related to carrier phase positioning configuration according to various aspects of this disclosure. The multi-RTT positioning technique utilizes UE Rx-Tx measurements and DL PRS RSRPs of downlink signals received from multiple TRPs, measured by the UE, and measured gNB Rx-Tx measurements and uplink SRS RSRPs (UL SRS-RSRPs) of uplink signals transmitted from the UE at multiple TRPs. The UE uses auxiliary data received from a positioning server (also referred to herein as a location server) to measure the UE Rx-Tx measurements (and (optionally) the DL PRS RSRPs of the received signals), and the TRPs use auxiliary data gNB Rx-Tx measurements (and (optionally) the ULSRS-RSRPs of the received signals) received from the positioning server. The measurements are used at the positioning server to determine the RTT, which is used to estimate the UE's location. In version 16, only UE-assisted and NG-RAN-assisted positioning techniques support multi-RTT, as noted in Table 1.

[0086] Figure 5 The illustration shows an example of a system 500 used for relative range estimation with a gNB RTT positioning framework, related to carrier phase positioning configuration.

[0087] For NR Enhanced Cell ID (E-CID) positioning technology, the UE's location is estimated using knowledge of the UE's serving ng-eNB, serving gNB, and serving cell, and this estimation is based on LTE signals. Information about the serving ng-eNB, serving gNB, and serving cell can be obtained through paging, registration, or other methods. NR E-CID positioning refers to techniques that improve UE location estimation using NR signals by using additional UE measurements and / or NR radio resources and other measurements. Although E-CID positioning may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE may not perform additional measurements solely for positioning purposes (e.g., the positioning procedure does not provide measurement configuration or measurement control messages, and the UE reports its available measurements rather than being required to perform additional measurement actions).

[0088] Uplink Time Difference of Arrival (UL-TDOA) positioning technology utilizes the UL Relative Time of Arrival (RTOA) (and (optionally) UL SRS-RSRP) of uplink signals transmitted from the UE at multiple receiving points (RPs). The RP uses auxiliary data received from the positioning server to measure the UL RTOA (and (optionally) UL SRS-RSRP) of the received signals, and uses the resulting measurements together with other configuration information to estimate the UE's location.

[0089] Uplink Angle of Arrival (UL-AoA) positioning technology utilizes the measured azimuth and zenith angles of the uplink signals transmitted from the UE at multiple RPs. The RP uses auxiliary data received from the positioning server (also referred to herein as the location server) to measure the azimuth angle AoA (A-AoA) and zenith angle AoA (Z-AoA) of the received signals, and uses these measurements together with other configuration information to estimate the UE's position.

[0090] Various RAT-based independent positioning technologies can also be used, such as network-assisted GNSS, atmospheric pressure sensor positioning, WLAN positioning, Bluetooth positioning, Land Beacon System (TBS) positioning, and motion sensor positioning. Network-assisted GNSS technology utilizes a UE equipped with a radio receiver capable of receiving GNSS signals. In the 3GPP specification, the term GNSS encompasses both global and regional / extended navigation satellite systems. Examples of global navigation satellite systems include the Global Positioning System (GPS), modernized GPS, Galileo, GLONASS, and BeiDou Navigation Satellite System (BDS). Regional navigation satellite systems include Quasi-Zenith Satellite Systems (QZSS), while many extended systems are classified under the general term Space-Based Extended Systems (SBAS) and provide regional extended services. Network-assisted GNSS technology can use different GNSS systems (e.g., GPS, Galileo, etc.) individually or in combination to determine the UE's location.

[0091] Atmospheric pressure sensor positioning technology uses barometric pressure sensors to determine the vertical component of the UE's position. The UE may optionally use auxiliary data to measure atmospheric pressure to calculate the vertical component of its position or send measurements to a positioning server for position calculation. This technology should be combined with other positioning methods to determine the UE's 3D position.

[0092] WLAN positioning technology uses WLAN measurements (access point (AP) identifiers and (optionally) other measurements) and a database to determine the UE's location. The UE optionally uses auxiliary data to measure signals received from the WLAN access point to send these measurements to the positioning server for location calculation. The UE's location is calculated using the measurement results and a reference database. Alternatively, the UE uses WLAN measurements and (optionally) WLAN AP auxiliary data provided by the positioning server to determine its location.

[0093] Bluetooth positioning technology uses Bluetooth measurements (beacon identifiers and (optionally) other measurements) to determine the UE's location. The UE measures the signals received from Bluetooth beacons. Using the measurement results and a reference database, the UE's location is calculated. The Bluetooth method can be combined with other positioning methods (e.g., WLAN) to improve the UE's positioning accuracy.

[0094] TBS positioning technology utilizes a terrestrial network of transmitters that broadcast signals used solely for positioning purposes. Examples of TBS positioning signal types include Urban Beacon System (MBS) signals and PRS. The UE may optionally use auxiliary data to measure the received TBS signals to calculate its location or send measurements to a positioning server for location calculation.

[0095] Motion sensor positioning technology utilizes various sensors (such as accelerometers, gyroscopes, magnetometers, etc.) to calculate the UE's displacement. The UE estimates the relative displacement based on a reference position and / or a reference time. The UE sends a report including the determined relative displacement, which can be used to determine the absolute position. This method can be used in conjunction with other positioning methods for hybrid positioning.

[0096] The different downlink measurements used for RAT-dependent positioning technology include DL PRS-RSRP, DL RSTD, and UERx-Tx time difference. The following measurement configurations can be used: 4 pairs of DL RSTD measurements can be performed per cell pair, and each measurement is performed across different pairs of DL PRS resources / resource groups using a single reference timing; 8 DL PRS RSRP measurements can be performed on different DL PRS resources within the same cell.

[0097] Table 4: Downlink measurements for downlink-based positioning technologies.

[0098]

[0099]

[0100]

[0101] Figure 6 This diagram illustrates an example procedure 600 used to enable a UE to obtain lateral link positioning and / or ranging location results. For example, procedure 600 may be used with the assistance of one or more other UEs in the serving public land mobile network (PLMN) of UE1. In procedure 600, ranging / SL positioning results may include absolute position, relative position, or distance and direction, for example, based on a service request. Furthermore, if the target UE decides to initiate an SL mobile-initiated location request (MO-LR) procedure, it may include one or more SL reference UEs and / or located UEs in the service request. See, for example, Technical Specification (TS) 23.586.

[0102] In procedure 600, UE1 is within coverage and has registered with a service PLMN. UE2 to n may or may not be within coverage, and if within coverage, may or may not be registered with the same service PLMN as UE1.

[0103] 1. The procedures and signaling specified in Clause 6.2 of TS23.586 may be used to preconfigure ranging / SL positioning service authorization and policy / parameter preconfiguration for UE1 to n (when within coverage area).

[0104] Note 1: If an instruction for UE-only operation is received, the ranging / side-link positioning control procedure defined in Clause 6.8 of TS23.586 can be executed.

[0105] 2. Based on the triggering of a service request (e.g., a request received from the application layer containing UE1 / ... / UEn), perform UE discovery for ranging / SL positioning in accordance with Clause 6.4 of TS23.586:

[0106] -If UE1 is the target UE, then UE1 discovers UE2 to n.

[0107] -If UE1 is a located UE, then the target UE (i.e., one of UE2 to n) discovers UE1 (as well as other located UEs in the set of UE2 to n).

[0108] 3. As defined in Clause 5.3 of TS23.586, establish secure multicast and / or unicast links between UE1 and n, so that UE1 can exchange ranging and sidelink positioning protocol (RSPP) messages with each of UE2 to n via the PC5-U reference point, and may enable UE2 to n to exchange RSPP with each other via PC5-U.

[0109] 4. UE1 and UE2 can (if needed) communicate via PC5 for ranging / SL positioning authorization and receive QoS parameters. Each UE verifies whether ranging / SL positioning is permitted based on any service authorization and policy / parameter provisioning received in step 1, including whether the ranging / SL positioning results can be transmitted to the LCS client or AF (if using this AF). The QoS requirements for ranging / SL positioning can also be provided based on the QoS requirements in the service request.

[0110] 5. UE1 can use the multicast and / or unicast links established in step 3 to obtain the side link positioning capability from UE2 to n.

[0111] Steps 4 and 5 can be performed to transmit information about UEs that are not served by the LMF.

[0112] 6. Based on the sidelink positioning capability of UE1 / ... / UEn, the target UE determines that it needs to perform SL-MO-LR. If UE1 is a located UE (i.e., when the target UE is one of UE2 / ... / UEn and does not have a NAS connection), then the target UE initiates an SL-MO-LR service request to UE1.

[0113] 7. If UE1 is in the Connection Management (CM) - Idle state, then UE1 initiates a UE-triggered service request in order to establish a signaling connection with UE1's service AMF.

[0114] 8. UE1 sends a Supplemental Service SL-MO-LR Request to the Serving AMF in a UL NAS delivery message. The SL-MO-LR request indicates to other UEs 2 to n (using the Application Layer ID and / or Common Public Subscription Identifier (GPSI)), any required auxiliary data, whether location calculation assistance is needed, and whether the location results should be transmitted to the LCS client or AF. The message should include the identifier of the LCS client or AF and may include the address of the Gateway Mobile Location Center (GMLC) through which the UE should access the LCS client or AF (via Network Open Function (NEF)). Additionally, a service type may be included, indicating which MO-LR service from the LCS client the UE is requesting. For location calculation assistance from the LMF, this includes the preferred type of sidelink positioning / ranging location results (e.g., absolute position, relative position, or distance and direction between UE pairs) and the required QoS. If UE1 is the located UE and one of UE2 / ... / UEn is the target UE (the target UE does not have a NAS connection), then the supplementary service SL-MO-LR request includes an indication that one of UE2 / ... / UEn (but not UE1) is the target UE.

[0115] 9. The serving AMF selects the LMF serving UE1 (e.g., an LMF that supports sidelink positioning / ranging) and sends an Nlmf_Location_DetermineLocation service operation to the LMF, which includes information from the SL-MO-LR request. The service operation contains an LCS-related identifier.

[0116] 10. The LMF sends a request to UE1 for UE1's capabilities to n.

[0117] Note 3: It is not assumed that UE2 / ... / UEn is served by the same LMF that serves UE1.

[0118] 11. UE1 returns its capabilities to LMF. If LMF requests this at step 10, then UE1 may additionally return the capabilities of the UE obtained at step 5.

[0119] 12. UE1 can send a request for specific auxiliary data to LMF.

[0120] 13. The LMF sends the requested auxiliary data to UE1, and UE1 forwards the received auxiliary data from the LMF to UE2 / ... / UEn. The auxiliary data can assist UE1 to obtain the side-link position measurement value at step 15, and / or can assist UE1 to calculate the side-link positioning / ranging position result at step 16.

[0121] Note 4: If UE1's SL-MO-LR request at step 8 contains a message with UE1's capability to n, then steps 10 and 11 can be omitted. If UE1's SL-MO-LR request at step 8 contains a message with a request for specific auxiliary data, then step 12 can be omitted.

[0122] 14. If the SL-MO-LR request at step 8 indicates a need for location calculation assistance and / or indicates that the lateral link positioning / ranging location results should be transmitted to the LCS client or AF, then the LMF sends a request for location information to UE1, and may also send a request for location information to UE2 / ... / UEn if UE2 / ... / UEn is served by the LMF. If the LMF determines that UE-based SL positioning should be applied, then the LMF includes an indication for UE-based SL positioning in the request. If an absolute location is requested at step 8, then the LMF may also provide a list of candidate positioned UEs. If a scheduled location time is received at step 14, then the LMF may include the scheduled location time.

[0123] 15. UE1 initiates a sidelink positioning / ranging procedure between UE1 and n, in which UE1 and n obtain sidelink position measurements, and UE2 and n transmit their sidelink position measurements to UE1 and / or LMF (depending on the requested assistance). If a scheduled position time is received at step 14, then sidelink positioning / ranging is performed at the scheduled position time.

[0124] 16. If the absolute location information of the target UE is required at step 8, and if the absolute location of the located UE is unavailable, then the target UE sends a request to the located UE to trigger the 5GC-MO-LR procedure so that the located UE can obtain its own absolute location. The request includes the QoS requirement received at step 8, which is used to derive the QoS of the located UE.

[0125] 17. If the LMF determines that UE-based calculations should be used, then at least one of UE1 / ... / UEn calculates a sidelink positioning / ranging result based on the sidelink position measurements obtained in step 15 and (possibly) using the auxiliary data received in step 13. The sidelink positioning / ranging result may include the absolute position, relative position or distance, and direction associated with UE1 to n.

[0126] 18. If UE1 receives a request for location information at step 14, then UE1 sends a response to LMF, which includes the sidelink location measurement value obtained at step 15, or the sidelink positioning / ranging location result obtained at step 17 if step 17 was performed, or the absolute position of the located UE obtained at step 16.

[0127] 19. If the absolute location information of the target UE is required at step 8 and the absolute location of the located UE is not received at step 18, the LMF may retrieve the location of the located UE locally or trigger a 5GC-Mobile Termination Location Request (MT-LR) procedure to the GMLC to obtain the absolute location of the located UE using the application layer ID or GPSI of the located UE. The LMF includes the QoS requirement received at step 8 in the request, which is used to derive the QoS of the located UE's location. If a scheduled location time is used, the LMF includes the scheduled location time in the request to the GMLC.

[0128] 20. The LMF calculates the sidelink positioning / ranging position results for UE1 to n based on the sidelink position measurement received at step 18 and the absolute position of the located UE obtained at step 19. Depending on the position request received at step 8, the sidelink positioning / ranging position results may include the absolute position, relative position or distance and direction related to UE1 to n.

[0129] 21. The LMF returns the Nlmf_Location_DetermineLocation service operation response to the AMF, which includes the sidelink location / ranging location result received in step 18 or calculated in step 20.

[0130] 22. If a lateral link location / ranging result is received at step 21, the AMF performs steps 7-12 of section 6.2 to send the lateral link location / ranging result to the GMLC and the AF or LCS client (if this operation was requested at step 8). The lateral link location / ranging result contains the identifiers of the corresponding UE1 to n received at step 8.

[0131] Note 5: Sending the location results and global identifier of UE1 to n to the AF or LCS client may require privacy verification from UE1 to n and / or from the HPLMN of UE1 to n.

[0132] 23. The LMF returns a Supplemental Service SL-MO-LR response to UE1 in the DL NAS delivery message, and if step 20 was performed, it includes any sidelink location / ranging position results calculated in step 20. If UE1 is a located UE, and the target UE is one of UE2 to n and does not have a NAS connection, then UE1 can transmit the sidelink location / ranging position results to the target UE.

[0133] Figure 7 The diagram illustrates procedure 700, which enables an LCS client or AF to obtain ranging and / or lateral mobility location results for a group of n UEs. For example (n≥2), these could be UE1, UE2, ..., UEn. In procedure 700, the GMLC identifies the UE among the n UEs to be designated as UE1 (e.g., the target UE in TS23.586) and one or more other UEs designated as UE2, UE3, ..., UEn (n≥2) (e.g., reference / located UEs in TS23.586). Based on the service request, the ranging / lateral mobility location results may include absolute, relative, or range and orientation associated with the UE. The SL-MT-LR procedure can be used to estimate the relative position or distance and / or orientation between UEs. Furthermore, example procedures for periodic and triggered SL-MT-LR are defined in section 6.20.4. In procedure 700, it can be assumed that at least one of the n UEs is within coverage and registered with the serving PLMN.

[0134] 1. The LCS client or AF (via NEF) sends an LCS service request to (H)GMLC for ranging / side-link location results for n UEs, each of which may be identified by GPSI or a pre-defined permanent identifier (SUPI). The request may include the required QoS, the required location results (e.g., absolute position, relative position, or distance and / or direction associated with the UE), and an SL reference UE (in the case of requesting relative position, distance, or direction). (H)GMLC or NEF authorizes the LCS client or AF to use the LCS service. If authorization fails, the remaining steps are skipped, and (H)GMLC or NEF responds to the LCS client or AF with a service authorization failure.

[0135] Additionally, each of the n UEs should include an application layer ID to enable UE discovery in step 12.

[0136] 2. (H) The GMLC invokes the Nudm_SDM_Get service operation on the Unified Data Management (UDM) of each of the n UEs to obtain the privacy settings of the UE identified by its GPSI or SUPI. The UDM returns the UE's privacy settings. (H) The GMLC checks the UE's LCS privacy profile.

[0137] 3. (H) The GMLC uses the GPSI or SUPI of each of the n UEs (for which GPSI or SUPI is available) to call the Nudm_UECM_Get service operation one at a time to the UDM of each UE. (H) The GMLC selects the UE that initiates ranging / SL positioning (e.g., regarded as UE1 in subsequent steps) and selects the corresponding service AMF.

[0138] Note: As defined in Clause 4.2.2.2.2 of TS23.502, the UDM knows the serving AMF address when the UE registers with the AMF. As defined in Clause 4.2.2.2.2 of TS23.502, the UDM knows the serving (V)GMLC address when the UE registers with the AMF.

[0139] 4. For non-roaming scenarios, skip this step. In roaming scenarios, the (H)GMLC may receive the (V)GMLC's address (along with the network address of the current serving AMF) from the UDM in step 3; otherwise, the (H)GMLC can use the Network Repository Function (NRF) service in the (H)PLMN to select an available (V)GMLC in the (V)PLMN based on the (V)PLMN identifier contained in the AMF address received in step 3. The (H)GMLC then sends a location request to the (V)GMLC by invoking the Ngmlc_Location_ProvideLocation service operation. If the (H)GMLC does not receive the (V)GMLC's address, or if the (V)GMLC's address is the same as the (H)GMLC's address, or if the two PLMN operators agree, the (H)GMLC sends a location service request message to the serving AMF. In this case, skip step 4. (H)-GMLC also provides the AF's LCS client type (if received in step 1), or the LCS client's LCS client type, as well as other attributes to be sent to the AMF in step 5.

[0140] 5. In roaming situations, the (V)GMLC first authorizes location requests from this (H)GMLC, PLMN, or this country. If not, an error response is returned. The (H)GMLC or (V)GMLC invokes the Namf_Location_ProvidePositioningInfo service operation to the AMF serving UE1 to request lateral link positioning / ranging results for n UEs. The service operation includes UE1's SUPI, UE's application layer ID, client type, and may include the required LCS QoS, the required location results (e.g., relative position or distance and direction associated with the UE), and other attributes received or determined in step 1.

[0141] 6. If UE1 is in CM-Idle state, then the AMF initiates a network-triggered service request procedure to establish a signaling connection with UE1. If the signaling connection establishment fails, steps 7-17 can be skipped.

[0142] 7-8. If the privacy check indicator indicates that action is required, then perform the same steps as in section 6.1.2, 7-8.

[0143] 9. The serving AMF selects the LMF serving UE1 (e.g., an LMF that supports ranging / sideline positioning) and sends an Nlmf_Location_DetermineLocation service operation to the LMF, which includes the information received in step 5, such as: the desired location result (e.g., the relative position or distance and direction between UE pairs), the SL reference UE (in the case of requesting relative position), and the UE's application layer ID (if received in step 5). The service operation includes an LCS-related identifier.

[0144] 10. The LMF uses the Namf_Communication_N1N2MessageTransfer service operation to send the SL-MT-LR request as a supplementary service message to the serving AMF, and the session ID parameter is set to the LCS-related identifier. The SL-MT-LR request may include the application layer IDs of other UEs 2 to n, the type of the desired location result (e.g., relative location or distance and / or direction), and the SL reference UE (in the case of requesting relative location).

[0145] 11. The Serving AMF uses DL NAS to deliver messages to forward the SL-MT-LR request and the routing identifier, which is equal to the LCS-related identifier, to UE1.

[0146] 12. UE1 attempts to discover other UE2 to n using the application layer IDs of other UE2 to n (if the procedure for discovery as defined in Section 6.4 of TS23.586 has not yet been used).

[0147] 13. UE1 obtains the sidelink localization capability of the discovered UE via SLPP (if it has not yet obtained it).

[0148] 14. UE1 returns a Supplemental Service SL-MT-LR response to the Serving AMF in the UL NAS delivery message, including the routing identifier received in step 11. The SL-MT-LR response indicates which of UE2 to n have been discovered and the sidelink location capabilities of the discovered UEs.

[0149] 15. The serving AMF forwards the SL-MT-LR response to the LMF indicated by the route identifier received in step 14, and includes an LCS-related identifier equal to the route identifier.

[0150] 16. Ranging / side traversal localization of UE1 and other discovered UEs is performed according to the SL-MO-LR method, the difference being that the ranging / side traversal localization measurement data or results can be returned to the LMF, and the LMF indicates an error to UE1 at step 13 or step 14: Reference source not found. The ranging / side traversal localization result will be calculated by the LMF (at step 19) or by UE1 (at step 17). For some undiscovered UEs among UE2 to n, the LMF interacts with the GMLC to initiate the 5GC-MT-LR procedure for UE2 to n to obtain their absolute positions and calculate the relative positions or distances and / or directions associated with the UEs.

[0151] 17-20. The LMF returns the sidelink location / ranging results to the LCS client or AF, as described in steps 13-15 and 24 of Clause 6.1.2. The results also include failure information for any undiscovered UEs.

[0152] Figure 8 The illustration shows an example program 800 for, for example, ranging and / or SL positioning control for UE-only operation. Both UE-only and network-based operations can be applied to ranging / side-link positioning control programs.

[0153] For example, UE-only operation can be applied in the following situations:

[0154] ● Neither the target UE nor the SL reference UE is served by NG-RAN.

[0155] ● Network-based operations are not supported by the 5GC network.

[0156] ● When network-based operations are not supported by the 5GC network, an indication of whether the UE is allowed to perform ranging / SL positioning using UE-only operations is included in the policy / parameters pre-configured for the UE and is pre-configured to the UE. The target UE takes this into account when initiating UE-only operations.

[0157] ● The SL-MO-LR request was rejected by the network.

[0158] In program 800:

[0159] 1. UE1 (i.e., the target UE) may receive ranging / SL positioning service requests from the following:

[0160] 1a.SL positioning client UE, during the procedure of opening ranging / SL positioning service via PC5, via PC5.

[0161] For absolute location, the service request includes the user information of the client UE and the target UE, as well as the required location QoS.

[0162] For relative location or ranging information, the service request includes user information of the SL positioning client UE, user information of the target UE, user information of the SL reference UE (UE2 / ... / UEn), and ranging / SL positioning QoS information.

[0163] 1b. RSPP application layer.

[0164] The service request includes the result type (i.e., absolute location, relative location, or ranging information) and the required QoS.

[0165] 2. UE1 discovers UE2 / ... / UEn (e.g., SL references UE / located UE).

[0166] 3. If UE1 / ... / UEn are not served by NG-RAN, or the serving network does not support ranging / SL positioning, then the application is limited to UE operation.

[0167] 4. UE1 and UE2 / ... / UEn perform capability exchange. Step 4 can be performed during steps 5 and 6 under the coordination of the SL positioning server UE.

[0168] 5. If UE1 does not support SL positioning server functionality, then UE1 discovers (if not already discovered in step 2) and selects the SL positioning server UE (either co-located with the SL reference UE / located UE or operated by a separate UE). If the SL positioning server UE co-located with the SL reference UE / located UE or operated by a separate UE, then UE1 discovers and selects the SL positioning server UE and requests the SL positioning server UE to participate in ranging / lateral walkway positioning.

[0169] 6. Transmit sidelink positioning assistance data between UE1 / ... / Uen and the SL positioning server UE.

[0170] 7. Perform SL-PRS measurements between UE1 and UE2 / ... / UEn and (optionally) also between UE2 / ... / UEn.

[0171] 8. Transmit the SL-PRS measurement data to the SL positioning server UE, or, if UE1 supports SL positioning server functionality, to UE1 to perform result calculations. Calculate absolute position, relative position, or ranging information at the UE based on the result type received in step 1.

[0172] 9. Send the ranging / SL positioning results to:

[0173] 9a.SL positioning client UE, ranging / SL positioning via PC5 as defined in Section 6.6.1.1.

[0174] During the service opening process, via PC5;

[0175] 9b.RSPP application layer.

[0176] Therefore, various aspects of this disclosure provide different positioning scenarios, including scenarios that do not involve location servers and implementations that do involve location servers. For example, in a scenario where the location server is not involved but the serving gNB is, the NG-RAN can schedule resources for SL-PRS transmission and SL positioning data transmission. Such implementations may involve cross-layer interaction between the UE's SLPP layer and RRC layer to share and exchange positioning-related information with the serving gNB. The UE may be triggered by its own higher layer (e.g., ranging, SL positioning layer, etc.) and / or receive an instruction from another UE's higher layer to initiate an SL positioning transmission process based on the serving gNB's scheduling of resources. In this implementation, this may be a direct interaction between the UE and the NG-RAN node (e.g., the serving gNB) without involving a location server (e.g., LMF) for provisioning SL positioning assistance data.

[0177] In the implementation scheme, the UE may transmit information related to the UE's location QoS or location QoS mapped to a standardized PC5 5G QoS Identifier (PQI) table as part of an SL location auxiliary data request to the serving gNB for resources requested by the UE for SL-PRS transmission. The location QoS may be based on a sidelink SL MO-LR location service request requested by the LCS client (e.g., an application), and may be based on a single UE request or multiple UE requests, for example, regarding the following metrics:

[0178] ●Absolute position

[0179] ○ Absolute horizontal position accuracy

[0180] ○ Absolute vertical position accuracy

[0181] ●Relative position

[0182] ○ Relative horizontal position accuracy

[0183] ○ Relative vertical position accuracy

[0184] ●Distance measurement

[0185] ○ Horizontal distance position accuracy

[0186] ○ Vertical distance position accuracy

[0187] ●Distance measurement direction

[0188] ○Azimuth direction accuracy

[0189] ○ Accuracy of reaching the zenith angle

[0190] ● Other mobility QoS parameters, such as:

[0191] ○ Absolute horizontal / vertical velocity

[0192] ○ Relative horizontal / vertical velocity

[0193] In the implementation, UE (e.g., UE group) location QoS is mapped to a standardized PQI table (as highlighted in Table 5 below, also known as the delivery QoS of SL location-related messages). Note:

[0194] ● The PQI value can be given by 'X', which can be an integer value.

[0195] ● The resource type is the non-guaranteed bit rate (GBR) shown in Table 5, to accommodate different broadcast types of SL-PRS and SLPP message transmissions, including capability exchange, auxiliary data exchange, location information exchange, and error and termination message exchange. In the implementation, the resource type can be configured as GBR or delayed critical service, since SL positioning can be considered a critical side link service.

[0196] ● The default priority can be 'Y', where Y can be an integer value to reflect the default priority of SL location-related messages.

[0197] In another implementation, the default priority can help determine the Layer 1 priority of SL location-related messages and / or SL-PRS.

[0198] ● The packet delay budget (PDB) can be given by 'Z' ms, where Z can be an integer value. In another implementation, the delay budget can be divided into a budget reflecting SLPP location-related messages (given by 'Z1' PDB) and SL-PRS transmissions (given by 'Z2' location / position delay budget (PoDB / LDB)).

[0199] ○ The PDB / PoDB / LDB can be used by lower layers to communicate the SL-PRS / SLPP location resource selection window for Mode 2 procedures. This SL-PRS / SLPP location resource selection window can indicate the waiting time limit for transmitting SLPP delivery block messages or SL-PRS.

[0200] The resource selection window is defined by [n+T1, n+T2], where n is the time slot in which the resource should be selected, T1 is defined as the processing time used to identify SL-PRS / SLPP message resource candidates and select these resources for transmission, and T2 is defined as T... 2min ≤T2≤PDB.

[0201] ○ This PDB / PoDB / LDB can be signaled from a higher layer of the UE itself as part of the QoS profile, or received from another UE / device via a first-level or second-level SCI in other implementations.

[0202] ● The packet error rate can be given by 'A' to indicate the reliability of SL location-related messages as given by block error rate (BLER), bit error rate (BER), packet error rate (PER), or any relevant metric.

[0203] ●SL positioning does not specify a default maximum data burst size, but in other implementations, the data burst size can be given by the number of bytes applicable to SL positioning-related messages.

[0204] ● The default averaging window can be given by 'B'ms, where B can be an integer value.

[0205] ●Note that multiple sets of {X,Y,Z,A,B} can be defined as parts of the normalized PQI.

[0206] In scenarios where standardized PQIs are unavailable or not provided, a default set of SL positioning PQIs applicable to {X,Y,Z,A,B} values ​​can be pre-configured within the UE. In another implementation, supported PQIs {X,Y,Z,A,B} can be broadcast to the UE for appropriate selection.

[0207] According to the implementation scheme, Mode 2 and / or Scheme 2 can support both autonomous dynamic and semi-persistent scheduling. In the dynamic scheme, the UE can sense and select resources based on SL-PRS transmission configuration and / or SL location data messages (e.g., transport blocks (TB)), while the semi-persistent scheme can select several consecutive resources based on the number of consecutive reselection counters applicable to SL-PRS and SL location data transmission. In the implementation scheme, a time period between consecutive SL-PRS and / or SL location data message (e.g., TB) transmissions of selected resources is defined, the period being given by the resource reservation interval (RRI) in the range {[1:99],100,200,…,1000}ms.

[0208] The UE can select resources when it generates a new SL positioning TB based on a higher-layer trigger and / or when it receives a higher-layer trigger to transmit an SL-PRS according to a defined SL-PRS configuration. The UE can perform sensing according to a sensing window, which is defined by [n-T0, nT].proc,0 The delimiter is defined as follows, where n is defined as above, T0 is defined in terms of the number of time slots (also depending on the subcarrier spacing (SCS)), and T proc,0 This is the time used to complete the sensing operation. The resource selection window can initially be defined by the UE as a function of T1, T2, and PDB / PoDB / LDB as described above. Furthermore, T2 can be defined as T... 2min The function can be based on a priority value for SL positioning TB or SL-PRS. This priority can be based on positioning QoS, delivery QoS, or a combination thereof.

[0209] Subsequently, when a selection window is defined, the UE can identify candidate resources within the selection window. A resource exclusion algorithm can then be applied to exclude candidate resources based on a defined policy, and the UE can then select a resource from the remaining candidate resources. In an implementation, resource selection may be subject to the condition that the percentage of remaining available resources in the selection window is higher than a configured threshold P% for SL-PRS transmission or SL location data message transmission. The configured threshold P% can be based on the priority value of the SL location TB or SL-PRS, wherein a mapping between a specific priority and P% can be determined and provided to the sensing UE.

[0210] In implementation schemes, the location QoS and location mapping PQI (also known as delivery QoS) described above may be transmitted as part of a QoS profile applicable to a specific LCS request to another entity (e.g., gNB and / or location server). This QoS profile may also be transmitted along with the SL QoS flow ID. In implementation schemes where the location server is not involved in scheduling SL-PRS transmissions, the UE may share one or more of the aforementioned QoS profiles with the serving gNB to assist in the gNB resource allocation process.

[0211] Table 5: Illustrative Examples of Standardized PQI and SL Positioning PQI

[0212]

[0213]

[0214] According to the implementation scheme and considering the aforementioned positioning QoS parameters, the UE can allocate SL-PRS resource requests based on the positioning method. Examples of such positioning methods are described above, such as SL-TDOA (class UL) for SL RTOA measurement, SL-TDOA (class DL) for SL RSTD measurement, single-ended or dual-ended SL-RTT for SL UE Rx-Tx time difference measurement, SL-AoA for azimuth-AoA and / or zenith-AoA measurement, etc. This allows the UE to request resources according to the specified positioning method. In the case of SL MO-LR without the participation of a location server, the decision may depend on the target UE / device and / or the anchor UE / device, and the UE / device may act as a server UE and / or be equipped with server UE capabilities. In the implementation scheme, the server UE may be another UE requesting SL-PRS resources for transmission.

[0215] In the implementation scheme, the requesting UE / device may request SL-PRS transmission characteristics for a given SL positioning resource pool, including but not limited to the following:

[0216] ●SL PRS Resource Index

[0217] ○SL-PRS Resource Index ID

[0218] ○SL-PRS bandwidth, in terms of: PRB, sub-channel, sub-channel size

[0219] ○SL-PRS comb tooth dimensions, in the following aspects:

[0220] ■SL-PRS comb tooth offset and associated SL-PRS comb tooth size (N)

[0221] ■SL-PRS start symbol and number of SL-PRS symbols (M)

[0222] ■The start time of SL-PRS can be relative to SFN0 or DFN0 and the total SL-PRS duration is given as X ms.

[0223] ○SL-PRS periodicity, in the following aspects:

[0224] ■ The time slots, where μ equals 0, 1, 2, and 3 respectively, based on SL-PRS subcarrier spacing of 15kHz, 30kHz, 60kHz, and 120kHz.

[0225] ■ Milliseconds (ms)

[0226] ■In another implementation, periodicity can be configured to be and The union of the values ​​is used to cover multiple periodic values.

[0227] ○The SL-PRS resource ID uniquely identifies the time-frequency resource within the time slot used for SL PRS transmission in the dedicated SL PRS resource pool, and in the case of a resource pool shared with SL data transmission, it uniquely identifies the time-frequency resource based on the SL PRS resource ID and SL PRS frequency domain allocation.

[0228] ○SL-PRS ID, which uniquely identifies an SL-PRS based on the SL-PRS resource ID and / or SL-PRS resource group ID, and can be used for SL-PRS transmitted across different time slots.

[0229] ○SL Location Session ID

[0230] ○SL-PRS Resource Group ID

[0231] ○SL BWP ID

[0232] ○SL carrier ID

[0233] ○SL-PRS repetition count

[0234] ○SL-PRS Silent Type

[0235] The example SL-PRS transport feature indicated above may be part of a resource index list that includes multiple SL-PRS transport features. In other embodiments, the SL-PRS transport feature may contain QCL information, such as a QCL source, for example, an SLSS, or another SL-PRS.

[0236] In the implementation, a UE initiating an SL positioning session or transmitting an SL-PRS to one or more peer UEs (e.g., via unicast, multicast, broadcast, etc.) may initiate an SL positioning request to the serving gNB. The SL positioning request may contain parameters related to SL positioning auxiliary data delivery, including SL-PRS configuration, which may include: dynamic granting; Type 1 configured granting, where the RRC / SLPP directly provides configured-side traverse granting for NR-side traverse positioning and / or communication; and / or Type 2 configured granting, where the RRC / SLPP defines the periodicity of configured-side traverse granting, and lower-layer signaling (e.g., DCI) can signal and activate or deactivate configured-side traverse granting, for example, releasing SL positioning resources. In the implementation, the SLPP may trigger a lower layer (e.g., RRC) to perform an NR-side traverse positioning and resource request to the serving gNB (e.g., an NG-RAN node).

[0237] Figure 9The illustration depicts an example procedure 900 for a device to initiate a request to a serving gNB for SLPP message data exchange and / or SL-PRS transmission, according to various aspects of this disclosure. For example, a UE capable of SL positioning can initiate procedures in several scenarios to indicate its interest in transmitting or receiving SL positioning information / operations. Examples of such scenarios include: upon successful connection establishment and / or connection restoration, upon changes in the transmission or reception of SL positioning information, upon changes in the QoS profile, upon receiving SL positioning capability information provided by a UE capability information side-link message / SLPP from an associated peer SL positioning UE, etc. Furthermore, a UE capable of SL positioning can initiate procedures to request the allocation of dedicated side-link DRB configuration and the transmission of time-frequency resources for SL positioning reference signals and SL positioning data transmission (e.g., SLPP).

[0238] In procedure 900, at step 902, UE 104 may receive a system information broadcast message from NE 102 (e.g., an NG-RAN node, such as a serving gNB) containing SIB 12 and / or a new SL positioning SIB containing initial SL positioning common configuration information applicable to one or more UEs / devices. In an implementation, UE 104 may not receive SIB 12 or the new SL positioning SIB, but may still proceed to step 904, in which SL UE information including information related to the initiation of the SL positioning procedure is transmitted. Note that SIB 12 is used as an example in Table 6 below; however, a new or equivalent SIB may be defined as carrying the same information for SL positioning.

[0239] System information broadcast messages may include the following information elements listed in Table 6:

[0240] Table 6: SIB 12 or a new SIB for common SL positioning information

[0241]

[0242]

[0243] ●Step 904: This RRC message (e.g., sidelink UE information or similar message) may share SL location-related information from UE 104 with NE 102 (e.g., with the serving gNB), which instructs UE 104:

[0244] ○ Is it currently configured to receive and / or transmit SL positioning messages and / or SL-PRS?

[0245] ○ Request the assignment or release of transmission resources used for SL positioning messages and / or SL-PRS;

[0246] ○ Report SL positioning QoS parameters and / or associated SL delivery QoS profiles related to SL positioning;

[0247] and / or

[0248] ○ Reports UE capability information for the sidelink location of associated peer UEs used for all broadcast types of communication.

[0249] The message content at step 904 may include the following information elements listed in Table 7. For illustrative purposes, the sidelink UE information RRC message is used as an example in the table below. However, a new RRC message may be defined, and / or another existing RRC message may be used to carry the same information containing SL positioning-related information:

[0250] Table 7: Sidelink UE Information Including SL Positioning Related Information

[0251]

[0252]

[0253]

[0254]

[0255] Step 906: The time-frequency resources provided to UE 104 from NE 102 to UE 104 via lower-layer signaling (e.g., DCI and / or RRC messages, such as RRCReconfiguration and / or separate / new SL location information messages) include resource pool information (e.g., a dedicated SL-PRS-only resource pool, a shared pool containing SL-PRS and SL data). This resource message can be a high-level resource configuration message, indicating the aggregate of resources used to perform SL-PRS and SL location data message transmission applicable to the cell. This may include:

[0256] ● One or more dedicated SL-PRS resource pools for Mode 1 / Scheme 1 transmission and / or Mode 2 / Scheme 2 transmission;

[0257] ● One or more SL-PRS and SL communication data sharing resource pools used for Mode 1 / Scheme 1 transmission and / or Mode 2 / Scheme 2 transmission;

[0258] ● One or more SL positioning anomaly resource pools are used to include abnormal transmissions in the following situations: the UE changes from the RRC_IDLE state to the RRC_CONNECTED state, experiences a Uu radio link failure, or performs a handover or exchange between transmission resource pools (e.g., from a dedicated resource pool to a shared resource pool) that may include only SL-PRS or SL-PRS and SL positioning data messages.

[0259] ●In the implementation scheme, Mode 1 / Scheme 1 may refer to a centralized resource allocation scheme, in which the gNB manages and schedules SL transmissions, while Mode 2 / Scheme 2 may refer to a distributed resource allocation scheme, in which each UE autonomously senses and performs resource selection for the resources to be transmitted.

[0260] In the implementation scheme, a UE can transmit sidelink UE information messages on behalf of multiple UEs participating in a single SL positioning session. This reduces the signaling overhead for each UE participating in the SL positioning session compared to transmitting SL UE information messages individually.

[0261] As mentioned above, the implementation also includes the delivery of SL positioning assistance data involving a location server. For example, in a location server-related scenario, the location server may deliver SL-PRS (SL positioning) assistance data to the UE in a semi-static manner via LPP / SLPP signaling (e.g., upon UE request and / or periodically after a period of time), such data including Mode 1 and / or Mode 2 dedicated (SL-PRS only) and / or shared / common (SL-PRS and SL data) resource pool information. This can be advantageous because the location server can have multiple SL positioning datasets from multiple NG-RAN nodes; however, this SL positioning assistance data delivery mechanism may not be sufficiently dynamic.

[0262] According to the implementation scheme, the serving gNB (e.g., the serving NG-RAN node) and / or neighboring gNBs may transmit a non-requested SL-PRS configuration response message containing the requested SL-PRS transport features to the location server. In additional or alternative implementation schemes, the location server may transmit an active request to receive SL-PRS transport features from the NG-RAN node.

[0263] Figure 10The illustration depicts an example of a procedure 1000 supporting side-link location assistance according to various aspects of this disclosure. For example, procedure 1000 provides pre-configuration of SL-PRS semi-static configuration information from a location server to a UE / device. In an embodiment, the SL-PRS semi-static configuration consists of SL-PRS transmission characteristics (e.g., unicast, multicast, or broadcast) that enable the UE to transmit SL-PRS to one or more other UEs. In an embodiment, the semi-static configuration can also be applied, for example, to the transmission of SL location data messages, such as SLPP messages, to one or more other UEs via unicast, multicast, and / or broadcast. For example, a UE can use the semi-static configuration based on configuration validity criteria (e.g., time-based criteria, area-based criteria, etc.) associated with one or more semi-static configurations. If a semi-static configuration is invalid, then the associated one or more semi-static configurations can also be considered invalid. In an embodiment, the UE / device can represent a target UE, an anchor UE, a server UE, a UE participating in SL-PRS transmission, etc.

[0264] In procedure 1000, at step 1004, location server 1002 (e.g., LMF) may request SL-PRS configuration information from NE 102 (e.g., NG-RAN node) containing SL-PRS transport characteristics from the applicable NG-RAN node, which may be provided periodically or whenever the transport characteristics are updated / published. The requested SL-PRS transport characteristics may include one or more of the following:

[0265] ● SL positioning dedicated resource pool ID used for SL-PRS or SL positioning transmission in Mode / Scheme 1 or Mode / Scheme 2;

[0266] ● SL positioning shared resource pool ID used for SL-PRS or SL positioning transmission in Mode / Scheme 1 or Mode / Scheme 2;

[0267] ● The SL-PRS resource index ID, including the following items, can also be shared with the location server from the NG-RAN node (in the implementation scheme, in the case of SL MO-LR or UE-based SL positioning, the NG-RAN node can receive this information from the UE):

[0268] ○SL-PRS bandwidth, in terms of: PRB, sub-channel, sub-channel size;

[0269] ○SL-PRS comb tooth dimensions, in the following aspects:

[0270] ■SL-PRS comb tooth offset and associated SL-PRS comb tooth size (N);

[0271] ■SL-PRS start symbol and number of SL-PRS symbols (M);

[0272] ■The start time of SL-PRS can be relative to SFN0 or DFN0 and the total duration of SL-PRS is given as Xms;

[0273] ○SL-PRS periodicity, in the following aspects:

[0274] ■ The time slots, where μ is equal to 0, 1, 2, and 3 respectively, based on the SL-PRS subcarrier spacing of 15kHz, 30kHz, 60kHz, and 120kHz;

[0275] ■ milliseconds (ms);

[0276] ■In the implementation plan, periodic grants are configured to be available. and The union of the values ​​is used to cover multiple periodic values.

[0277] ○SL-PRS Resource ID can identify time-frequency resources within a time slot used for SL PRS transmission in a dedicated SL PRS resource pool, and in scenarios involving resource pools shared with SL data transmission, time-frequency resources are identified based on SL PRS Resource ID and SL PRS frequency domain allocation.

[0278] ○SL-PRS ID, which uniquely identifies an SL-PRS based on its SL-PRS resource ID and / or SL-PRS resource group ID;

[0279] ○SL locates the session ID;

[0280] ○SL-PRS resource group ID;

[0281] ○SL BWP ID;

[0282] ○SL carrier ID;

[0283] ○SL-PRS repetition count; and / or

[0284] ○SL-PRS silent mode.

[0285] ● The validity period associated with the above-mentioned SL-PRS transmission characteristics is based on a start timer and a duration or expiration timer. In an implementation, the validity of a semi-static SL PRS configuration may be associated with area validity; for example, the SL-PRS configuration may be valid only within a specific area having a band ID, cell, TRP, PCI, CGI, TAI, RAN notification area, and / or a combination thereof.

[0286] ● Instance signaling can include NRPPa signaling and associated message passing.

[0287] At step 1006, NE 102 may respond with one or more of the SL-PRS configuration information containing SL-PRS transport characteristics. Instance signaling may include NRPPa signaling and associated message passing. At step 1008, if, for example, one or more of the SL-PRS configuration information containing SL-PRS transport characteristics is unavailable, NE 102 may accordingly indicate this unavailability. Instance signaling may include NRPPa signaling and associated message passing.

[0288] At step 1010, and at least in part based on the type of positioning performed (e.g., SL MO-LR and / or UE-based SL positioning), UE 104 may request semi-static SL positioning assistance data. The request for semi-static SL positioning assistance data configuration may include SL-PRS transport characteristics and / or SL positioning data message resources. In an implementation, the semi-static SL positioning assistance data may override pre-configured SL positioning assistance data. Furthermore, UE 104 may first utilize the semi-static SL positioning assistance data configuration before previously stored and / or pre-configured semi-static SL positioning assistance data configuration. Instance signaling may include SLPP / LPP signaling and associated message passing.

[0289] At step 1012, location server 1002 may transmit SL positioning assistance data containing SL-PRS semi-static transmission characteristics to UE 104 via the positioning SIB using UE-specific signaling (e.g., LPP / SLPP or broadcast signaling). Instance signaling may include SLPP / LPP signaling and associated message passing. At step 1014, location server 1002 may transmit the unavailability of the requested SL-PRS semi-static transmission characteristics to UE 104 using UE-specific signaling (e.g., LPP / SLPP). In an implementation, steps 1006, 1008, 1012, and / or 1014 may be transmitted unsolicited. Instance signaling may include SLPP / LPP signaling and associated message passing.

[0290] Figure 11The illustration depicts an example of a procedure 1100 supporting sidelink positioning assistance according to various aspects of this disclosure. For example, procedure 1100 provides a discovered UE and associated coverage status for SL positioning without the involvement of a location server. At step 1102, NE 102 (e.g., an NG-RAN node, such as a serving gNB) may transmit SIB 12 and / or a new SL positioning SIB = V2X SL common configuration containing a common SL positioning configuration to UE 104. At step 1104, UE 104 may transmit a sidelink UE information message containing the discovered UE and associated coverage status to NE 102. At step 1106, NE 102 may transmit a resource message containing SL positioning time-frequency information (e.g., SL positioning resource pool configuration) to UE 104.

[0291] In procedure 1100, for example in a scenario involving a location server, a request for SL location assistance data may convey information about the discovered UE and its associated coverage status. The steps may be similar to procedure 1000 (Error! Reference source not found), except that in at least some embodiments, a request for SL location assistance data may include the following information:

[0292] ●The list of discovered UEs consists of the following items:

[0293] ○UE type: Anchor UE (with or without known location information), Server UE, Client UE, Assistant UE;

[0294] ○UE ID, such as 5G TMSI (when within coverage area), Layer 2 source ID, Layer 2 destination ID, group

[0295] Group ID and associated member IDs;

[0296] ○ Coverage status indication, which uses flags or selections that include coverage area or outside coverage area.

[0297] variable;

[0298] ●SL locates QoS information.

[0299] Figure 12The illustration depicts an example of a procedure 1200 supporting side-link location assistance according to various aspects of this disclosure. For example, procedure 1200 provides the discovered UE and associated coverage status for SL location in the presence of a location server. At step 1202, location server 1002 (e.g., LMF) may transmit a request for SL-PRS transmission features to NE 102 (e.g., NG-RAN node). At step 1204, NE 102 may transmit the SL-PRS transmission features to location server 1002. At step 1206, and optionally, NE 102 may transmit an indication of the unavailability of SL-PRS configuration information to location server 1002.

[0300] At 1208, UE 104 may optionally transmit a request to location server 1002 for SL location assistance data containing the discovered UE and associated coverage status. At 1210, location server 1002 may transmit the SL location assistance data to UE 104, and at 1212, location server 1002 may transmit an indication to UE 104 of the unavailability of the SL location assistance data.

[0301] According to the implementation scheme, in procedures 1100 and 1200, UE 104 may have already received the coverage status of the discovered UE through various signaling mechanisms, including lower-layer signaling (e.g., first or second level SCI, SL MAC CE) and / or higher-layer signaling (e.g., PC5 RRC, SLPP, PC5-S, etc.). Requests for coverage status can also be based on request-based or non-request-based messages.

[0302] Figure 13 The illustration depicts an example of a UE 1300 according to various aspects of this disclosure. The UE 1300 may include a processor 1302, a memory 1304, a controller 1306, and a transceiver 1308. The processor 1302, memory 1304, controller 1306, or transceiver 1308, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground).

[0303] Processor 1302, memory 1304, controller 1306, or transceiver 1308, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic means configured to or otherwise support components for performing the functions described in this disclosure, or any combination thereof.

[0304] Processor 1302 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 1302 may be configured to operate memory 1304. In some other embodiments, memory 1304 may be integrated into processor 1302. Processor 1302 may be configured to execute computer-readable instructions stored in memory 1304 to cause UE 1300 to perform various functions of this disclosure.

[0305] Memory 1304 may include volatile or non-volatile memory. Memory 1304 may store computer-readable, computer-executable code containing instructions that, when executed by processor 1302, cause UE 1300 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 1304 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available medium accessible by a general-purpose or special-purpose computer.

[0306] In some implementations, processor 1302 and memory 1304 coupled to processor 1302 may be configured to cause UE 1300 to perform one or more of the functions described herein (e.g., instructions stored in memory 1304 executed by processor 1302). For example, processor 1302 may support wireless communication at UE 1300 according to the examples disclosed herein. UE 1300 may be configured or operable to support components for performing: transmitting from the UE to a second device a configuration message containing an indication to perform one or more of Side Link Positioning Reference Signal (SL-PRS) or SL Positioning Data Message Transmission, the configuration message containing one or more SL positioning parameters; and receiving from the second device a resource configuration message containing a set of time-frequency resources in which one or more of the SL-PRS or SL Positioning Data Message Transmission are performed.

[0307] Additionally, UE 1300 can be configured to support any or a combination of the following: receiving a higher-layer trigger to perform one or more of the SL-PRS or SL positioning data message transmission; the higher-layer trigger comprising one or more of the following: Sidelink Positioning Protocol (SLPP) layer, Vehicle-to-Everything (V2X) layer, ProSe layer, ranging layer, SL positioning layer, or Sidelink Positioning Application layer; receiving the higher-layer trigger from the UE via one or more of the following: higher-layer signaling comprising one or more of Sidelink Positioning Protocol (SLPP), PC5 Radio Resource Control (RRC), or PC5-S; or lower-layer signaling comprising Level 1 Sidelink Control Information (SCI), Level 1 Media Access Control (MAC) Control Element (CE), Level 2 SCI, or Level 2 MAC. One or more of the CEs; the configuration message includes one or more of the following: SL positioning QoS profile, at least one delivery QoS profile indicating SL positioning delivery QoS parameters, SL positioning session identifier, SL-PRS transmission characteristics, or one or more UEs discovered for SL positioning.

[0308] Additionally, UE 1300 may be configured to support any or a combination of the following: receiving a system information message containing one or more common SL positioning configurations, wherein the one or more common SL positioning configurations include at least one of the following: an SL positioning radio bearer configuration list, an SL-PRS priority, a positioning message priority, an SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information; wherein the UE includes one or more of the following: a target UE, an anchor UE, a server UE, or a device configured to perform one or more of SL-PRS or SL positioning data message transmissions; and wherein the configuration message includes one or more of the following: an SL positioning transmission resource request; and a list of SL positioning receiver unicast, multicast, or broadcast destinations. The configuration message includes at least one of the following: one or more of the SL positioning transmitter or receiver frequency list; SL positioning UE type; one or more SL positioning capabilities; SL positioning transmission resource discovery request; SL positioning destination identifier; SL positioning broadcast type; or coverage status of the discovered UE; the configuration message includes one or more of the SL-PRS dedicated shared pools for at least one of mode 1 and scheme 1 transmission or mode 2 and scheme 2 transmission; the configuration message includes one or more SL-PRS and SL communication data dedicated resource pools for at least one of mode 1 and scheme 1 transmission or mode 2 and scheme 2 transmission; the configuration message includes a set of coverage status indications for the discovered UEs, wherein the coverage status indications include whether each discovered UE is within or outside the coverage area.

[0309] Alternatively, UE 1300 may support transmitting from the UE to the NE a configuration message containing an indication to perform one or more of the Side Link Positioning Reference Signal (SL-PRS) or SL Positioning Data Message Transmission, the configuration message containing one or more SL positioning parameters; and receiving from the second device a resource configuration message containing a set of time-frequency resources in which the one or more of the SL-PRS or SL Positioning Data Message Transmission are to be performed.

[0310] Additionally, UE 1300 may be configured to support any or a combination of the following: wherein the UE receives a higher-layer trigger to perform one or more of the SL-PRS or SL positioning data message transmission; the higher-layer trigger includes one or more of the following: Sidelink Positioning Protocol (SLPP) layer, Vehicle-to-Everything (V2X) layer, ProSe layer, ranging layer, SL positioning layer, or Sidelink Positioning Application layer; wherein the UE receives the higher-layer trigger from another UE via one or more of the following: higher-layer signaling, which includes one or more of the Sidelink Positioning Protocol (SLPP), PC5 Radio Resource Control (RRC), or PC5-S; or lower-layer signaling, which includes Level 1 Sidelink Control Information (SCI), Level 1 Media Access Control (MAC) Control Element (CE), Level 2 SCI, or Level 2 MAC. One or more of the CE; the configuration message includes one or more of the following: SL positioning QoS profile, at least one delivery QoS profile indicating SL positioning delivery QoS parameters, SL positioning session identifier, SL-PRS transmission characteristics, or one or more UEs discovered to be used for SL positioning.

[0311] Additionally, UE 1300 may be configured to support any or a combination of the following: wherein the UE receives a system information message containing one or more common SL positioning configurations, the one or more common SL positioning configurations including at least one of the following: an SL positioning radio bearer configuration list, an SL-PRS priority, a positioning message priority, an SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information; wherein the UE includes one or more of the following: a target UE, an anchor UE, a server UE, or a device configured to perform one or more of SL-PRS or SL positioning data message transmissions; and wherein the configuration message includes one or more of the following: an SL positioning transmission resource request; an SL positioning receiver unicast, multicast, or broadcast purpose. The configuration message includes at least one of the following: a list of locations; one or more of the following: a list of SL positioning transmitters or receivers; an SL positioning UE type; one or more SL positioning capabilities; an SL positioning transmission resource discovery request; an SL positioning destination identifier; an SL positioning broadcast type; or the coverage status of the discovered UE; the configuration message includes one or more of the following: an SL-PRS dedicated shared pool for at least one of Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more SL-PRS and SL communication data dedicated resource pools for at least one of Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes a set of coverage status indications for the discovered UEs, wherein the coverage status indications include whether each discovered UE is within or outside the coverage area.

[0312] Controller 1306 manages input and output signals for UE 1300. Controller 1306 can also manage peripheral devices not integrated into UE 1300. In some implementations, controller 1306 may utilize an operating system, such as... Or other operating systems. In some implementations, controller 1306 may be implemented as part of processor 1302.

[0313] In some embodiments, UE 1300 may include at least one transceiver 1308. In other embodiments, UE 1300 may have more than one transceiver 1308. Transceiver 1308 may represent a wireless transceiver. Transceiver 1308 may include one or more receiver chains 1310, one or more transmitter chains 1312, or a combination thereof.

[0314] Receiver chain 1310 may be configured to receive signals (e.g., control information, data, packets) via wireless media. For example, receiver chain 1310 may include one or more antennas for receiving signals via air or wireless media. Receiver chain 1310 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 1310 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data through inverse processing of a modulation technique applied during signal transmission. Receiver chain 1310 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0315] Transmitter chain 1312 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 1312 may include at least one modulator for modulating data onto a carrier signal to prepare the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 1312 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 1312 may also include one or more antennas for transmitting the amplified signal over the air or in the wireless medium.

[0316] Figure 14 The illustration depicts an example of a processor 1400 according to various aspects of this disclosure. Processor 1400 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1400 may include a controller 1402 configured to perform various operations according to the examples described herein. Processor 1400 may optionally include at least one memory 1404, for example, said at least one memory may be an L1 / L2 / L3 cache memory. Additionally or alternatively, processor 1400 may optionally include one or more arithmetic logic units (ALUs) 1406. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0317] Processor 1400 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) according to the examples described herein. The processor chipset may include one or more cores, one or more cache memories (e.g., memory native to the processor chipset (e.g., processor 1400) or included in the processor chipset), or other memories (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), and others).

[0318] Controller 1402 may be configured to manage and coordinate various operations of processor 1400 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1400 to support various operations according to the examples described herein. For example, controller 1402 may operate as a control unit of processor 1400, thereby generating control signals that manage the operation of various components of processor 1400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0319] Controller 1402 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 1404 and determine subsequent instructions to be executed to enable processor 1400 to support various operations according to the examples described herein. Controller 1402 may be configured to track the memory addresses of instructions associated with memory 1404. Controller 1402 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1402 may be configured to interpret instructions and determine control signals to be output to other components of processor 1400 to enable processor 1400 to support various operations according to the examples described herein. Alternatively or additionally, controller 1402 may be configured to manage data flow within processor 1400. Controller 1402 may be configured to control data transfers between registers, ALU 1406, and other functional units of processor 1400.

[0320] Memory 1404 may include one or more cache memories (e.g., memory native to or included in the processor 1400, or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some embodiments, memory 1404 may reside within or on the processor chipset (e.g., native to the processor 1400). In some other embodiments, memory 1404 may reside external to the processor chipset (e.g., remote from the processor 1400).

[0321] Memory 1404 may store computer-readable, computer-executable code containing instructions that, when executed by processor 1400, cause processor 1400 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium (e.g., system memory or another type of memory). Controller 1402 and / or processor 1400 may be configured to execute the computer-readable instructions stored in memory 1404 to cause processor 1400 to perform various functions. For example, processor 1400 and / or controller 1402 may be coupled to or to memory 1404, processor 1400, and controller 1402, and may be configured to perform the various functions described herein. In some instances, processor 1400 may include multiple processors and memory 1404 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be individually or jointly configured to perform the various functions described herein.

[0322] One or more ALUs 1406 may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALUs 1406 may reside within or on a processor chipset (e.g., processor 1400). In some other embodiments, one or more ALUs 1406 may reside outside the processor chipset (e.g., processor 1400). One or more ALUs 1406 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 1406 may receive input operands and operation codes that determine the operation to be performed. One or more ALUs 1406 may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 1406s may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 1406s to handle conditional operations, comparisons, and bitwise operations.

[0323] Processor 1400 may support wireless communication according to the examples disclosed herein. Processor 1400 may be configured or operable to transmit from a first device to a second device a configuration message containing an indication to perform one or more of Side Link Positioning Reference Signal (SL-PRS) or SL Positioning Data Message Transmission, the configuration message containing one or more SL positioning parameters; and to receive from the second device a resource configuration message containing a set of time-frequency resources in which one or more of the SL-PRS or SL Positioning Data Message Transmission are to be performed.

[0324] Additionally, the processor 1400 may be configured to support any or a combination of the following: receiving a higher-layer trigger to perform one or more of the SL-PRS or SL positioning data message transmission; the higher-layer trigger comprising one or more of the following: a Sidelink Positioning Protocol (SLPP) layer, a Vehicle-to-Everything (V2X) layer, a ProSe layer, a ranging layer, an SL positioning layer, or a Sidelink Positioning Application layer; at least one controller is configured to cause the processor to receive the higher-layer trigger from the UE via one or more of the following: higher-layer signaling comprising one or more of the Sidelink Positioning Protocol (SLPP), PC5 Radio Resource Control (RRC), or PC5-S; or lower-layer signaling comprising Level 1 Sidelink Control Information (SCI), Level 1 Media Access Control (MAC) Control Element (CE), Level 2 SCI, or Level 2 MAC. One or more of the CEs; the configuration message includes one or more of the following: SL positioning QoS profile, at least one transport QoS profile indicating SL positioning transport QoS parameters, SL positioning session identifier, SL-PRS transport characteristics, or one or more UEs discovered for SL positioning; receiving a system information message containing one or more common SL positioning configurations, the one or more common SL positioning configurations including at least one of the following: SL positioning radio bearer configuration list, SL-PRS priority, positioning message priority, SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0325] Additionally, the processor 1400 may be configured to support any or a combination of the following: wherein the first device comprises one or more of the following: a target UE, an anchor UE, a server UE, or a device configured to perform one or more of SL-PRS or SL location data message transmissions; the configuration message comprises one or more of the following: an SL location transmission resource request; at least one of a list of SL location receiver unicast, multicast, or broadcast destinations; one or more of a list of SL location transmitters or receivers frequencies; an SL location UE type; one or more SL location capabilities; and SL location transmission resources. The configuration message includes: a discovery request; an SL location destination identifier; an SL location broadcast type; or the coverage status of the discovered UE; the configuration message includes one or more SL-PRS dedicated shared pools for at least one of Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes one or more SL-PRS and SL communication data dedicated resource pools for at least one of Mode 1 and Scheme 1 transmission or Mode 2 and Scheme 2 transmission; the configuration message includes a set of coverage status indications for the discovered UEs, wherein the coverage status indications include whether each discovered UE is within or outside the coverage area.

[0326] Figure 15 The diagram illustrates an example of an NE 1500 according to various aspects of this disclosure. The NE 1500 may include a processor 1502, a memory 1504, a controller 1506, and a transceiver 1508. The processor 1502, memory 1504, controller 1506, or transceiver 1508, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground).

[0327] Processor 1502, memory 1504, controller 1506, or transceiver 1508, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic means configured to or otherwise support components for performing the functions described in this disclosure, or any combination thereof.

[0328] Processor 1502 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 1502 may be configured to operate memory 1504. In some other embodiments, memory 1504 may be integrated into processor 1502. Processor 1502 may be configured to execute computer-readable instructions stored in memory 1504 to cause NE 1500 to perform various functions of this disclosure.

[0329] Memory 1504 may comprise volatile or non-volatile memory. Memory 1504 may store computer-readable, computer-executable code containing instructions that, when executed by processor 1502, cause NE 1500 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 1504 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available medium accessible by a general-purpose or special-purpose computer.

[0330] In some implementations, processor 1502 and memory 1504 coupled to processor 1502 may be configured to cause NE 1500 to perform one or more of the functions described herein (e.g., processor 1502 executing instructions stored in memory 1504). For example, processor 1502 may support wireless communication at NE 1500 according to the examples disclosed herein.

[0331] The NE 1500 may be configured or operable to support components for performing the following operations: receiving, at the NE and from the UE, a configuration message containing an indication to perform one or more of the Side Link Positioning Reference Signal (SL-PRS) or SL Positioning Data Message Transmission, the configuration message containing one or more SL positioning parameters; and transmitting to the UE a resource configuration message containing a set of time-frequency resources for performing the one or more of the SL-PRS or SL Positioning Data Message Transmission.

[0332] Additionally, the NE 1500 can be configured to support any or a combination of the following: transmitting system information messages containing one or more common SL positioning configurations; wherein the one or more common SL positioning configurations include at least one of the following: a list of SL positioning radio bearers, SL-PRS priority, positioning message priority, a list of SL positioning frequency information, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0333] The NE 1500 can be configured or operable to support components for performing the following operations: generating a semi-static configuration at the NE that includes one or more side link positioning reference signals (SL-PRS) transmission characteristics comprising one or more SL positioning or shared resource pools; and transmitting the semi-static configuration to the UE.

[0334] Additionally, the NE 1500 can be configured to support any or a combination of the following: the semi-static configuration is associated with one or more of a validity period or a valid area; the semi-static configuration is transmitted as one or more of a request message or a non-request message; an indication of the unavailability of the SL positioning semi-static configuration is transmitted to the UE; the SL-PRS transmission features include one or more of the following: an SL positioning dedicated resource pool identifier for one or more of the Mode 1 or Scheme 1 SL-PRS transmissions; an SL positioning dedicated resource pool identifier for one or more of the Mode 1 or Scheme 1 SL positioning transmissions; an SL positioning dedicated resource pool identifier for one or more of the Mode 2 or Scheme 2 SL-PRS transmissions; and an SL positioning dedicated resource pool for one or more of the Mode 2 or Scheme 2 SL positioning transmissions. Identifier; SL positioning shared resource pool identifier for one or more of the SL-PRS positioning transmissions in Mode 1 or Scheme 1; SL positioning shared resource pool identifier for one or more of the SL positioning transmissions in Mode 1 or Scheme 1; SL positioning shared resource pool identifier for one or more of the SL-PRS positioning transmissions in Mode 2 or Scheme 2; SL positioning shared resource pool identifier for one or more of the SL positioning transmissions in Mode 2 or Scheme 2; or an SL-PRS resource index containing one or more of the following: SL-PRS bandwidth, SL-PRS comb size, SL-PRS periodicity, SL-PRS resource identifier, SL-PRS identifier, SL positioning session identifier, SL bandwidth portion (BWP) identifier, SL carrier identifier, or SL-PRS repetition count.

[0335] Additionally, the NE 1500 can be configured to support any or a combination of the following: transmitting the semi-static configuration via one or more of UE-specific signaling or broadcast signaling; activating the semi-static configuration via one or more of UE-specific signaling or broadcast signaling; or deactivating the semi-static configuration via one or more of UE-specific signaling or broadcast signaling.

[0336] Alternatively, the NE 1500 may support: receiving at the NE from a second device a configuration message containing an indication to perform one or more of the Side Link Positioning Reference Signal (SL-PRS) or SL Positioning Data Message Transmission, the configuration message containing one or more SL positioning parameters; and transmitting to the second device a resource configuration message containing a set of time-frequency resources in which the one or more of the SL-PRS or SL Positioning Data Message Transmission are to be performed.

[0337] Additionally, the NE 1500 can be configured to support any or a combination of the following: wherein the NE transmission includes system information messages of one or more common SL positioning configurations; the one or more common SL positioning configurations include at least one of the following: a list of SL positioning radio bearers, SL-PRS priority, positioning message priority, a list of SL positioning frequency information, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

[0338] Alternatively, the NE 1500 may support: generating a semi-static configuration that includes one or more sidelink positioning reference signals (SL-PRS) transmission characteristics that contain one or more SL positioning or shared resource pools; and transmitting the semi-static configuration to the UE.

[0339] Additionally, the NE 1500 can be configured to support any or a combination of the following: the semi-static configuration is associated with one or more of a validity period or a valid area; the NE transmits the semi-static configuration as one or more of a request message or a non-request message; the NE transmits an indication to the UE of the unavailability of the SL positioning semi-static configuration; the SL-PRS transmission feature includes one or more of the following: an SL positioning dedicated resource pool identifier for one or more of the Mode 1 or Scheme 1 SL-PRS transmission; an SL positioning dedicated resource pool identifier for one or more of the Mode 1 or Scheme 1 SL positioning transmission; an SL positioning dedicated resource pool identifier for one or more of the Mode 2 or Scheme 2 SL-PRS transmission; an SL positioning dedicated resource pool identifier for one or more of the Mode 2 or Scheme 2 SL positioning transmission. Use a resource pool identifier; an SL positioning shared resource pool identifier for one or more of the SL-PRS positioning transmissions in Mode 1 or Scheme 1; an SL positioning shared resource pool identifier for one or more of the SL positioning transmissions in Mode 1 or Scheme 1; an SL positioning shared resource pool identifier for one or more of the SL-PRS positioning transmissions in Mode 2 or Scheme 2; an SL positioning shared resource pool identifier for one or more of the SL positioning transmissions in Mode 2 or Scheme 2; or an SL-PRS resource index containing one or more of the following: SL-PRS bandwidth, SL-PRS comb size, SL-PRS periodicity, SL-PRS resource identifier, SL-PRS identifier, SL positioning session identifier, SL bandwidth portion (BWP) identifier, SL carrier identifier, or SL-PRS repetition count.

[0340] Additionally, the NE 1500 can be configured to support any or a combination of the following: wherein the NE transmits the semi-static configuration via one or more of UE-specific signaling or broadcast signaling; wherein the NE activates the semi-static configuration via one or more of UE-specific signaling or broadcast signaling; and wherein the activation of the semi-static configuration is deactivated via one or more of UE-specific signaling or broadcast signaling.

[0341] Controller 1506 manages input and output signals for the NE 1500. Controller 1506 can also manage peripheral devices not integrated into the NE 1500. In some implementations, controller 1506 may utilize an operating system, such as... Or other operating systems. In some implementations, controller 1506 may be implemented as part of processor 1502.

[0342] In some embodiments, the NE 1500 may include at least one transceiver 1508. In other embodiments, the NE 1500 may have more than one transceiver 1508. The transceiver 1508 may represent a wireless transceiver. The transceiver 1508 may include one or more receiver chains 1510, one or more transmitter chains 1512, or a combination thereof.

[0343] Receiver chain 1510 may be configured to receive signals (e.g., control information, data, packets) via wireless media. For example, receiver chain 1510 may include one or more antennas for receiving signals via air or wireless media. Receiver chain 1510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 1510 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data through inverse processing of a modulation technique applied during signal transmission. Receiver chain 1510 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0344] Transmitter chain 1512 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 1512 may include at least one modulator for modulating data onto a carrier signal to prepare the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 1512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 1512 may also include one or more antennas for transmitting the amplified signal over the air or in the wireless medium.

[0345] Figure 16 The diagram illustrates a flowchart of method 1600 according to various aspects of this disclosure. The operation of the method can be implemented by a UE as described herein. In some embodiments, the UE can execute a set of instructions to control functional elements of the UE to perform the described functions. It should be noted that the methods described herein describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible.

[0346] At 1602, the method may include transmitting from a first device to a second device a configuration message including an indication to perform one or more of a Side Link Positioning Reference Signal (SL-PRS) or SL positioning data message transmission, the configuration message including one or more SL positioning parameters. Operation of 1602 may be performed according to the examples described herein. In some embodiments, aspects of operation of 1602 may be referenced from... Figure 13 The described UE is used to execute.

[0347] At 1604, the method may include receiving a resource configuration message from a second device, the resource configuration message including a set of time-frequency resources in which one or more of SL-PRS or SL positioning data message transmissions are to be performed. The operation of 1604 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1604 may be referenced from... Figure 13 The described UE is used to execute.

[0348] Figure 17 The diagram illustrates a flowchart of method 1700 according to various aspects of this disclosure. The operation of the method can be implemented by the NE described herein. In some embodiments, the NE may execute a set of instructions to control the functional elements of the NE to perform the described functions. It should be noted that the method described herein describes possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible.

[0349] At 1702, the method may include receiving, at a first device and from a second device, a configuration message including an indication to perform one or more of the lateral link positioning reference signal (SL-PRS) or SL positioning data message transmission, the configuration message including one or more SL positioning parameters. Operation of 1702 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1702 may be referenced... Figure 15 The NE described is used to execute.

[0350] At 1704, the method may include transmitting a resource configuration message to a second device, the resource configuration message including a set of time-frequency resources in which one or more of SL-PRS or SL positioning data message transmissions are to be performed. The operation of 1704 may be performed according to the examples described herein. In some embodiments, aspects of the operation of Zx04 may be referenced from... Figure 15 The NE described is used to execute.

[0351] Figure 18 The diagram illustrates a flowchart of method 1800 according to various aspects of this disclosure. The operation of the method can be implemented by the NE described herein. In some embodiments, the NE may execute a set of instructions to control the functional elements of the NE to perform the described functions. It should be noted that the method described herein describes possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible.

[0352] At 1802, the method may include generating a semi-static configuration at the first device of one or more sidelink positioning reference signals (SL-PRS) transmission characteristics comprising one or more SL positioning or shared resource pools. The operation of 1802 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1802 may be referenced... Figure 15 The NE described is used to execute.

[0353] At 1804, the method may include transmitting a semi-static configuration to a second device. The operation of 1804 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1804 may be referenced... Figure 15 The NE described is used to execute.

[0354] The descriptions herein are provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but is given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first device, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to enable the first device to: A configuration message is transmitted to the second device, including an indication to perform one or more of the lateral link positioning reference signal (SL-PRS) or SL positioning data message transmission, the configuration message including one or more SL positioning parameters; and Receive a resource configuration message from the second device, the resource configuration message including a set of time-frequency resources in which one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

2. The first device of claim 1, wherein the at least one processor is configured to receive a higher-level trigger to perform one or more of the SL-PRS or SL location data message transmissions.

3. The first device according to claim 2, wherein the higher layer trigger includes one or more of the following: the Sidelink Positioning Protocol (SLPP) layer, the Vehicle-to-Everything (V2X) layer, the ProSe layer, the ranging layer, the SL positioning layer, or the Sidelink Positioning Application layer.

4. The first device of claim 2, wherein the at least one processor is configured to receive the higher-layer trigger from the UE via one or more of the following: Higher-layer signaling, including one or more of the following: Sidelink Positioning Protocol Layer (SLPP), PC5 Radio Resource Control (RRC), or PC5-S; or Lower-level signaling includes one or more of the following: Level 1 Link Control Information (SCI), Level 1 Media Access Control (MAC) Control Element (CE), Level 2 SCI, or Level 2 MAC CE.

5. The first device according to claim 1, wherein the configuration message includes one or more of the following: an SL positioning quality of service (QoS) profile, at least one delivery QoS profile indicating SL positioning delivery QoS parameters, an SL positioning session identifier, an SL-PRS transmission characteristic, or one or more UEs discovered for SL positioning.

6. The first device of claim 1, wherein the at least one processor is configured to enable the first device to receive system information messages including one or more common SL positioning configurations, the one or more common SL positioning configurations including at least one of the following: an SL positioning radio bearer configuration list, an SL-PRS priority, a positioning message priority, an SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

7. The first device according to claim 1, wherein the first device comprises one or more of the following: a target user equipment (UE), an anchor UE, a server UE, or a device configured to perform one or more of SL-PRS or SL location data message transmission.

8. The first device according to claim 1, wherein the configuration message includes one or more of the following: SL locates and transmits resource requests; The SL location receiver is at least one of the unicast, multicast, or broadcast destination lists; SL is one or more of the frequency list for the transmitter or receiver; SL identifies the user equipment (UE) type; One or more SL positioning capabilities; SL locates and transmits resource discovery requests; SL locates the destination identifier; SL indicates the broadcast type; or The coverage status of the UE was detected.

9. The first device according to claim 1, wherein the configuration message includes one or more of the SL-PRS dedicated shared pools for at least one of mode 1 and scheme 1 transmission or mode 2 and scheme 2 transmission.

10. The first device according to claim 1, wherein the configuration message includes one or more SL-PRS and SL communication data dedicated resource pools for at least one of mode 1 and scheme 1 transmission or mode 2 and scheme 2 transmission.

11. The first device of claim 1, wherein the configuration message includes a set of coverage status indications for a group of discovered user equipment (UEs), and wherein the coverage status indications include whether each discovered UE is within or outside the coverage area.

12. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured to enable the processor to: A configuration message is transmitted from the first device to the second device, including an indication to perform one or more of the Side Link Positioning Reference Signal (SL-PRS) or SL positioning data message transmission, the configuration message including one or more SL positioning parameters; and Receive a resource configuration message from the second device, the resource configuration message including a set of time-frequency resources in which one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

13. The processor of claim 12, wherein the at least one controller is configured to cause the processor to receive a higher-level trigger to perform one or more of the SL-PRS or SL positioning data message transmissions.

14. The processor of claim 13, wherein the higher-layer trigger comprises one or more of the following: a sidelink positioning protocol (SLPP) layer, a vehicle-to-everything (V2X) layer, a ProSe layer, a ranging layer, an SL positioning layer, or a sidelink positioning application layer.

15. The processor of claim 13, wherein the at least one controller is configured to receive the higher-level trigger from the user equipment (UE) via one or more of the following: Higher-layer signaling, including one or more of the following: Sidelink Positioning Protocol Layer (SLPP), PC5 Radio Resource Control (RRC), or PC5-S; or Lower-level signaling includes one or more of the following: Level 1 Link Control Information (SCI), Level 1 Media Access Control (MAC) Control Element (CE), Level 2 SCI, or Level 2 MAC CE.

16. The processor of claim 12, wherein the configuration message includes one or more of the following: an SL positioning quality of service (QoS) profile, at least one delivery QoS profile indicating SL positioning delivery QoS parameters, an SL positioning session identifier, an SL-PRS transmission characteristic, or one or more user equipment (UEs) discovered for SL positioning.

17. The processor of claim 12, wherein the at least one controller is configured to enable the processor to receive system information messages including one or more common SL positioning configurations, the one or more common SL positioning configurations including at least one of the following: an SL positioning radio bearer configuration list, an SL-PRS priority, a positioning message priority, an SL positioning frequency information list, SL-PRS / SL positioning area validity information, or common SL positioning measurement information.

18. The processor of claim 12, wherein the first device comprises one or more of the following: a target user equipment (UE), an anchor UE, a server UE, or a device configured to perform one or more of SL-PRS or SL location data message transmission.

19. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor, coupled to and configured to enable the UE to: A configuration message is transmitted to the second device, including an indication to perform one or more of the lateral link positioning reference signal (SL-PRS) or SL positioning data message transmission, the configuration message including one or more SL positioning parameters; and Receive a resource configuration message from the second device, the resource configuration message including a set of time-frequency resources in which one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

20. A network device for wireless communication, comprising: At least one memory; and At least one processor coupled to and configured to equip the network with: The second device receives a configuration message including an indication to perform one or more of the lateral link positioning reference signal (SL-PRS) or SL positioning data message transmission, the configuration message including one or more SL positioning parameters; and A resource configuration message is transmitted to the second device, the resource configuration message including a set of time-frequency resources in which one or more of the SL-PRS or SL positioning data message transmissions are to be performed.

Images