WO2024176204A1

WO2024176204A1 - Full configuration for sidelink positioning

Info

Publication number: WO2024176204A1
Application number: PCT/IB2024/053055
Authority: WO
Inventors: Hyung-Nam Choi; Robin Rajan THOMAS
Original assignee: Lenovo Singapore Pte Ltd
Current assignee: Lenovo Singapore Pte Ltd
Priority date: 2023-03-31
Filing date: 2024-03-28
Publication date: 2024-08-29
Anticipated expiration: 2025-09-30

Abstract

Various aspects of the present disclosure relate to methods, apparatuses, and systems that support full configuration for sidelink (SL) positioning. For instance, implementations provide for an indicator identifying full configuration messaging in SL positioning protocol (SLPP) messages for which delta signaling is used. If a full configuration indicator is set in an SLPP message by a transmitting entity, the receiving entity can release currently stored content of an SLPP (e.g., from a previous SLPP message) and apply new content received in the full configuration message. A variety of different types of events can cause a full configuration messages.

Description

FULL CONFIGURATION FOR SIDELINK POSITIONING

RELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Application Serial No. 63/493,589 filed March 31, 2023 entitled “FULL CONFIGURATION FOR SIDELINK POSITIONING,” the disclosure of which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to SL communication.

BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a nextgeneration NodeB (gNB), or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system, e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0004] Some wireless communications proposals provide ways for using sidelink (SL) communication between UEs to enable and/or assist with UE positioning. Current proposals, however, may introduce signaling complexity and corresponding increases in overhead, and may not account for certain types of positioning scenarios.

SUMMARY [0005] The present disclosure relates to methods, apparatuses, and systems that support full configuration for SL positioning. For instance, implementations provide for an indicator identifying full configuration messaging in SL positioning protocol (SLPP) messages for which delta signaling is used. If a full configuration indicator is set in an SLPP message by a transmitting entity, the receiving entity can release currently stored content of a concerned SLPP (e.g., a previous SLPP message) and apply new content received in the full configuration message. A variety of different types of events can cause a full configuration messages.

[0006] Thus, by utilizing the described techniques, signaling latency experienced during SL positioning can be reduced and SL positioning accuracy can be increased.

[0007] Some implementations of the methods and apparatuses described herein may further include transmitting, from a first apparatus to a second apparatus and via delta signaling, a first message including first SL positioning-related information; generating a second message including second SL positioning-related information; and transmitting, to the second apparatus, the second message via full configuration signaling.

[0008] Some implementations of the methods and apparatuses described herein may further include: generating the second message to include a full configuration indicator; further including using the full configuration signaling for the second message based at least in part on an event; the event includes one or more of an addition of an apparatus to an existing apparatus group, a usage of a new ciphering key for protecting the second SL positioning-related information, an expiry of a timer, or when an amount of delta of SL positioning-related information is below a threshold amount; the first apparatus includes a SL positioning server device and the second apparatus includes a SL target device; the first message and the second message include respective SL provide assistance data messages; the first SL positioning-related information and the second SL positioning-related information include respective SL positioning reference signal (PRS) configuration information.

[0009] Some implementations of the methods and apparatuses described herein may further include: where the second apparatus is part of an apparatus group and the method further includes: generating the second message based at least in part on a third apparatus joining the apparatus group; and transmitting the second message via full configuration signaling to the apparatus group including the second apparatus and the third apparatus; the first message is protected via a first ciphering key and the method further includes: generating the second message to be protected via a second ciphering key; transmitting the second ciphering key to a fourth apparatus for forwarding to the second apparatus; and transmitting the second message protected via the second ciphering key via the full configuration signaling.

[0010] Some implementations of the methods and apparatuses described herein may further include: receiving, at a first apparatus from a second apparatus and via delta signaling, a first message including first SL positioning-related information; receiving, from the second apparatus, a second message via full configuration signaling, the second message including second SL positioning-related information; and releasing, based at least in part on the full configuration signaling, the first SL positioning-related information and apply the second SL positioning-related information.

[0011] Some implementations of the methods and apparatuses described herein may further include: the second message includes a full configuration indicator; the first apparatus includes a SL target device and the second apparatus includes a SL positioning server device; the first apparatus is part of an apparatus group, and the second SL positioning-related information includes an indication that a third apparatus joins the apparatus group; further including: receiving, from a fourth apparatus, a first ciphering key and utilize the first ciphering key to access the first SL positioning- related information; and receiving, from the fourth apparatus, a second ciphering key and utilize the second ciphering key to access the second SL positioning-related information.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 illustrates an example of a wireless communications system that supports full configuration for SL positioning in accordance with aspects of the present disclosure.

[0013] FIG. 2 illustrates an example scenario for message transfer.

[0014] FIG. 3 illustrates an example location services (LCS) architecture.

[0015] FIG. 4 illustrates an example procedure for a regulatory location service for a nonroaming scenario. [0016] FIG. 5 illustrates an example procedure for obtaining UE location and/or providing positioning assistance data.

[0017] FIG. 6 illustrates different SL communication scenarios.

[0018] FIG. 7 illustrates an example message that includes an example of the use of need codes.

[0019] FIG. 8 illustrates an example procedure that supports full configuration for SL positioning in accordance with aspects of the present disclosure.

[0020] FIG. 9 illustrates an example of a block diagram of devices that support full configuration for SL positioning in accordance with aspects of the present disclosure.

[0021] FIGs. 10 through 14 illustrate flowcharts of methods that support full configuration for SL positioning in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0022] In wireless communications systems, SL communications have been considered to enabling and/or assisting with device positioning, e.g., UE positioning. For instance, the SL positioning protocol (SLPP) has been proposed for exchanging SL positioning related messages between UEs over the PC5 interface. The cast types which are considered for SLPP signaling include unicast, groupcast, and broadcast. To attempt to support the radio resource efficient transmission of SLPP signaling messages over PC5, the use of delta signaling is being discussed. Delta signaling, for instance, refers to the notion that the content received in a message differs from the content received in a previous message. However, some scenarios may use full configuration signaling for SLPP messages. Full configuration refers to the notion that upon reception of the full configuration a target UE releases the currently stored message content and applies the new received message content.

[0023] Some proposals for supporting full configuration signaling discuss associating the transmission of an SLPP message with an SL positioning session. For instance, in cases of full configuration signaling a concerned session will be released and a new session will be setup. However, such proposals may introduce complexity in terms of signaling load and session handling. Furthermore, such proposals may not work in session-less positioning procedures. [0024] Accordingly, this disclosure provides for techniques that support full configuration for SL positioning. For instance, implementations provide for a “fullConfig” indicator in SLPP messages for which delta signaling is used. If a fullConfig indicator is set, for example, in an SLPP message by a transmitting entity, the receiving entity releases the currently stored content of a concerned SLPP message (e.g., a previous SLPP message) and applies new content received in the full configuration message. A variety of different types of events can cause a full configuration message, examples of which are detailed throughout this disclosure.

[0025] Thus, by utilizing the described techniques, signaling latency experienced during SL positioning can be reduced and SL positioning accuracy can be increased. More specifically, efficient transmission of SLPP messages can be supported in most SL communication scenarios, such as for PC5-only and joint PC5-Uu-based operation scenarios. Further, efficient transmission of SLPP messages can be supported for both session-based and session-less positioning.

[0026] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flowcharts.

[0027] FIG. 1 illustrates an example of a wireless communications system 100 that supports full configuration for SL positioning in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc. [0028] The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a RAN, a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0029] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0030] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

[0031] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment), as shown in FIG. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

[0032] A UE 104 may also be able to support wireless communication directly with other UEs

104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, V2X deployments, or cellular- V2X deployments, the communication link 114 may be referred to as a SL. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0033] A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an SI, N2, or another network interface). The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0034] In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-real time (RT) RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0035] An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0036] Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3), a layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (LI) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU.

[0037] Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs). In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU).

[0038] A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., Fl, Fl-c, Fl-u), and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface). In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

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

[0040] The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an SI, N2, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a PDU session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106). [0041] In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communication system 100, e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) to perform various operations (e.g., wireless communications). In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (e.g., multiple frame structures). The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0042] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., /r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. The first numerology (e.g., /r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., /2=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., /r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., jU=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0043] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0044] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency-division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0045] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short- range, high data rate capabilities.

[0046] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., ^=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /z=l ), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /r=3), which includes 120 kHz subcarrier spacing.

[0047] According to implementations for full configuration for SL positioning, a UE 104(1) transmits a SL positioning message 120 to a UE 104(2). The UE 104(1), for instance, represents a SL positioning server UE and the UE 104(2) represents a SL target device for which a position is to be estimated. The SL positioning message 120 can include various information pertaining to SL positioning, examples of which are detailed throughout this disclosure. Further, the SL positioning message 120 can be generated and transmitted via delta signaling. The UE 104(1) then generates a SL positioning message 122 that includes different SL positioning information than the SL positioning message 120 and transmits the SL positioning message 122 to the UE 104(2). Further, the UE 104(1) sets an indicator on the SL positioning message 122 to identify the SL positioning message 122 as a full configuration message and transmits the SL positioning message 122 to the UE 104(2) via full configuration signaling. Based at least in part on the SL positioning message 122 being indicated via full configuration signaling, the UE 104(2) performs a release and apply operation 124 to release SL positioning information from the SL positioning message 120 and apply SL positioning information from the SL positioning message 122.

[0048] SL positioning has been discussed to support the target accuracy requirements for SL positioning as listed in Table 1 below. SL positioning, for instance, is intended to be applied for a variety of use cases such as V2X, public safety, IIoT, and commercial use cases. One goal of SL positioning is to determine the position of a UE by using SL positioning methods such as Round Trip Time (RTT)-type solutions using SL, SL- Angle of Arrival (Ao A) and SL-Time Difference of Arrival (TDOA). SL positioning can be based on new SL PRS that is transmitted over the PC5 interface and can be supported in many coverage scenarios (e.g., in-coverage, partial coverage, and out-of-coverage scenarios) and for PC5-only-based and joint PC5-Uu-based operation scenarios. For exchanging the SL positioning related information between UEs over the PC5 interface a new protocol denoted as SLPP can be introduced. The following functionalities, for instance, are to be supported by SLPP: SL Positioning Capability Transfer; SL Positioning Assistance Data exchange; SL Location Information Transfer; Error handling; and Abort.

[0049] The cast types which are considered for SLPP signaling include unicast, groupcast, and broadcast, but unicast/one-to-one operation can be considered as baseline for exchange of SLPP signaling between UEs. For exchange of SL positioning capability and SL positioning assistance data information, groupcast and broadcast (in addition to unicast) can be considered to be supported when the protection of groupcast/broadcast of SL positioning signaling can be ensured. [0050] To support the radio resource efficient transmission of SLPP signaling messages over PC5 the use of delta signaling is being discussed. “Delta signaling,” for instance, indicates that the content received in a message differs from the content received in a previous message. Currently, delta signaling is applied in LPP and NR RRC specifications only for downlink (DL) messages which are transmitted from the network to the UE. The “delta” can be applied for the optionally present fields/parameters in the DL messages and the handling of those fields/parameters at the UE when absent is defined by using so-called need codes.

[0051] Currently, the SL Provide Assistance Data message is the candidate message for which delta signaling may be useful since it can carry the SL PRS configuration which may be of large size. The SL Provide Assistance Data message can be provided by the location server (e.g. LMF in network and/or SL Positioning Server UE) to the Target UE. Based on the received SL PRS configuration the Target UE can receive the SL PRS that is transmitted by the Anchor UE and perform measurements according to the supported SL positioning methods.

[0052] However, in some cases there may be a need to use full configuration signaling for the SL Provide Assistance Data message. “Full configuration” can mean that upon reception of the full configuration the Target UE releases the currently stored SL PRS configuration and applies the new received SL PRS configuration. One example for the use of full configuration signaling may be in the case of groupcast transmission of the SL Provide Assistance Data message and whenever a new Target UE joins the group. In order to support full configuration signaling for the SL Provide Assistance Data message (and for other SLPP messages as well for which delta signaling is used) a solution is proposed in this disclosure.

[0053] An alternative solution to support full configuration signaling is to associate the transmission of the SL Provide Assistance Data message with an SL positioning session. In case of full configuration signaling the concerned session will then be released and a new session will be setup. However, this alternative solution causes some complexity in terms of signaling load and session handling. Furthermore, it may not work in session-less positioning procedures. Table 1: Target accuracy requirements for SL positioning

Note: “Set A” and “Set B” refer to the categorization of requirements into two sets.

[0054] In some wireless system designs only Cell-identifier (ID) and RAT-independent positioning methods (e.g. Global Navigation Satellite System (GNSS)) are supported in NR. In order to meet the positioning requirements for regulatory (e.g., emergency services) and commercial use cases (e.g., IIoT) as listed in Table 2 below, RAT-dependent (for both FR1 and FR2) and RAT- independent positioning methods (such as Precise Point Positioning (PPP) and Real-Time Kinematic (RTK)) have been specified. Table 3 below shows the list of RAT-dependent positioning methods such as specified in Rel-16.

Table 2: Positioning requirements for regulatory and commercial use cases

Table 3: RAT-dependent positioning methods

[0055] In order to meet the higher positioning requirements for commercial use cases and specifically IIoT use cases such as listed in Table 4 below, further enhancements for NR positioning have been specified in Rel-17 such as:

• Improvements of positioning accuracy and latency (e.g., uplink (UL)-AoA enhancements, DL- Angle of Departure (AoD) enhancements, Preconfigured measurement gap, Preconfigured PRS processing window etc.)

• Improvements of network efficiency (On-Demand PRS transmission)

• Improvement of device efficiency (Positioning in RRC INACTIVE)

• Providing high integrity and reliability requirements (GNSS integrity)

• Enhancements of A-GNSS positioning

Table 4: Positioning requirements for commercial and industrial internet of things (IIoT) use cases

[0056] In the 5GS architecture that is applicable to positioning of a UE either the UE itself or the location server determines the UE position depending on the applied positioning method. And for exchanging the positioning related information (e.g. location related measurements, location estimates, assistance data), LIE Positioning Protocol (LPP) as specified in Technical Specification (TS) 37.355 can be used point-to-point between the location server and the UE. In LPP the following message types are supported:

• Request Capabilities

• Provide Capabilities

• Request Assistance Data

• Provide Assistance Data

• Request Location Information

• Provide Location Information

• Abort

• Error

[0057] FIG. 2 illustrates an example scenario 200 for message transfer. The scenario 200, for instance, illustrates example LPP message transfer between the LMF (location server) and the UE. LPP messages are carried as transparent PDUs across intermediate network interfaces using the appropriate protocols.

[0058] Step 1: The LMF sends an LPP message to the AMF. The LPP message may be the Request Capabilities message to request the UE to send its positioning capabilities.

[0059] Step 2: The AMF transports the received LPP message to the NG-RAN node by including the LPP message into the LPP message container of the DL NAS Transport message.

[0060] Step 3: The NG-RAN node transports the received LPP message container to the UE by including the LPP message container into the RRC DLInformationTransfer message as specified in TS 38.331.

[0061] Step 4: Upon receiving the Request Capabilities message, the UE generates the Provide Capabilities message as response. The UE sends then the Provide Capabilities message to the NG- RAN node by including the LPP message into the RRC ULInformationTransfer message as specified in TS 38.331. [0062] Step 5: The NG-RAN node transports the LPP message received from the UE to the AMF by including the LPP message into the LPP message container of the UL NAS Transport message.

[0063] Step 6: The AMF extracts the LPP message from the received NAS message/LPP message container and sends it to the LMF.

[0064] The Location Services (LCS) feature in 3GPP provides the mechanisms to support mobile location services for operators, subscribers and third-party service providers. Examples of location-based services include emergency services, tracking services, location-based information services (navigation, city sightseeing, location dependent content broadcast, mobile yellow pages etc.). The location information may be requested by and reported to a client (application) associated with the UE and/or by a client within or attached to the 5GC.

[0065] FIG. 3 illustrates an example LCS architecture 300. In the architecture 300, for instance, an external LCS client requests the 5GC for the current location of the target UE and the relation of the LCS entities is shown. The external LCS Client interacts with gateway mobile location center (GMLC) for the purpose of obtaining location information for one or more (target) UEs. The LCS Client may reside in a UE and may be implemented as hardware and/or software, e.g., application. Examples for LCS client include 911 emergency dispatch center (PSAP), a map application, etc.

[0066] The GMLC is the first node an external LCS client accesses in a Public Land Mobile Network (PLMN) and works as a location server to an external application for location information. The LMF manages the overall co-ordination and scheduling of resources required for the location of a UE that is registered with or accessing 5GC. It also calculates or verifies a final location and any velocity estimate and may estimate the achieved accuracy. The LMF processes the location services request which may include transferring assistance data to the target UE to assist with UE-based and/or UE-assisted positioning and/or may include positioning of the target UE. The LMF then returns the position estimate for a UE back to the AMF. In the case of a location service requested by an entity other than the AMF (e.g., a GMLC or UE), the AMF returns the location result to this entity. In C-plane the LMF works as location server.

[0067] The AMF contains functionality responsible for managing positioning for a target UE for all types of location request. The AMF receives a request for some location services associated with a particular target UE from another entity (e.g., GMLC or UE) or the AMF itself decides to initiate some location service on behalf of a particular target UE (e.g., for an emergency call from the UE). The AMF then sends a location services request to an LMF.

[0068] The NG-RAN node (i.e. gNB) is involved in the handling of various positioning procedures including positioning of a target UE, provision of location related information not associated with a particular target UE and transfer of positioning messages between an AMF or LMF and a target UE. The Target UE is the UE whose position (absolute or relative) is to be obtained by the network or by the UE itself.

[0069] NRPPa is the C-plane radio network layer signaling protocol between a NG-RAN node (gNB) and the LMF. LPP is a point-to-point positioning protocol that supports positioning and location related services for a target device. In C-plane, LPP is terminated between a target device and an LMF.

[0070] The following types of location requests are specified in 3GPP:

[0071] Network Induced Location Request (NI-LR): A serving AMF for a UE initiates localization of the UE for a regulatory service (e.g. an emergency call from the UE) or for verification of a UE location (country or international area) for NR satellite access.

[0072] Mobile Terminated Location Request (MT-LR): An LCS client external to or internal to a serving PLMN sends a location request to the PLMN for the location of a target UE.

[0073] Mobile Originated Location Request (MO-LR): A UE sends a request to a serving PLMN for location related information for the UE itself.

[0074] Immediate Location Request: An LCS client sends or instigates a location request for a target UE (or group of target UEs) and expects to receive a response containing location information for the target UE (or group of target UEs) within a short time period which may be specified using LCS QoS. In regulatory cases, one or more responses of the target UE's location information can be expected. An immediate location request may be used for an NI-LR, MT-LR or MO-LR.

[0075] Deferred Location Request: An LCS client sends a location request to a PLMN for a target UE (or group of target UEs) and expects to receive a response containing the indication of event occurrence and location information if requested for the target UE (or group of target UEs) at some future time (or times), which may be associated with specific events associated with the target UE (or group of target UEs). Deferred location requests are supported only for an MT-LR.

[0076] FIG. 4 illustrates an example procedure 400 for a regulatory location service for a nonroaming scenario. The procedure 400, for instance, can be implemented as a 5GC -MT-LR procedure for the regulatory location service for non-roaming scenario as specified in TS 23.273. In such a scenario, an external LCS client requests the 5GC for the current location of the target UE. It can be assumed that the target UE is identified using a Subscription Permanent Identifier (SUPI) or Generic Public Subscription Identifier (GPSI).

[0077] Step 1: The external client sends a request to the GMLC for the current location of the target UE. The request includes amongst other the requested LCS QoS.

[0078] Step 2: The GMLC sends the Namf Location ProvidePositioninglnfo Request to the AMF to request the current location of the UE.

[0079] Step 3: If the UE is in connection management (CM) -IDLE state, the AMF initiates a network triggered Service Request procedure to establish a signaling connection with the UE.

[0080] Step 4: The AMF selects an LMF based on the available information (e.g. requested LCS QoS, LMF capabilities, LMF load, LMF location) or based on AMF local configuration (if AMF is configured locally with a mapping table of UE identity and LMF address).

[0081] Step 5: The AMF sends the Nlmf Location DetermineLocation Request to the selected LMF to request the current location of the UE. The request includes amongst other the requested LCS QoS and the UE positioning capability if available.

[0082] Step 6: The LMF performs positioning procedures and determines the geographical location of the UE.

[0083] Step 7: The LMF returns the Nlmf Location DetermineLocation Response towards the AMF to return the current location of the UE, e.g., the location estimate and accuracy and may include information about the positioning method and the timestamp of the location estimate. [0084] Step 8: The AMF returns the Namf Location ProvidePositioninglnfo Response towards the GMLC to return the current location of the UE.

[0085] Step 9: The GMLC sends the location service response including the location information of the UE to the external client.

[0086] FIG. 5 illustrates an example procedure 500 for obtaining UE location and/or providing positioning assistance data. The example procedure 500, for instance, represents an exemplary 5GC-M0-LR procedure as specified in TS 23.273 where the UE requests the serving PLMN to obtain the location of the UE and/or provides positioning assistance data. It can be assumed that an LCS client resides in the UE and initiates the MO-LR.

[0087] Step 1: If the UE is in CM-IDLE state, UE instigates the UE triggered Service Request procedure in order to establish a signaling connection with the AMF.

[0088] Step 2: The UE sends an MO-LR Request message included in a UL NAS TRANSPORT message to the AMF. Different types of location services can be requested: location estimate of the UE, location estimate of the UE to be sent to an LCS client, or positioning assistance data. If the UE is requesting its own location or that its own location be sent to an LCS client (e.g. for using a location-based service), this message carries the requested LCS QoS information, e.g. accuracy, response time. If the UE is requesting that its location be sent to an LCS client, the message also includes the identity of the LCS client and the address of the GMLC through which the LCS client should be accessed. If the UE is instead requesting positioning assistance data, the embedded LPP message specifies the type of assistance data and the positioning method for which the assistance data applies.

[0089] Step 3: The AMF selects an LMF based on the available information (e.g. requested LCS QoS, LMF capabilities, LMF load, LMF location) or based on AMF local configuration, e.g., if AMF is configured locally with a mapping table of UE identity and LMF address.

[0090] Step 4: The AMF sends the Nlmf Location DetermineLocation Request to the selected LMF. The request includes amongst other an indication whether a location estimate, or positioning assistance data is requested. [0091] Step 5: If the UE is requesting its own location, the LMF performs positioning procedures and determines the geographical location of the UE. If the UE is instead requesting positioning assistance data, the LMF transfers this data to the UE.

[0092] Step 6: When a location estimate best satisfying the requested LCS QoS has been obtained or when the requested location assistance data has been transferred to the UE, the LMF returns the Nlmf Location DetermineLocation Response towards the AMF. The response includes the location estimate, its age and accuracy. If the UE is requesting positioning assistance data, steps 7 to 11 can be skipped.

[0093] Step 7: If the location estimate was successfully obtained, the AMF sends the Ngmlc Location LocationUpdate Request to the GMLC. The request carries the identity of the UE, the event causing the location estimate (5GC-M0-LR) and the location estimate, its age and obtained accuracy indication. In addition, the request includes the identity of the LCS Client.

[0094] Step 8: The GMLC transfers the Location Information message to the LCS client, carrying the identity of the UE, the event causing the location estimate (5GC-M0-LR) and the location estimate in accordance with the LCS QoS requested by the UE.

[0095] Step 9: The LCS Client sends the GMLC the Location Information Ack message signaling that the location estimate of the UE has been received successfully.

[0096] Step 10: The GMLC sends a Ngmlc Location LocationUpdate Response to AMF to acknowledge the successful reception of the location estimate by the LCS Client.

[0097] Step 11 : The AMF sends an MO-LR Response message included in a DL NAS TRANSPORT message. If the UE is requesting its own location, the response carries any location estimate requested by the UE and the timestamp of the location estimate (if available) including the indication received from LMF whether the obtained location estimate satisfies the requested accuracy or not, or an indicator whether a location estimate was successfully transferred to the identified LCS client.

[0098] FIG. 6 illustrates different SL communication scenarios 600. Regarding NR SL communication and discovery, the feature SL communication was introduced in Rel-16 NR to support V2X and non-V2X services. The interface used for SL communication (transmission/reception) between two UEs in proximity is denoted as PC5. Table 5 below illustrates scenarios 600 which are supported for SL communication where UE1 and UE2 are located incoverage (IC), partial coverage (PC) and out-of-coverage (OOC) of a cell.

Table 5: Sidelink communication scenarios

[0099] The transmission and reception of user traffic over the PC5 interface is supported for unicast, groupcast and broadcast transmission. The transmission and reception of signaling traffic over the PC5 interface is supported only for unicast transmission. An SL connection over PC5 is defined as a logical connection between a pair of Source and Destination Layer-2 IDs. Source and Destination Layer-2 IDs identify the sender and the target of the SL communication, respectively. And for a cast type a corresponding pair of a Source Layer-2 ID and a Destination Layer-2 ID is used. The SL communication is based on the Proximity-based Services (ProSe) feature.

[0100] In order to enable SL communication between UEs in proximity the SL discovery procedure may need to be performed by the UEs. The SL discovery procedure is used by UE(s) to discover or to be discovered by other UE(s) in proximity. For instance, a UE that wants to discover other UE(s) in proximity transmits a discovery message over PC5. Other UE(s) in proximity monitor the discovery message and if they want to be discovered they respond with a discovery response message. After discovery the UE can establish a SL communication connection with each of the UE(s) which responded. More details to NR SL communication and discovery can be found in TS 23.304.

[0101] The following are some example SL positioning terminologies and can be used to refer to roles of particular UEs and/or other devices participating in a SL positioning session. [0102] Initiator device initiates a SL positioning/ranging session, may be a network entity, (e.g., gNB, LMF) or UE/roadside unit (RSU).

[0103] Responder device responds to a SL positioning/ranging session from an initiator device, and may be implemented in various ways such as a network entity (e.g., gNB, LMF), UE/roadside unit (RSU), etc.

[0104] Target UE: UE of interest whose position (absolute or relative) is to be obtained by the network or by the UE itself.

[0105] Sidelink positioning: Refers to positioning of a UE using reference signals transmitted over SL, i.e., PC5 interface, to obtain absolute position, relative position, or ranging information.

[0106] Ranging: Determination of the distance and/or the direction between a UE and another entity, e.g., Anchor UE.

[0107] Anchor UE: UE supporting positioning of Target UE, e.g., by transmitting and/or receiving reference signals for positioning, providing positioning-related information, etc., over the PC5 interface. This device may also be referred to as SL Reference UE.

[0108] Assistant UE: A UE supporting Ranging/Sidelink between a SL Reference UE and Target UE over PC5, such as when the direct Ranging/Sidelink positioning between the SL Reference UE/ Anchor UE and the Target UE cannot be supported. The measurement/results of the Ranging/Sidelink Positioning between the Assistant UE and the SL Reference UE and that between the Assistant UE and the Target UE are determined and used to derive the Ranging/Sidelink Positioning results between Target UE and SL Reference UE.

[0109] SL Positioning Server UE: A UE offering location calculation, for SL Positioning and Ranging based service. It interacts with other UEs over PC5 as necessary in order to calculate the location of the Target UE. Target UE or SL Reference UE can act as SL Positioning server UE if location calculation is supported.

[0110] SL Positioning Client UE: A third-party UE, other than SL Reference UE and Target UE, which initiates Ranging/Sidelink positioning service request on behalf of the application residing on it. [0111] Regarding delta signaling and full configuration signaling in NR RRC, delta signaling is used in the NR RRC specification for DL messages which are transmitted from the network to the UE in order to reduce the signaling load over the Uu radio interface especially for large DL RRC messages such as RRCReconfiguration and RRCResume. The “delta” is applied for the optionally present fields/parameters in the DL RRC messages and the handling of those fields/parameters at the UE when absent is defined by using so-called need codes. In NR RRC the need codes Need S, Need M, Need N and Need R are specified, see Table 6 below.

Table 6: Meaning of need codes

[0112] FIG. 7 illustrates an example message 700 that includes an example of the use of need codes. The message 700, for instance, represents a DL RRC message. In the message 700 the abstract syntax notation one (ASN.1) structure of a DL RRC message is shown that consists of 6 fields (fieldl to field6). The two fields fieldl and field2 are mandatory present, e.g., they are always present whenever the RRC message is transmitted to the UE. The other four fields fields to field6 are optionally present and the handling of those fields at the UE when absent is defined by their need codes. Let’s consider the following example: In the first transmission of the DL RRC message all 6 fields are present and the UE stores the values of the mandatory present fields and the optionally present fields according to the defined need codes. In the second transmission of the DL RRC message only the two mandatory present fields fieldl and field2 are present. Upon reception of the second DL RRC message the UE replaces the values of the stored mandatory fields by the new ones and takes the following actions for the absent fields:

[0113] Field 3: the UE takes no action, e.g., the UE does not maintain the previously received value for field 3.

[0114] Field 4: the UE follows the specified behavior, e.g., the UE applies a default value for field 4.

[0115] Field 5: the UE maintains the previously received value for field 5.

[0116] Field 6: the UE releases the previously received value for field 6.

[0117] In some scenarios the network cannot use delta signaling and instead needs to use full configuration signaling for the RRCReconfiguration and RRCResume messages. For instance, full configuration by the RRCReconfiguration message is used in scenarios for handover when a UE is moved from a source RAN node of a release X to a target RAN node of an earlier release X-l . A reason is that the target RAN node may not support all the radio configurations that were configured to the UE in the source RAN node. In this case the UE needs to be fully re-configured with radio configurations of the target RAN node. The full configuration can be indicated by the network to the UE by using the fullConfig indicator in the concerned RRC message. If the UE receives the RRCReconfiguration or RRCResume message with the fullConfig indicator then it releases the currently stored radio configurations and applies the new radio configurations received in the concerned RRC message. [0118] Accordingly, solutions are provided in this disclosure to support full configuration signaling, such as for SLPP messages for which delta signaling is used. In implementations, a fullConfig indicator is introduced for SLPP messages for which delta signaling is used. For instance, if the fullConfig indicator is set in an SLPP message by a transmitting entity then the receiving entity releases the currently stored content of the concerned SLPP message and applies the new received content. The following represent non-limiting example events on which the new fullConfig indicator can be set:

[0119] For groupcast transmission: whenever a new SL UE is included in the group.

[0120] For unicast/groupcast/broadcast transmission: when ciphering is applied for protecting the content of the SLPP message and new ciphering key is used for protecting the message content.

[0121] For unicast/groupcast/broadcast: upon expiry of a periodic timer configured by network, e.g. LMF, or pre- configured by network. The timer is started for the initial/first transmission of the SLPP message and restarted whenever the SLPP message is transmitted using full configuration signaling.

[0122] For unicast/groupcast/broadcast: when the amount of delta is low, e.g., is below a threshold amount of change for a previous set of data.

[0123] In the following discussion several conditions may apply, including: (1) The out-of- coverage SL communication scenario as shown in the scenarios 600; PC5-only positioning operation scenario; The following types of SL UEs are participating in the SL positioning session: Target UE1, Target UE2, Target UE3, Anchor UE and SL Positioning Server UE; Delta signaling and full configuration signaling are used for the SL Provide Assistance Data message; The SL Provide Assistance Data message contains the SL PRS configuration; The SL PRS configuration consists of mandatory present and optionally present fields/parameters for which need codes are defined; and in case the Anchor UE and SL Positioning Server UE are the same UE, the applicable steps and behaviors can be the steps 4, 5, 6, 8, 9, 10 and 11 discussed with reference to the procedure 800 discussed below.

[0124] FIG. 8 illustrates an example procedure 800 that supports full configuration for SL positioning in accordance with aspects of the present disclosure. In the procedure 800: [0125] Step 1: The SL Positioning Server UE wants to determine the current location of the Target UE1 and UE2. In order to allow the Target UEs to perform positioning measurements, the Server UE sends to the Anchor UE the SL PRS configuration request message to request the SL PRS configuration that the Anchor UE supports.

[0126] Step 2: The Anchor UE sends to the Server UE the SL PRS configuration response message indicating the SL PRS configuration it supports.

[0127] Step 3: Based on the response received from the Anchor UE the Server UE sends to the Anchor UE the SL PRS activation message indicating the SL PRS configuration that the Anchor UE shall transmit over PC5. The SL PRS activation message includes the characteristics of SL PRS transmission, e.g., start time and duration, frequency range (FR1/FR2), resource bandwidth, sequence ID, comb size, resource repetition, muting configuration, power control parameters (e.g., SL Pathloss reference, SL Tx power), etc.

[0128] Step 4: The Anchor UE transmits the SL PRS to the Target UEs in accordance with the SL PRS activation message received from the Server UE.

[0129] Step 5: To reduce signaling load for transmitting the SL Provide Assistance Data message to the Target UEs the Server UE establishes a group consisting of Target UE1 and UE2.

[0130] Step 6: The Server UE sends the SL Provide Assistance Data message per groupcast transmission to the Target UEs. The SL Provide Assistance Data message contains the SL PRS configuration that has been activated by the Server UE in step 3. The Target UE1 and UE2 store the content of the received SL PRS configuration in accordance with the defined need codes.

[0131] Step 7: After some time the Server UE decides to change the characteristics of SL PRS transmission and sends to the Anchor UE the SL PRS activation message indicating the change of SL PRS configuration.

[0132] Step 8: The Anchor UE transmits the SL PRS to the Target UEs in accordance with the SL PRS activation message received from the Server UE.

[0133] Step 9: The Server UE sends the SL Provide Assistance Data message per groupcast transmission to the Target UEs using delta signaling. The SL Provide Assistance Data message contains the SL PRS configuration that has been activated by the Server UE in step 7 and that is “delta” to the SL PRS configuration sent in step 6. The Target UE1 and UE2 store the content of the received SL PRS configuration in accordance with the defined need codes.

[0134] Step 10: The SL Positioning Server UE wants to determine the current location of the Target UE3 and extends the current group by adding Target UE3.

[0135] Step 11 : The Server UE sends the SL Provide Assistance Data message per groupcast transmission to the Target UEs using full configuration signaling. The SL Provide Assistance Data message contains the fullConfig indicator and SL PRS configuration that has been activated by the Server UE in step 7. The Target UE1 and UE2 release the currently stored content of the SL PRS configuration and apply the new received configuration. The Target UE3 stores the content of the received SL PRS configuration in accordance with the defined need codes.

[0136] In alternative or additional implementations, the assumptions and message flow are primarily the same as for the implementation described above with reference to the procedure 800. One difference, however, is that it can be assumed that the SL PRS configuration in the SL Provide Assistance Data message is protected by applying ciphering. As result, the following steps are different compared to the discussion of the procedure 800 above:

[0137] Step 3: The SL PRS activation message indicating the SL PRS configuration that the Anchor UE shall transmit over PC5 additionally contains the ciphering key with which the content of SL PRS configuration shall be protected.

[0138] Step 4: The Anchor UE transmits the protected SL PRS to the Target UEs in accordance with the SL PRS activation message received from the Server UE in step 3.

[0139] Step 7: After some time the Server UE decides to change the ciphering key for protecting the content of SL PRS configuration and sends to the Anchor UE the SL PRS activation message indicating the new ciphering key.

[0140] Step 8: The Anchor UE transmits the protected SL PRS to the Target UEs in accordance with the SL PRS activation message received from the Server UE in step 7.

[0141] Step 9: The Server UE sends the SL Provide Assistance Data message per groupcast transmission to the Target UEs using full configuration signaling. The SL Provide Assistance Data message contains the SL PRS configuration that has been activated by the Server UE in step 7. The Target UE1 and UE2 release the currently stored content of the SL PRS configuration and apply the new received configuration.

[0142] In alternative or additional implementations, the assumptions and message flow are primarily the same as for the implementation described above with reference to the procedure 800. A difference here, however, is that it can be assumed that the SL Positioning Server UE has been pre-configured by network with a periodic timer for transmitting SLPP messages using delta signaling. As result, the following steps are different compared to the procedure 800 discussion above:

[0143] Step 6: The Server UE initially starts the timer when it sends to Target UEs the initial/first SL Provide Assistance Data message containing the SL PRS configuration.

[0144] Step 11 : Upon expiry of the timer the Server UE sends to Target UEs the SL Provide Assistance Data message containing the SL PRS configuration using full configuration signaling. Furthermore, the Server UE restarts the timer.

[0145] FIG. 9 illustrates an example of a block diagram 900 of a device 902 (e.g., an apparatus) that supports full configuration for SL positioning in accordance with aspects of the present disclosure. The device 902 may be an example of UE 104 as described herein. The device 902 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 902 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 904, a memory 906, a transceiver 908, and an I/O controller 910. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0146] The processor 904, the memory 906, the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 904, the memory 906, the transceiver 908, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0147] In some implementations, the processor 904, the memory 906, the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 904 and the memory 906 coupled with the processor 904 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 904, instructions stored in the memory 906). In the context of UE 104, for example, the transceiver 908 and the processor coupled 904 coupled to the transceiver 908 are configured to cause the UE 104 to perform the various described operations and/or combinations thereof.

[0148] For example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. For instance, the processor 904 and/or the transceiver 908 may be configured as and/or otherwise support a means to transmit, to a second apparatus and via delta signaling, a first message including first SL positioning-related information; generate a second message including second SL positioning-related information; and transmit, to the second apparatus, the second message via full configuration signaling.

[0149] Further, in some implementations, the processor is configured to cause the first apparatus to generate the second message to include a full configuration indicator; the processor is configured to cause the first apparatus to use the full configuration signaling for the second message based at least in part on an event; the event includes one or more of an addition of an apparatus to an existing apparatus group, a usage of a new ciphering key for protecting the second SL positioning-related information, an expiry of a timer, or when an amount of delta of SL positioning- related information is below a threshold amount; the first apparatus includes a SL positioning server device and the second apparatus includes a SL target device; the first message and the second message include respective SL provide assistance data messages.

[0150] Further, in some implementations, the first SL positioning-related information and the second SL positioning-related information include respective SL PRS configuration information; the second apparatus is part of an apparatus group and the processor is configured to cause the first apparatus to: generate the second message based at least in part on a third apparatus joining the apparatus group; and transmit the second message via full configuration signaling to the apparatus group including the second apparatus and the third apparatus; the first message is protected via a first ciphering key and the processor is configured to cause the first apparatus to: generate the second message to be protected via a second ciphering key; transmit the second ciphering key to a fourth apparatus for forwarding to the second apparatus; and transmit the second message protected via the second ciphering key via the full configuration signaling.

[0151] Further, the processor 904 and/or the transceiver 908 may be configured as and/or otherwise support a means to receive, from a second apparatus and via delta signaling, a first message including first SL positioning-related information; receive, from the second apparatus, a second message via full configuration signaling, the second message including second SL positioning-related information; and release, based at least in part on the full configuration signaling, the first SL positioning-related information and apply the second SL positioning-related information.

[0152] Further, in some implementations, the second message includes a full configuration indicator; the first apparatus includes a SL target device and the second apparatus includes a SL positioning server device; the first apparatus is part of an apparatus group, and the second SL positioning-related information includes an indication that a third apparatus joins the apparatus group; the processor is configured to cause the first apparatus to: receive, from a fourth apparatus, a first ciphering key and utilize the first ciphering key to access the first SL positioning-related information; and receive, from the fourth apparatus, a second ciphering key and utilize the second ciphering key to access the second SL positioning-related information.

[0153] In a further example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. The processor 904 and/or the transceiver 908, for instance, may be configured as or otherwise support a means for transmitting, from a first apparatus to a second apparatus and via delta signaling, a first message including first SL positioning-related information; generating a second message including second SL positioning-related information; and transmitting, to the second apparatus, the second message via full configuration signaling. [0154] Further, in some implementations, the processor 904 and/or the transceiver 908 may be configured as or otherwise support a means for generating the second message to include a full configuration indicator; using the full configuration signaling for the second message based at least in part on an event; the event includes one or more of an addition of an apparatus to an existing apparatus group, a usage of a new ciphering key for protecting the second SL positioning-related information, an expiry of a timer, or when an amount of delta of SL positioning-related information is below a threshold amount; the first apparatus includes a SL positioning server device and the second apparatus includes a SL target device; the first message and the second message include respective SL provide assistance data messages; the first SL positioning-related information and the second SL positioning-related information include respective SL PRS configuration information.

[0155] Further, in some implementations, the second apparatus is part of an apparatus group and the method further includes: generating the second message based at least in part on a third apparatus joining the apparatus group; and transmitting the second message via full configuration signaling to the apparatus group including the second apparatus and the third apparatus; the first message is protected via a first ciphering key and the method further includes: generating the second message to be protected via a second ciphering key; transmitting the second ciphering key to a fourth apparatus for forwarding to the second apparatus; and transmitting the second message protected via the second ciphering key via the full configuration signaling.

[0156] In a further example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. The processor 904 and/or the transceiver 908, for instance, may be configured as or otherwise support a means for receiving, at a first apparatus from a second apparatus and via delta signaling, a first message including first SL positioning-related information; receiving, from the second apparatus, a second message via full configuration signaling, the second message including second SL positioning- related information; and releasing, based at least in part on the full configuration signaling, the first SL positioning-related information and apply the second SL positioning-related information.

[0157] Further, in some implementations, the second message includes a full configuration indicator; the first apparatus includes a SL target device and the second apparatus includes a SL positioning server device; the first apparatus is part of an apparatus group, and the second SL positioning-related information includes an indication that a third apparatus joins the apparatus group; further including: receiving, from a fourth apparatus, a first ciphering key and utilize the first ciphering key to access the first SL positioning-related information; and receiving, from the fourth apparatus, a second ciphering key and utilize the second ciphering key to access the second SL positioning-related information.

[0158] The processor 904 of the device 902, such as a UE 104, may support wireless communication in accordance with examples as disclosed herein. The processor 904 includes at least one controller coupled with at least one memory, and the at least one controller is configured to and/or operable to cause the processor to transmit, to a UE and via delta signaling, a first message comprising first sidelink positioning-related information; generate a second message comprising second sidelink positioning-related information; and transmit, to the UE, the second message via full configuration signaling. Further, the at least one controller is configured to and/or operable to cause the processor to receive, from a second apparatus and via delta signaling, a first message comprising first sidelink positioning-related information; receive, from the second apparatus, a second message via full configuration signaling, the second message comprising second sidelink positioning-related information; and release, based at least in part on the full configuration signaling, the first sidelink positioning-related information and apply the second sidelink positioning-related information. Further, the at least one controller is configured to and/or operable to cause the processor to perform any of the various operations described herein, such as with reference to a UE 104 and/or the device 902.

[0159] The processor 904 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 904 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 904. The processor 904 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 906) to cause the device 902 to perform various functions of the present disclosure.

[0160] The memory 906 may include random access memory (RAM) and read-only memory (ROM). The memory 906 may store computer-readable, computer-executable code including instructions that, when executed by the processor 904 cause the device 902 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 904 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 906 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0161] The I/O controller 910 may manage input and output signals for the device 902. The I/O controller 910 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 910 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 910 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 910 may be implemented as part of a processor, such as the processor M08. In some implementations, a user may interact with the device 902 via the I/O controller 910 or via hardware components controlled by the I/O controller 910.

[0162] In some implementations, the device 902 may include a single antenna 912. However, in some other implementations, the device 902 may have more than one antenna 912 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 908 may communicate bi-directionally, via the one or more antennas 912, wired, or wireless links as described herein. For example, the transceiver 908 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 908 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 912 for transmission, and to demodulate packets received from the one or more antennas 912.

[0163] FIG. 10 illustrates a flowchart of a method 1000 that supports full configuration for SL positioning in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a device or its components as described herein. For example, the operations of the method 1000 may be performed by a UE 104 as described with reference to FIGs. 1 through 10. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0164] At 1002, the method may include transmitting, from a first apparatus to a second apparatus and via delta signaling, a first message comprising first SL positioning-related information. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a device as described with reference to FIG. 1.

[0165] At 1004, the method may include generating a second message comprising second SL positioning-related information. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a device as described with reference to FIG. 1.

[0166] At 1006, the method may include transmitting, to the second apparatus, the second message via full configuration signaling. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed by a device as described with reference to FIG. 1.

[0167] FIG. 11 illustrates a flowchart of a method 1100 that supports full configuration for SL positioning in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 104 as described with reference to FIGs. 1 through 10. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0168] At 1102, the method may include generating the second message based at least in part on a third apparatus joining the apparatus group. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a device as described with reference to FIG. 1.

[0169] At 1104, the method may include transmitting the second message via full configuration signaling to the apparatus group including the second apparatus and the third apparatus. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a device as described with reference to FIG. 1.

[0170] FIG. 12 illustrates a flowchart of a method 1200 that supports full configuration for SL positioning in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a device or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 104 as described with reference to FIGs. 1 through 10. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0171] At 1202, the method may include generating the second message to be protected via a second ciphering key. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a device as described with reference to FIG. 1.

[0172] At 1204, the method may include transmitting the second ciphering key to a third apparatus for forwarding to the second apparatus. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a device as described with reference to FIG. 1.

[0173] At 1206, the method may include transmitting the second message protected via the second ciphering key via the full configuration signaling. The operations of 1206 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1206 may be performed by a device as described with reference to FIG. 1.

[0174] FIG. 13 illustrates a flowchart of a method 1300 that supports full configuration for SL positioning in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a device or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 104 as described with reference to FIGs. 1 through 10. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware. [0175] At 1302, the method may include receiving, at a first apparatus from a second apparatus and via delta signaling, a first message comprising first SL positioning-related information. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a device as described with reference to FIG. 1.

[0176] At 1304, the method may include receiving, from the second apparatus, a second message via full configuration signaling, the second message comprising second SL positioning- related information. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a device as described with reference to FIG. 1.

[0177] At 1306, the method may include releasing, based at least in part on the full configuration signaling, the first SL positioning-related information and apply the second SL positioning-related information. The operations of 1306 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1306 may be performed by a device as described with reference to FIG. 1.

[0178] FIG. 14 illustrates a flowchart of a method 1400 that supports full configuration for SL positioning in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a device or its components as described herein. For example, the operations of the method 1400 may be performed by a UE 104 as described with reference to FIGs. 1 through 10. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0179] At 1402, the method may include receiving, from a fourth apparatus, a first ciphering key and utilize the first ciphering key to access the first SL positioning-related information. The operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a device as described with reference to FIG. 1.

[0180] At 1404, the method may include receiving, from the fourth apparatus, a second ciphering key and utilize the second ciphering key to access the second SL positioning-related information. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a device as described with reference to FIG. 1.

[0181] It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0182] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0183] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0184] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0185] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0186] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (e.g., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0187] The terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity, may refer to any portion of a network entity (e.g., a base station, a CU, a DU, a RU) of a RAN communicating with another device (e.g., directly or via one or more other network entities).

[0188] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described example.

[0189] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMS What is claimed is:

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: transmit, to a second apparatus and via delta signaling, a first message comprising first sidelink positioning-related information; generate a second message comprising second sidelink positioning-related information; and transmit, to the second apparatus, the second message via full configuration signaling.

2. The UE of claim 1, wherein the at least one processor is configured to cause the UE to generate the second message to include a full configuration indicator.

3. The UE of claim 1, wherein the at least one processor is configured to cause the UE to use the full configuration signaling for the second message based at least in part on an event.

4. The UE of claim 3, wherein the event comprises one or more of an addition of an apparatus to an existing apparatus group, a usage of a new ciphering key for protecting the second sidelink positioning-related information, an expiry of a timer, or when an amount of delta of sidelink positioning-related information is below a threshold amount.

5. The UE of claim 1 , wherein the UE comprises a sidelink positioning server device and the second apparatus comprises a sidelink target device.

6. The UE of claim 1, wherein the first message and the second message comprise respective sidelink provide assistance data messages.

7. The UE of claim 1 , wherein the first sidelink positioning-related information and the second sidelink positioning-related information comprise respective sidelink positioning reference signal (PRS) configuration information.

8. The UE of claim 1, wherein the second apparatus is part of an apparatus group and wherein the at least one processor is configured to cause the UE to: generate the second message based at least in part on a third apparatus joining the apparatus group; and transmit the second message via full configuration signaling to the apparatus group including the second apparatus and the third apparatus.

9. The UE of claim 1 , wherein the first message is protected via a first ciphering key and wherein the at least one processor is configured to cause the UE to: generate the second message to be protected via a second ciphering key; transmit the second ciphering key to a fourth apparatus for forwarding to the second apparatus; and transmit the second message protected via the second ciphering key via the full configuration signaling.

10. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a second apparatus and via delta signaling, a first message comprising first sidelink positioning-related information; receive, from the second apparatus, a second message via full configuration signaling, the second message comprising second sidelink positioning-related information; and release, based at least in part on the full configuration signaling, the first sidelink positioning-related information and apply the second sidelink positioning-related information.

11. The UE of claim 10, wherein the second message comprises a full configuration indicator.

12. The UE of claim 10, wherein the UE comprises a sidelink target device and the second apparatus comprises a sidelink positioning server device.

13. The UE of claim 10, wherein the UE is part of an apparatus group, and wherein the second sidelink positioning-related information comprises an indication that a third apparatus joins the apparatus group.

14. The UE of claim 10, wherein the at least one processor is configured to cause the UE to: receive, from a fourth apparatus, a first ciphering key and utilize the first ciphering key to access the first sidelink positioning-related information; and receive, from the fourth apparatus, a second ciphering key and utilize the second ciphering key to access the second sidelink positioning-related information.

15. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to a user equipment (UE) and via delta signaling, a first message comprising first sidelink positioning-related information; generate a second message comprising second sidelink positioning-related information; and transmit, to the UE, the second message via full configuration signaling.

16. The processor of claim 15, wherein the at least one controller is configured to cause the processor to generate the second message to include a full configuration indicator.

17. The processor of claim 15, wherein the at least one controller is configured to cause the processor to use the full configuration signaling for the second message based at least in part on an event.

18. The processor of claim 17, wherein the event comprises one or more of an addition of an apparatus to an existing apparatus group, a usage of a new ciphering key for protecting the second sidelink positioning-related information, an expiry of a timer, or when an amount of delta of sidelink positioning-related information is below a threshold amount.

19. The processor of claim 15, wherein the processor comprises a sidelink positioning server device and the UE comprises a sidelink target device.

20. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a second apparatus and via delta signaling, a first message comprising first sidelink positioning-related information; receive, from the second apparatus, a second message via full configuration signaling, the second message comprising second sidelink positioning-related information; and release, based at least in part on the full configuration signaling, the first sidelink positioning-related information and apply the second sidelink positioning-related information.