Side link and bidirectional round trip time positioning

Abstract

A method, system, and computer-readable medium for performing operations for sidelink positioning are disclosed, including transmitting a sidelink positioning reference signal (SL-PRS) to another UE, receiving feedback information generated from the other UE based on the measured signal strength of the transmitted SL-PRS transmission, and configuring an SL-PRS multiplexing group based on the received feedback information.

Description

Background Art

[0001] (Claim of Priority) This application claims priority to U.S. Provisional Application No. 63 / 466,233, filed on May 12, 2023, entitled "SIDELINK AND DOUBLE SIDED RTT Positioning", the entire disclosure of which is incorporated herein by reference.

[0002] A wireless communication network provides an integrated communication platform and telecommunications services to wireless user devices. Exemplary telecommunications services include telephony, data (e.g., voice, audio, and / or video data), messaging, and / or other services. The wireless communication network has a radio access node that exchanges wireless signals with wireless user devices using a wireless network protocol such as those described in various telecommunications standards published by the Third Generation Partnership Project (3GPP). Exemplary wireless communication networks include time division multiple access (TDMA) networks, frequency-division multiple access (FDMA) networks, orthogonal frequency-division multiple access (OFDMA) networks, Long Term Evolution (LTE), and Fifth Generation New Radio (5G NR). The wireless communication network uses technologies such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming, and / or other features to facilitate mobile broadband services.

Summary of the Invention

[0003] One aspect of this disclosure discloses a method for sidelink positioning. In one aspect, the method may include the action of receiving a request from another UE for a sidelink positioning reference signal (SL-PRS) transmission, and the action of transmitting the SL-PRS transmission using any symbol or slot in a shared resource pool that includes one or more physical sidelink shared channel (PSSCH) / physical sidelink feedback channel (PSFCH) transmissions.

[0004] Other embodiments include apparatus, systems, and computer programs for performing the actions of the aforementioned methods.

[0005] This innovative method may include other optional features. For example, in some implementations, the bandwidth of SL-PRS is less than or equal to the bandwidth of the shared resource pool.

[0006] In some implementations, comb-based multiplexing is used in conjunction with SL-PRS TF resources.

[0007] In some implementations, the bandwidth of the SL-PRS is greater than that of the PSSCH.

[0008] In some implementations, comb-based multiplexing is performed using SL-PRS time and frequency (TF) resources.

[0009] In some implementations, transmitting an SL-PRS transmission using any symbol or dedicated slot in a shared resource pool containing one or more PSSCH / PSFCH transmissions may include transmitting an SL-PRS transmission using any symbol or dedicated slot in a shared resource pool containing multiple PSSCH / PSFCH transmissions.

[0010] In some implementations, the SL-PRS bandwidth is larger than the bandwidth of each PSSCH transmission.

[0011] In some implementations, the slots in a shared resource pool are dedicated slots.

[0012] In another innovative aspect of this disclosure, a method for sidelink positioning is disclosed. In one aspect, the method may include: receiving sidelink positioning reference signal (SL-PRS) transmissions from one or more other UEs; measuring the signal strength of each of the received SL-PRS transmissions; and transmitting feedback information to one or more devices based on the measured signal strength of each of the received SL-PRS transmissions.

[0013] Other embodiments include apparatus, systems, and computer programs for performing the actions of the aforementioned methods.

[0014] This innovative method may include other optional features. For example, in some implementations, feedback information is transmitted using sidelink control information (SCI).

[0015] In some implementations, receiving an SL-PRS transmission from one or more other UEs may include receiving an SL-PRS transmission from one other UE.

[0016] In some implementations, the feedback information includes one or more UE identifiers, each corresponding to a UE from which an SL-PRS transmission satisfying a predetermined signal strength threshold was received.

[0017] In some implementations, the UE identifier can include either a UEID or a session ID.

[0018] In some implementations, one or more devices include a Location Management Function (LMF), a Sidelink LMF (SL-LMF), or a Server UE.

[0019] In some implementations, one or more other devices include other UEs.

[0020] In some implementations, the measured signal strength is the reference signal received power (RSRP) strength.

[0021] In some implementations, the measured signal strength is a reference strength signal indicator (RSSI).

[0022] Another innovative aspect of this disclosure discloses another method of sidelink positioning. In one aspect, the method may include transmitting a sidelink positioning reference signal (SL-PRS) transmission to another UE, receiving feedback information generated from the other UE based on the measured signal strength of the transmitted SL-PRS transmission, and configuring an SL-PRS multiplexing group based on the received feedback information.

[0023] Other embodiments include apparatus, systems, and computer programs for performing the actions of the aforementioned methods.

[0024] This innovative method may include other optional features. For example, in some implementations, feedback information is transmitted using sidelink control information (SCI).

[0025] In some implementations, the feedback information includes one or more UE identifiers, each corresponding to a UE that sent an SL-PRS transmission that met a predetermined signal strength threshold.

[0026] In some implementations, the UE identifier can include a UEID or a session ID.

[0027] In some implementations, the measured signal strength is the reference signal received power (RSRP) strength.

[0028] In some implementations, the measured signal strength is the reference signal indicator (RSSI).

[0029] Details of one or more embodiments of these systems and methods are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of these systems and methods will become apparent from the description, the drawings, and the claims.

Brief Description of the Drawings

[0030] [Figure 1] Shows a wireless network according to some implementations.

[0031] [Figure 2] Shows a flowchart of an exemplary method for transmitting SL-PRS using a shared resource pool according to some implementations.

[0032] [Figure 3A] Shows a conceptual diagram of the relative bandwidth used by a physical sidelink shared channel (PSSCH), a physical sidelink shared channel (PSSCH) / physical sidelink feedback channel (PSFCH), and a sidelink positioning reference signal (SL-PRS) for a shared resource for a single PSSCH / PSFCH according to some implementations.

[0033] [Figure 3B]This diagram illustrates the conceptual bandwidth used by the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Shared Channel (PSSCH) / Physical Sidelink Feedback Channel (PSFCH), and Sidelink Positioning Reference Signal (SL-PRS) for shared resources across multiple PSSCH / PSFCH in several implementation configurations.

[0034] [Figure 3C] This diagram shows another conceptual representation of the relative bandwidth used by the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Shared Channel (PSSCH) / Physical Sidelink Feedback Channel (PSFCH), and Sidelink Positioning Reference Signal (SL-PRS) for a single PSSCH / PSFCH shared resource across several implementations.

[0035] [Figure 4] This document shows flowcharts of methods for synchronization and intra-band emission (IBE) interference control performed by RxUE, based on several implementation configurations.

[0036] [Figure 5] This shows flowcharts of methods for synchronization and IBE control performed by TxUE, based on several implementation configurations.

[0037] [Figure 6] The following are flowcharts of typical bidirectional RTT flows for several implementation configurations.

[0038] [Figure 7] The following are flowcharts of a typical two-way RTT with no transmission order restrictions, based on several implementation configurations.

[0039] [Figure 8] This section shows example user equipment (UE) in several implementation forms.

[0040] [Figure 9] Several implementations of an access node are shown as examples. [Modes for carrying out the invention]

[0041] This disclosure generally relates to sidelink and bidirectional round-trip time (RTT) positioning for a shared resource pool. In some implementations, this disclosure provides a multiplexed frame structure for sidelink positioning using a shared resource pool. The solutions provided herein enable methods for handling synchronization and inter-band emission (IBE) interference. Furthermore, the solutions provided herein enable on-demand sidelink positioning reference signal (SL-PRS) transmission and physical layer requirements for SL-PRS transmission. In other implementations, this disclosure provides a method for device positioning using bidirectional RTT. The solutions provided herein enable bidirectional RTT positioning without order restrictions and specify the content of feedback for bidirectional RTT positioning.

[0042] Figure 1 shows several implementations of the wireless network 100. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and base station 104 communicate using a system that supports control for managing the UE 102's access to the network via base station 104.

[0043] In some implementations, the wireless network 100 may be a non-standalone (NSA) network incorporating the Long-Term Evolution (LTE) and 5G New Radio (NR) communication standards as defined by the 3G Partnership Project (3GPP) technical specifications. For example, the wireless network 100 may be an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR dual connectivity (EN-DC) network, or an NR-EUTRA dual connectivity (NE-DC) network. In some other implementations, the wireless network 100 may be a standalone (SA) network incorporating only 5G NR. Furthermore, other types of communication standards are possible, including future 3GPP systems (e.g., Sixth Generation (6G)), Institute of Electrical and Electronics Engineers (IEEE) 802.11 technologies (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11-2007, IEEE 802.11n, IEEE 802.11-2012, IEEE 802.11ac, or other current or future-developed IEEE 802.11 technologies), and IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.). While aspects may be described herein using terms generally related to 5G NR, aspects of this disclosure may apply to other systems, such as systems following 3G, 4G, and / or 5G (e.g., 6G).

[0044] In the wireless network 100, UE 102 and any other UEs in the system may be, for example, machine-type devices such as laptop computers, smartphones, tablet computers, smart meters, or dedicated devices for healthcare, intelligent transport systems, or any other wireless devices. In the network 100, base station 104 provides UE 102 with network connectivity to a wider network (not shown). This connectivity of UE 102 is provided via an air interface 108 within the base station service area provided by base station 104. In some implementations, such a wider network may be a wide-area network operated by a cellular network provider, or it may be the Internet. Each base station service area associated with base station 104 is supported by one or more antennas integrated with base station 104. The service area may be divided into multiple sectors associated with one or more specific antennas. Such sectors may be physically associated with one or more fixed antennas and may be assigned to physical areas using one or more tunable antennas or antenna configurations that are adjustable in a beamforming process used to direct signals to specific sectors.

[0045] UE102 includes a control circuit 110 coupled to a transmitter circuit 112 and a receiver circuit 114. Each of the transmitter circuit 112 and the receiver circuit 114 may be coupled to one or more antennas. The control circuit 110 may include various combinations of application-specific circuits and baseband circuits. The transmitter circuit 112 and the receiver circuit 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuits and / or front-end module (FEM) circuits.

[0046] In various implementations, the transmitter circuit 112, the receiver circuit 114, and the control circuit 110 may be integrated in various ways to implement the operations described herein. The control circuit 110 may be adapted or configured to perform various operations with respect to the UE, such as those described elsewhere in this disclosure.

[0047] Furthermore, the transmitting circuit 112 may transmit using multiple multiplexed uplink physical channels. The multiple uplink physical channels may be multiplexed, for example, with carrier aggregation, according to time division multiplexing (TDM) or frequency division multiplexing (FDM). The transmitting circuit 112 may be configured to receive block data from the control circuit 110 for transmission via the air interface 108.

[0048] Furthermore, the receiving circuit 114 may receive multiple multiplexed downlink physical channels from the air interface 108 and relay the physical channels to the control circuit 110. The multiple downlink physical channels may be multiplexed, for example, with carrier aggregation, by TDM or FDM. The transmitting circuit 112 and the receiving circuit 114 may transmit and receive both structured control data and content data (e.g., messages, images, videos, etc.) within the data blocks carried by the physical channels, respectively.

[0049] Figure 1 also shows base station 104. In some implementations, base station 104 may be a 5G radio access network (RAN), next-generation RAN, E-UTRAN, non-terrestrial cell, or legacy RAN such as UTRAN. As used herein, terms such as "5G RAN" may refer to base station 104 operating on an NR or 5G radio network 100, and terms such as "E-UTRAN" may refer to base station 104 operating on an LTE or 4G radio network 100. UE 102 utilizes connections (or channels) 106A, 106B, each including a physical communication interface or layer.

[0050] The base station 104 circuit may include a control circuit 116 coupled to a transmit circuit 118 and a receive circuit 120. Each of the transmit circuit 118 and the receive circuit 120 may be coupled to one or more antennas that can be used to enable communication via the air interface 108. The transmit circuit 118 and the receive circuit 120 may be adapted to transmit and receive data, respectively, to any UE connected to the base station 104. The receive circuit 120 may receive multiple uplink physical channels from one or more UEs, including UE 102.

[0051] In Figure 1, one or more channels 106A, 106B are shown as air interfaces enabling communicable coupling and may conform to cellular communication protocols such as UMTS protocol, 3GPP LTE protocol, Advanced Long-Term Evolution (LTE-A) protocol, LTE-Based Access to Unlicensed Spectrum (LTE-U), 5G protocol, NR protocol, NR-Based Access to Unlicensed Spectrum (NR-U) protocol, and / or any other communication protocol(s). In implementations, UE102 may directly exchange communication data via the ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Discovery Link Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0052] This disclosure generally relates to sidelink and bidirectional round-trip time (RTT) positioning for shared resource pools. In some implementations, this disclosure provides a multiplexed frame structure for sidelink positioning using a shared resource pool. The solutions provided herein enable methods for handling synchronization and interband radiation (IBE) interference. Furthermore, the solutions provided herein enable on-demand sidelink positioning reference signal (SL-PRS) transmission and physical layer requirements for SL-PRS transmission. In other implementations, this disclosure provides a method for device positioning using bidirectional RTT. The solutions provided herein enable bidirectional RTT positioning without order restrictions and specify the content of feedback for bidirectional RTT positioning.

[0053] Multiplexed frame structure for shared resource pools

[0054] Comb-based multiplexing of SL-PRS from different UEs within a slot for a dedicated resource pool should be supported. The arrangement raises the question of how to support comb-based and TDM multiplexing for a shared resource pool. Furthermore, it raises the question of how synchronization and interband interference should be handled. This disclosure provides several different frame structures for SL-PRS. The frame structure is, for example, where the SL-PRS is multiplexed. For comb-based multiplexing, mechanisms are described to facilitate addressing multiple UEs and mitigate the effects of synchronization loss and interband interference. For TDM, this disclosure describes mechanisms to facilitate addressing multiple UEs.

[0055] In some implementations, SL-PRS resides within any symbol in a shared resource pool. SL-PRS is transmitted within a single shared resource pool, including a single PSSCH / PSFCH transmission. In such implementations, the bandwidth of SL-PRS is less than or equal to the bandwidth of the resource pool. In some implementations, comb-based multiplexing is performed using SL-PRS time and frequency (TF) resources.

[0056] In other implementations, the SL-PRS resides in a dedicated slot within a shared resource pool. The SL-PRS is transmitted within a single shared resource pool, but may span a larger frequency resource than a single PSSCH / PSFCH transmission. In such implementations, the SL-PRS bandwidth can be less than or equal to the PSSCH bandwidth. Alternatively, in such implementations, the SL-PRS bandwidth can be greater than the PSSCH bandwidth. In some implementations, comb-based multiplexing is performed using the SL-PRS TF resource.

[0057] In other implementations, the SL-PRS resides in any symbol or dedicated slot within a set of shared resource pools. The SL-PRS may span frequency resources encompassing multiple independent SL-PSSCH / PSFCH transmissions between multiple pairs of UEs. In such implementations, the bandwidth of the SL-PRS is greater than the bandwidth of each PSSCH.

[0058] Figure 2 shows a flowchart of an exemplary method 200 for sending SL-PRS using a shared resource pool, in several implementation forms. Method 200 is described as being performed by a UE such as UE105 or UE800.

[0059] A UE can initiate the execution of method 200 by receiving a request from another UE for the transmission of a side-link positioning reference signal (SL-PRS) (202).

[0060] The UE can continue executing method 200 by sending an SL-PRS transmission using any symbol or dedicated slot in the shared resource pool that includes one or more physical sidelink shared channel (PSSCH) / physical sidelink feedback channel (PSFCH) transmissions (204).

[0061] In some implementations, the bandwidth of the SL-PRS is less than or equal to the bandwidth of the shared resource pool. An example of this scenario is shown in Figure 300A, where the bandwidth of the SL-PRS 330A is equal to the bandwidth of the shared resource pool in the PSSCH / PSFCH 320A.

[0062] In some implementations, comb-based multiplexing is used in conjunction with SL-PRS TF resources.

[0063] In some implementations, the bandwidth of the SL-PRS is greater than that of the PSSCH. An example of this scenario is shown in Figure 300C of Figure 3C, where the bandwidth of the SL-PRS 330C is shown to be greater than that of the shared resource pool represented in the PSSCH / PSFCH 320C.

[0064] In some implementations, comb-based multiplexing is performed using SL-PRS time and frequency (TF) resources.

[0065] In some implementations, transmitting an SL-PRS transmission using any symbol or dedicated slot in a shared resource pool containing one or more PSSCH / PSFCH transmissions may include the UE transmitting an SL-PRS transmission using any symbol or dedicated slot in a shared resource pool containing multiple PSSCH / PSFCH transmissions.

[0066] In some implementations, the bandwidth of the SL-PRS is greater than the bandwidth of each of the PSSCH transmissions. An example of this scenario is shown in Figures 300B-1 and 300B-2 in Figure 3B, where the bandwidth of the SL-PRS 330B is greater than the bandwidth of each of the PSSCH transmissions 320B-1 and 320B-2.

[0067] COM-based multiplexing

[0068] Some implementations target comb-based multiplexing of SL PRS from different UEs in slots for a shared resource pool. In some examples, comb-based multiplexing of SL PRS from different UEs in slots for a shared resource pool is not supported.

[0069] Alternatively, a second implementation allows for comb-based multiplexing. This second implementation has the need to enable signaling of additional SL PRS sources (one or more) and SL PRS destinations (one or more). In some implementations, this need can be met using a new SCI Stage 2 with S ID / D IDs (one or more) for communication and source IDs (one or more) / destination IDs (one or more) for SL PRS Tx / Rx. In some implementations, communication and positioning S / D are signaled separately (it may be necessary to signal the number of the S / D positioning pair). In other implementations, communication and positioning S / D are signaled together.

[0070] Several implementations provide solutions for managing the effects of synchronization and IBE interference. Regarding synchronization, UEs performing comb-based multiplexing have a common synchronization source. For in-band radiation (IBE) interference and power control, solutions are proposed to ensure that power levels at all receiver UEs are limited to thresholds.

[0071] In some implementations, a common source is used to ensure the same power level. In other implementations, SL-PRS multiplexing groups may be created to ensure that the power difference is below a threshold. In such implementations, each UE may feed back all communication session UEIDs (or source UE IDs or other identifiers) arriving at acceptable power via the Sidelink LTE Positioning Protocol (SL LPP) (e.g., as supporting information) based on the power received from their signals (e.g., their PSSCH transmit / power control). This information may be reported to a multiplexing selector such as an LMF, sidelink LMF, or a UE selected or configured to perform identification (server UE). In the case of comb-based multiplexing between multiple pairs, the multiplexing selector identifies specific UE pairs that can be multiplexed based on the reported feedback to ensure that all received SL PRS are within the threshold.

[0072] Figure 4 shows flowcharts of Method 400 for synchronous and in-band radiated (IBE) interference control performed by an Rx UE in several implementation forms. Method 400 is described as being performed by a UE such as UE105 or UE800.

[0073] A UE can initiate the execution of method 400 by receiving one or more transmissions from one or more other UEs (402).

[0074] The UE can continue the execution of method 400 by measuring the signal strength of each received transmission (404).

[0075] The UE can continue the execution of method 400 by sending feedback information to one or more devices based on the measured signal strength of each received transmission (406).

[0076] In some implementations, one or more transmissions received in step 402 are sidelink positioning reference signal (SL-PRS) transmissions, the signal strength measured in step 404 is the signal strength of each received SL-PRS transmission, and the feedback information sent to one or more devices in step 406 is based on the measured signal strength of each received SL-PRS transmission. In such implementations, the signal strength measured in step 404 may be the reference signal received power (RSRP), reference strength signal indicator (RSSI), or any other power measurement of the received SL-PRS transmission.

[0077] In some implementations, one or more transmissions received in step 402 are PSCCH transmissions, the signal strength measured in step 404 is the signal strength of each of the received PSCCH transmissions, and the feedback information sent to one or more devices in step 406 is based on the measured signal strength of each of the received PSCCH transmissions. In such implementations, the signal strength measured in step 404 may be the reference signal received power (RSRP), reference strength signal indicator (RSSI), or any other power measurement of the received PSCCH transmission.

[0078] In some implementations, one or more transmissions received in step 402 are PSFCH transmissions, the signal strength measured in step 404 is the signal strength of each of the received PSFCH transmissions, and the feedback information sent to one or more devices in step 406 is based on the measured signal strength of each of the received PSFCH transmissions. In such implementations, the signal strength measured in step 404 may be the received power of the PSFCH transmissions.

[0079] In some implementations, the feedback transmission in stage 406 is transmitted using sidelink control information (SCI).

[0080] In some implementations, receiving an SL-PRS transmission from one or more other UEs may include a UE receiving an SL-PRS transmission from one other UE.

[0081] In some implementations, the feedback information includes one or more UEIDs, each of which corresponds to a UEID from which an SL-PRS transmission satisfying a predetermined RSRP threshold was received.

[0082] In some implementations, one or more devices have location management (LMF) capabilities.

[0083] In some implementations, one or more other devices include other UEs.

[0084] Figure 5 shows flowcharts of Method 500 for synchronization and IBE control performed by TxUE in several implementation forms. Method 500 is described as being performed by a UE such as UE105 or UE800.

[0085] One UE can initiate the execution of process 500 by transmitting a sidelink positioning reference signal (SL-PRS) to another UE (502).

[0086] The UE can continue executing process 500 by receiving feedback information from other UEs that is generated based on the measured signal strength of the transmitted SL-PRS transmission (504).

[0087] The UE can continue executing process 500 by configuring an SL-PRS multiplexing group based on the received feedback information (506).

[0088] In some implementations, the measured signal strength is the reference signal received power (RSRP) strength.

[0089] In some implementations, the measured signal intensity is the Reference Strength Signal Indicator (RSSI).

[0090] In some implementations, SL-PRS transmissions are sent using sidelink control information (SCI).

[0091] In some implementations, the feedback information includes one or more UEIDs, each corresponding to the UEID of a UE that sent an SL-PRS transmission that met a predetermined RSRP threshold.

[0092] In some implementations, the UE, which can be comb-based multiplexed, is pre-configured. The network is responsible for ensuring synchronization and power levels.

[0093] Process 500 considers a scenario in which the UE has already sent an SL-PRS transmission. However, in a scenario in which the UE has not yet sent an SL-PRS, the measurement in the feedback information may be based on the measurement of another signal transmitted by the UE, such as PSCCH, PSSCH, PSFCH, CSI-RS, or PT-RS.

[0094] TDM-based redundancy

[0095] Some implementations disclose TDM-based multiplexing of SL-PRS from different UEs in a slot for a shared resource pool. Some implementations do not perform TDM-based multiplexing of SL-PRS from different UEs in a slot for a shared resource pool. Other implementations perform TDM-based multiplexing of SL-PRS from different UEs in a slot for a shared resource pool. To facilitate the latter implementation, updates to addressing are required to enable signaling of SL-PRS sources (one or more) and SL-PRS destinations (one or more). Such updates may be similar to solutions for comb-based multiplexing.

[0096] Unordered two-way RTT

[0097] The move toward SL-PRS-based RX-TX measurements for two-sided round-trip time (RTT) has raised issues regarding how to distinguish between different PRS transmissions for sidelink PRS RX-TX measurements and reporting, and how to provide feedback on the measurements to support both types of two-sided RTT. This disclosure describes the ordering distinction for two-sided RTTs in which implicit and explicit signaling for measurements and feedback indicates the type of two-sided RTT. This specification also describes the feedback for two-sided RTTs in which specific feedback required for either ordered or unordered two-sided RTTs may be shown.

[0098] Figure 6 shows a typical two-way RTT flow diagram 600 for several implementations. Figure 7 shows a general two-way RTT flow diagram 700 without transmission order restrictions for several implementations.

[0099] Considering the flowcharts in Figures 6 and 7, the propagation time between the target UE and the anchor UE can be estimated as follows.

number

[0100] This disclosure provides a solution for distinguishing different PRS transmissions for sidelink PRS RX-TX measurement and reporting.

[0101] Order distinction for bilateral RTT

[0102] In some implementations, signaling may be used to indicate a distinction in measurement types. Measurement types can be explicit or implicit. For example, in some implementations, signaling may be used to configure the UE to use explicit measurement. In such implementations, signaling may be used to explicitly configure the UE to use an SL-RTT configuration that uses (a) two-sided RTT, or (b) two-sided RTT sequence. In other implementations, signaling may be used to configure the user to use implicit measurement. Implicit measurement may involve resource allocation that identifies the number of consecutive SL-PRS transmissions for UE-A. In some implementations, signaling may reserve resources for a response for UE-B.

[0103] In some implementations, signaling may be employed to indicate the type of feedback. The feedback type can be explicit or implicit. In some implementations, for example, explicit feedback may include a flag indicating ordered / out of order. On the other hand, in some implementations, for example, implicit feedback received from the UE after an SL-PRS transmission implicitly indicates a bidirectional RTT order. In some implementations, feedback may include information about a specific SL-PRS resource(s) that implicitly identifies the order. In some implementations, feedback may include timestamps indicating when the SL-PRS was sent and / or received, which implicitly identify the order.

[0104] Examples 1-11 relate to sequential distinction for round-the-clock testing (RTT).

[0105] This disclosure also provides a solution for using feedback measurements to support both bilateral RTT types.

[0106] Feedback for bilateral RTT

[0107] In some implementations, the measurement in a typical case may require reporting T-response A and T-round B from the anchor UE. In the first implementation, the Rx-Tx time difference can be based on the nearest subframes. For example, for feedback, T2-T1, T6-T5; for estimates, TroundA (from T4 and T1), TreplyA (from TroundA, T2-T1, and T4-T3), TreplyB (from T5-T4), and TroundB{(T6-T5)+(T5-T4)+(T4-T3)}. In the second implementation, the Rx-Tx time difference can be based on the actual SL-PRS transmission time. For example, for feedback, T3-T2 (TreplyA) and T6, or T6-T3 (TroundB); for estimates, TroundA (from T4 and T3) and TreplyB (from T5-T4).

[0108] In some implementations, measurements in the unordered case may need to report TreplyA and TreplyB. In the first implementation, the Rx-Tx time difference can be based on the nearest subframes. For example, for feedback, T2-T1 and T6-T5; for estimates, TroundA(T3-T1), TroundB(T3-T5), TreplyA{TroundA-(T3-T4)-T2-T1}, TreplyB{TroundB-(T4-T3)-{T6-T5)}. In the second implementation, the Rx-Tx time difference can be based on the actual SL-PRS transmission time. For example, for feedback, T4-T2(TreplyA) and T4-T6(TreplyB); for estimates, TroundA(from T1 and T3) and TroundB(from T3 and T5).

[0109] Examples 12-13 relate to feedback for bilateral RTT.

[0110] On-demand PRS for SL positioning

[0111] In some implementations, the on-demand SL-PRS transmission procedure allows the transmitting UE, receiving UE, LMF, and / or SL-LMF to control and determine whether or not an SL-PRS is transmitted, and to modify the characteristics of an ongoing SL-PRS transmission. The on-demand SL-PRS transmission procedure can be initiated by the transmitting UE (self-triggered), the receiving UE (triggered by another UE), the LMF (in-coverage), or the SL-LMF (out-of-coverage).

[0112] In some implementations, the transmitting UE and / or receiving UE may initiate on-demand SL-PRS. In some implementations, the transmitting UE, receiving UE and / or LMF (in-coverage) may initiate on-demand SL-PRS. In some implementations, the transmitting UE, receiving UE and / or SL-LMF (out-of-coverage) may initiate on-demand SL-PRS.

[0113] In some implementations, an SL-PRS change may be a predefined SL-PRS configuration having an SL-PRS configuration ID, explicit parameters for the SL-PRS configuration, a request for sending / receiving an SL-PRS, or a request for measurement. For example, in the first implementation, if the LMF is involved (in coverage), the actual SL-PRS change is requested by the LMF, regardless of whether the procedure is initiated by the UE or the LMF. In the second implementation, if the SL-LMF is involved (outside coverage), the actual SL-PRS change is requested by the SL-LMF, regardless of whether the procedure is initiated by the UE or the SL-LMF. In the third implementation, the actual SL-PRS change may be requested by the primary UE, which may be configured (pre-configured) as the primary for on-demand SL-PRS. In the fourth implementation, the actual SL-PRS change may be requested by either UE, i.e., the primary UE or the secondary UE.

[0114] Generally, the overall procedure is as follows: First, information is exchanged via SL-LPP (from SL-LMF to SL-UE(s) or from SL-UE(s) to SL-LMF). For example, SL-PRS configurations are exchanged. This may include, for example, the exchange of identification information for an on-demand SL-PRS primary. In the case of self-triggering, the SL-LPP signal is directed to the UE itself. Next, on-demand PRS requests are exchanged. If initiated by a UE, the UE may request an SL-PRS transmission or a change in SL-PRS transmission characteristics with respect to a predefined PRS configuration ID or explicit PRS configuration parameters. This can be self-triggered or triggered by another UE (primary UE). If initiated by an SL-LMF, the UE takes measurements and changes the PRS transmission characteristics.

[0115] Examples 14-25 relate to on-demand PRS for SL positioning.

[0116] PHY layer requirements for SL-PRS transmission

[0117] In some implementations, a UE may use a PSFCH channel to support UE-A requesting UE-B to transmit an SL-PRS via lower-layer signaling sent by UE-A. In some implementations, a transmitting UE / receiving UE pair may be configured with a PSFCH resource (and sequence) during SL-PRS configuration. According to the first implementation, a single resource is configured for each SL-PRS. The resource may be used for a single request or to turn periodic SL-PRS on / off for semi-persistent operation. Alternatively, according to the second implementation, one or two resources may be configured for each SL-PRS. In this second implementation, if there is one PSFCH resource, it is used to request aperiodic transmission of an SL-PRS. On the other hand, if there are two resources in this second implementation (for periodic SL-PRS), one may be used to initiate an SP transmission and the other may be used to stop a periodic transmission.

[0118] In some implementations, it may be possible for some PRBs within the PSFCH symbol to be omitted. In this case, the UE may be configured (in advance) to use these resources to request that UE-B transmit an SL-PRS. If the UE is scheduled to transmit a PSFCH in response to a PSSCH transmit, the PSFCH may have a higher priority than the PSCCH transmit.

[0119] In some implementations, the UE may use an SL-PRS request signal in the SCI to support UE-A requesting UE-B to send an SL-PRS via lower-layer signaling sent by UE-A. For a dedicated resource pool with a single-stage SCI, the SL-PRS request signal is a field in the SCI. For a shared resource pool with a two-stage SCI, the SL-PRS request signal is a field in SCI stage 2. Sending an SL-PRS in response to a lower-layer request from UE-A is up to the upper layers of UE-B itself. In one implementation, the on-demand SL-PRS transmission procedure may be initiated by the transmitting UE-B (self-triggered).

[0120] In some implementations, the UE may use MAC-CE in PSSCH to support UE-A in requesting UE-B to send SL-PRS via lower-layer signaling sent by UE-A.

[0121] Figure 8 shows exemplary UE800 implementations in several configurations. The UE800 is similar to the UE102 in Figure 1 and may be substantially interchangeable.

[0122] The UE800 can be any mobile or non-mobile computing device, such as mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, pressure sensors, thermometers, motion sensors, accelerometers, inventory sensors, volt / current meters, etc.), video devices (e.g., cameras, video cameras, etc.), wearable devices (e.g., smartwatches), and relaxation IoT devices.

[0123] The UE800 may include a processor 802, an RF interface circuit 804, memory / storage 806, a user interface 808, a sensor 810, a driver circuit 812, a power management integrated circuit (PMIC) 814, one or more antennas 816, and a battery 818. The components of the UE800 may be implemented as an integrated circuit (IC), a part thereof, individual electronic devices or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram in Figure 8 is intended to show an overview of some of the components of the UE800. However, some of the components shown may be omitted, additional components may exist, and different arrangements of the components shown may be used in other implementations.

[0124] The components of the UE800 may be coupled to various other components via one or more interconnectors 820, and one or more interconnectors 820 may represent any type of interface, input / output, (local, system, or expansion) bus, transmission line, trace, optical connection, etc., that enables various circuit components (on common or different chips or chipsets) to interact with each other.

[0125] The processor 802 may include, for example, a baseband processor circuitry (BB) 822A, a central processor unit circuitry (CPU) 822B, and a graphics processor unit circuitry (GPU) 822C. The processor 802 may include any type of circuit or processor circuit that executes or otherwise operates computer executable instructions, such as program code, software modules, or functional processes, from memory / storage 806, to cause the UE800 to perform the operations described herein.

[0126] In some implementations, the baseband processor circuit 822A can access the communication protocol stack 824 in memory / storage 806 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 822A can access the communication protocol stack to perform user plane functions in the physical (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and PDU layer, and control plane functions in the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some implementations, the operation of the PHY layer may be additionally / alternatively performed by components of the RF interface circuit 804. The baseband processor circuit 822A can generate or process baseband signals or waveforms that carry information within a 3GPP-compliant network. In some implementations, the waveform for noise reduction (NR) can be based on cyclic prefix quadrature frequency division multiplexing (OFDM) "CP-OFDM" in the uplink or downlink, and discrete Fourier transform spread OFDM "DFT-S-OFDM" in the uplink.

[0127] The memory / storage 806 may include one or more non-temporary computer-readable media (e.g., a communication protocol stack 824) containing instructions that can be executed by one or more of the processors 802, causing the UE800 to perform the various operations described herein. The memory / storage 806 includes any type of volatile or non-volatile memory that can be distributed throughout the UE800. In some implementations, some of the memory / storage 806 may reside on the processor 802 itself (e.g., L1 and L2 caches), while other memory / storage 806 may be outside the processor 802 but accessible via memory interfaces. The memory / storage 806 may include, but is not limited to, any suitable volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0128] The RF interface circuit 804 may include a transceiver circuit and a radio frequency front module (RFEM) that enable the UE800 to communicate with other devices via a radio access network. The RF interface circuit 804 may include various elements located in the transmit or receive path. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuits, control circuits, and the like.

[0129] In the receiving path, the RFEM receives the radiated signal from the air interface via antenna(s) 816, and subsequently filters and amplifies the signal (using a low-noise amplifier). The signal may also be provided to a receiver of the transceiver, which downconverts the RF signal to a baseband signal, and the baseband signal is provided to the baseband processor of processor 802.

[0130] In the transmission path, the transmitter of the transceiver upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal using a power amplifier before radiating the signal across the air interface via the antenna(s)816. In various implementations, the RF interface circuit(s)804 may be configured to transmit / receive signals in a manner compliant with NR access technology.

[0131] Antenna(s) 816 may include one or more antenna elements for converting electrical signals into radio waves so that they can travel through the air, and for converting received radio waves into electrical signals. The antenna elements may be arranged in one or more antenna panels. Antenna(s) 816 may have omnidirectional, directional, or a combination thereof antenna panels that enable beamforming and multi-input multi-output communications. Antenna(s) 816 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna(s) 816 may have one or more panels designed for a specific frequency band, including the FR1 or FR2 band.

[0132] The user interface 808 includes various input / output (I / O) devices designed to enable user interaction with the UE800. The user interface 808 includes input device circuits and output device circuits. The input device circuits include, among other things, any physical or virtual means for receiving input, including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, and so on. The output device circuits include any physical or virtual means for displaying information, such as sensor readings, actuator positions (one or more), or other similar information, or for conveying information in other ways. The output device circuit may include any number or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary state indicators such as light-emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.), and outputs such as characters, graphics, and multimedia objects are generated or created from the operation of the UE800.

[0133] The sensor 810 may include devices, modules, or subsystems intended to detect events or changes in its environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measuring units including accelerometers, gyroscopes, or magnetometers; micro-electromechanical systems or nano-electromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (e.g., thermistors); pressure sensors; image capture devices (e.g., cameras or lensless apertures); light detection and distance measuring sensors; proximity sensors (e.g., infrared detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices.

[0134] The driver circuit 812 may include software and hardware elements that operate to control specific devices that are incorporated into the UE800, attached to the UE800, or otherwise coupled to the UE800 in a way that allows them to communicate with the UE800. The driver circuit 812 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE800. For example, the driver circuit 812 may include a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface, a sensor driver for acquiring sensor readings from sensor 810 and controlling and allowing access to sensor 810, a driver for acquiring the actuator position of an electromechanical component or for controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0135] The PMIC814 can manage the power supplied to various components of the UE800. In particular, with respect to the processor 802, the PMIC814 can control power selection, voltage scaling, battery charging, or DC-DC conversion.

[0136] In some implementations, the PMIC 814 may control, or may be part of, various power-saving mechanisms of the UE800. The battery 818 may supply power to the UE800, but in some examples, the UE800 may be mounted and deployed in a fixed location, or it may have a power source coupled to a power grid. The battery 818 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, or a lithium-air battery. In some implementations, such as vehicle-based applications, the battery 818 may be a typical automotive lead-acid battery.

[0137] Figure 9 shows exemplary access node 900 (e.g., base station or gNB) in several implementation configurations. The access node 900 is similar to the base station 104 and may be substantially interchangeable. The access node 900 may include a processor 902, an RF interface circuit 904, a core network (CN) interface circuit 906, a memory / storage circuit 908, and one or more antennas 910.

[0138] The components of the access node 900 may be coupled with various other components via one or more interconnectors 912. The processor 902, RF interface circuit 904, memory / storage circuit 908 (including the communication protocol stack 914), antenna(s) 910, and interconnectors 912 may be similar to the elements with similar names shown and described with respect to Figure 8. For example, the processor 902 may include processor circuits such as a baseband processor circuit (BB) 916A, a central processing unit (CPU) 916B, and a graphics processing unit (GPU) 916C.

[0139] The CN interface circuit 906 may provide connectivity to a core network, such as a 5th Generation Core network (5GC), using a 5GC-compliant network interface protocol, such as the Carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to / from the access node 900 via optical fiber or wireless backhaul. The CN interface circuit 906 may include one or more dedicated processors or FPGAs for communication using one or more of the protocols described above. In some implementations, the CN interface circuit 906 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0140] As used herein, terms such as “access node” and “access point” may describe equipment that provides wireless baseband functionality for data connectivity and / or voice connectivity between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). As used herein, terms such as “NG RAN node” may refer to an access node 900 operating on an NR or 5G system (e.g., gNB), and terms such as “E-UTRAN node” may refer to an access node 900 operating on an LTE or 4G system (e.g., eNB). Depending on the implementation, the access node 900 may be implemented as one or more dedicated physical devices, such as a macrocell base station and / or a low-power (LP) base station to provide a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0141] In some implementations, all or part of the access node 900 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be called the CRAN and / or virtual baseband unit pool (vBBUP). In a V2X scenario, the access node 900 may be or may operate as a “roadside unit”. The term “Roadside Unit” or “RSU” may refer to any traffic infrastructure entity used for V2X communication. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, and an RSU implemented in or by a UE may be called a “UE-type RSU”, an RSU implemented in or by an eNB may be called an “eNB-type RSU”, an RSU implemented in or by a gNB may be called a “gNB-type RSU”, and so on.

[0142] For convenience, various components may be described in this specification as performing one or more tasks. Such descriptions should be interpreted as including the phrase “configured to perform.” Descriptions of components configured to perform one or more tasks are expressly intended not to be subject to the interpretation of § 112(f) of the U.S. Patent Act.

[0143] For one or more embodiments, at least one of the components shown in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes, or methods as described in the following Examples section. For example, the baseband circuit described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the embodiments described below. As another example, a circuit associated with a UE, base station, network element, etc., as described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the embodiments described below in the Examples section. [Examples]

[0144] Further exemplary embodiments are provided in the following sections.

[0145] Example 1 includes a UE that receives a signaling configured to indicate a side-link round-trip time (SL-RTT) measurement type, and configuring the UE to implement the SL-RTT measurement type indicated by the received signaling.

[0146] Example 2 includes the fact that the signaling in Example 1 indicates an explicit measurement type.

[0147] Example 3 includes an SL-RTT configuration in which the explicit measurement type of Example 2 includes (a) the use of a two-sided RTT, (b) a sequence of two-sided RTTs, or both.

[0148] Example 4 includes the fact that the signaling in Example 1 indicates an implicit measurement type.

[0149] Example 5 includes the implicit measurement type of Example 4, which includes resource allocation 2 that identifies the number of consecutive SL-PRS transmissions for UE-A.

[0150] Example 6 includes the implicit measurement type of Example 4, which includes reserving resources for the response for UE-B.

[0151] Example 7 includes a UE that receives a signaling configured to indicate an SL-RTT feedback type, and configuring the UE to implement the feedback type indicated by the received signaling.

[0152] Example 8 includes the fact that the signaling in Example 7 exhibits an explicit feedback type.

[0153] Example 9 includes the fact that the explicit feedback type of Example 8 includes a flag indicating whether the inputs are in order or out of order.

[0154] Example 10 includes the fact that the signaling in Example 7 exhibits an implicit feedback type.

[0155] Example 11 includes demonstrating that the implicit feedback type of Example 10 implicitly indicates a two-sided RTT order when feedback is received from the UE after SL-PRS transmission.

[0156] Example 11 includes demonstrating that the implicit feedback type of Example 10 may also include information about a specific SL-PRS resource(s) that identifies the sequence.

[0157] Example 12 includes receiving a bilateral RTT measurement transmission and transmitting feedback based on the received bilateral RTT measurement transmission, wherein the transmitted feedback is the Rx-Tx time difference based on the nearest subframe.

[0158] Example 13 includes receiving a bilateral RTT measurement transmission and transmitting feedback based on the received bilateral RTT measurement transmission, wherein the transmitted feedback is the Rx-Tx time difference based on the actual SL-PRS transmission time.

[0159] Example 14 includes the first device deciding to initiate the transmission of one or more SL-PRS transmissions, and the first device transmitting one or more SL-PRS transmissions.

[0160] Example 15 includes the first device determining that the characteristics of one or more SL-PRS transmissions in progress will change, and modifying the characteristics of the SL-PRS transmissions in progress based on the determined characteristic change.

[0161] Example 16 includes Example 15, wherein the first device is a transmitting UE, a receiving UE, an LMF, or an SL-LMG.

[0162] Embodiment 14 includes: a first device receiving a transmission from a second device indicating that one or more SL-PRS transmissions should be initiated; the first device deciding to initiate the transmission of one or more SL-PRS transmissions based on the received transmission; and the first device transmitting one or more SL-PRS transmissions.

[0163] Example 15 includes Example 14, wherein the first device is a receiving UE.

[0164] Example 16 includes Example 14, wherein the second device is a transmitting UE, LMF, or SL-LMG.

[0165] Example 17 includes Example 14 and further comprises: a first device receiving a transmission from a second device indicating a change in the characteristics of one or more SL-PRS transmissions in progress; and the first device modifying the characteristics of the SL-PRS transmissions in progress based on the determined characteristic change.

[0166] Example 18 includes Example 17, wherein the first device is a receiving UE.

[0167] Example 19 includes Example 17, wherein the second device is a transmitting UE, LMF, or SL-LMG.

[0168] Example 20 includes Example 15 or Example 17, and the changes to the SLPRS transmission may be changes in a predefined SL-PRS configuration.

[0169] Example 21 includes Example 20, and the predefined SL-PRS configuration may include an SL-PRS configuration ID, explicit parameters for the SL-PRS configuration, a request for transmitting / receiving SL-PRS, or a request for measurement.

[0170] Example 22 may include one or more of Examples 14-21, and the actual SL-PRS change is required by the LMF, regardless of whether the procedure is initiated by the UE or the LMF, if the LMF is involved.

[0171] Example 23 may include one or more of Examples 14-21, and actual SL-PRS changes may be required by the SL-LMF, regardless of whether the procedure is initiated by the UE or the SL-LMF, if the SL-LMF is involved.

[0172] Example 24 may include one or more of Examples 14-21, where the actual SL-PRS change may be requested by the primary UE, and the primary UE may be configured (in advance) as an on-demand SL-PRS primary.

[0173] Example 25 may include one or more of Examples 14-21, and the actual SL-PRS change may be requested by one of the UEs (e.g., primary UE or secondary UE).

[0174] Example 26 may include UE-A sending a request to UE-B in the PSFCH requesting UE-B to transmit SL-PRS via lower-layer signaling, and UE-A receiving the transmission of SL-PRS from UE-B via lower-layer signaling.

[0175] Example 27 may include Example 26, where a single resource is configured for each SL-PRS.

[0176] Example 28 may include Example 27, where resource usage may be for a single request to turn a periodic SL-PRS on / off for semi-persistent operation.

[0177] Example 29 may include Example 26, in which one or two resources are configured per SL-PRS.

[0178] Example 30 may include Example 29, in which one PSFCH resource is used to request periodic transmission of SL-PRS.

[0179] Example 31 may include Example 29, in which two PSFCH resources are used, one of which may be used to initiate periodic SL-PRS transmission and the other of which may be used to stop periodic SL-PRS transmission.

[0180] Example 32 may include Example 26, in which UE-A determines that one or more physical resource blocks (PRBs) in the PSFCH are not being utilized, and UE-A sends a request to UE-B to send an SL-PRS using the unused PRBs in the PSFCH.

[0181] Example 33 may include one or more of Examples 26 to 32, and if UE-A is scheduled to transmit a PSFCH in response to a PSSCH transmission, the PSFCH may have a higher priority than the PSCCH transmission.

[0182] Example 34 may include Example 26, in which a request for SL-PRS is sent via SCI.

[0183] Example 35 may include Example 34, where the SCI is a single-stage SCI and the SL-PRS request signal is a field in the SCI.

[0184] Example 36 may include Example 34, wherein the SCI is a two-stage SCI, and the SL-PRS request signal is the field in SCI stage 2.

[0185] Example 37 may include Example 26, in which a request for SL-PRS is sent using MAC-CE in PSSCH.

[0186] Example 38 may include Example 37, and the UE identifier may include a UEID or a session ID.

[0187] Example 39 may include Example 35, wherein the signal strength measured is the reference signal received power (RSRP) strength.

[0188] Example 40 may include Example 35, where the measured signal intensity is the Reference Signal Indicator (RSSI).

[0189] Example 41 is a method for sidelink positioning, comprising: transmitting a sidelink positioning reference signal (SL-PRS) transmission to another UE; receiving feedback information generated from the other UE based on the measured signal strength of the transmitted SL-PRS transmission; and configuring an SL-PRS multiplexing group based on the received feedback information.

[0190] Example 42 is Method 41, in which feedback information is transmitted using Sidelink Control Information (SCI).

[0191] Example 43 is the method of claim 41, wherein the feedback information includes one or more UE identifiers, each of which corresponds to a UE that has transmitted an SL-PRS transmission satisfying a predetermined signal intensity threshold.

[0192] Example 44 is the method of claim 43, wherein the UE identifier may include a UEID or a session ID.

[0193] Example 45 is the method of claim 41, wherein the signal strength measured is the reference signal received power (RSRP) strength.

[0194] Example 46 is the method of claim 41, wherein the signal intensity measured is a reference signal indicator (RSSI).

[0195] Embodiment 47 is a method performed by a user device (UE), comprising determining a time difference between a sidelink reception time TUE-RX and a transmission time TUE-TX, wherein TUE-RX includes a timing for the reception of sidelink subframe #i, and TUE-TX is the transmission timing of the UE's sidelink positioning reference signal for sidelink subframe #j, or the transmission timing of the sidelink subframe #j that is temporally closest to the received sidelink subframe #i.

[0196] Any of the embodiments described above may be combined with any other embodiment (or combination of embodiments) unless otherwise specified. The above descriptions of one or more implementation forms are illustrative and illustrative, but are not intended to be exhaustive or to limit the scope of embodiments to the exact forms disclosed. Modifications and variations are possible based on the above teachings or can be learned from the practice of various embodiments.

[0197] Although the embodiments described above are in considerable detail, numerous variations and modifications will become apparent to those skilled in the art if the above disclosure is fully understood. The following claims are intended to be construed as encompassing all such variations and modifications.

[0198] It should be fully understood that the use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

Claims

1. One or more processors comprising circuits that execute one or more instructions, wherein when the one or more instructions are executed, the one or more processors are made to perform an operation, and the operation is Receiving a request from another UE for the transmission of a sidelink positioning reference signal (SL-PRS), Transmitting an SL-PRS transmission using any symbol or slot in a shared resource pool that includes one or more physical sidelink shared channel (PSSCH) transmissions, physical sidelink feedback channel (PSFCH) transmissions, or both, including, One or more processors.

2. The operation according to claim 1, wherein the bandwidth of the SL-PRS is less than or equal to the bandwidth of the shared resource pool.

3. The operation according to claim 1, wherein comb-based multiplexing is used in conjunction with SL-PRS T-F resources.

4. The operation according to claim 1, wherein the bandwidth of the SL-PRS is greater than the bandwidth of the PSSCH.

5. The operation according to claim 1, wherein comb-based multiplexing is performed using SL-PRS time and frequency (T-F) resources.

6. Sending an SL-PRS transmission using any symbol or dedicated slot in a shared resource pool that includes one or more PSSCH / PSFCH transmissions is possible. This includes transmitting an SL-PRS transmission using any symbol or dedicated slot in a shared resource pool that includes multiple PSSCH / PSFCH transmissions, The operation described in claim 1.

7. The operation according to claim 6, wherein the bandwidth of the SL-PRS is greater than the bandwidth of each of the PSSCH transmissions.

8. The operation according to claim 1, wherein the slot of the shared resource pool is a dedicated slot.

9. A method for sidelink positioning, Receiving a request from another UE for the transmission of a sidelink positioning reference signal (SL-PRS), Transmitting an SL-PRS transmission using any symbol or slot in a shared resource pool that includes one or more physical sidelink shared channel (PSSCH) / physical sidelink feedback channel (PSFCH) transmissions, Methods that include...

10. The method according to claim 9, wherein the bandwidth of the SL-PRS is less than or equal to the bandwidth of the shared resource pool.

11. The method according to claim 9, wherein comb-based multiplexing is used in conjunction with SL-PRS T-F resources.

12. The method according to claim 9, wherein the bandwidth of the SL-PRS is greater than the bandwidth of the PSSCH.

13. The method according to claim 9, wherein comb-based multiplexing is performed using SL-PRS time and frequency (T-F) resources.

14. Sending an SL-PRS transmission using any symbol or dedicated slot in a shared resource pool that includes one or more PSSCH / PSFCH transmissions is possible. This includes transmitting an SL-PRS transmission using any symbol or dedicated slot in a shared resource pool that includes multiple PSSCH / PSFCH transmissions, The method according to claim 9.

15. The method according to claim 14, wherein the bandwidth of the SL-PRS is greater than the bandwidth of each of the PSSCH transmissions.

16. The method according to claim 9, wherein the slot of the shared resource pool is a dedicated slot.

17. One or more processors comprising circuits that execute one or more instructions, wherein when the one or more instructions are executed, the one or more processors are made to perform an operation, and the operation is Receiving a Sidelink Positioning Reference Signal (SL-PRS) transmission from one or more other UEs, To measure the signal strength of each of the received SL-PRS transmissions, Based on the measured signal strength of each of the received SL-PRS transmissions, feedback information is transmitted to one or more devices. One or more processors, including [the specified component].

18. The operation according to claim 17, wherein the feedback information is transmitted using side link control information (SCI).

19. Receiving an SL-PRS transmission from one or more other UEs is possible. Including receiving an SL-PRS transmission from one other UE, The operation described in claim 17.

20. The operation according to claim 17, wherein the feedback information includes one or more UE identifiers, and each of the one or more UE identifiers corresponds to a UE from which an SL-PRS transmission satisfying a predetermined signal intensity threshold was received.

21. The operation according to claim 20, wherein the UE identifier may include a UEID or a session ID.

22. The operation according to claim 17, wherein one or more of the devices include a location management function (LMF), a sidelink LMF (SL-LMF), or a server UE.

23. The operation according to claim 17, wherein one or more other devices include the other UEs.

24. The operation according to claim 17, wherein the measured signal strength is the reference signal received power (RSRP) strength.

25. The operation according to claim 17, wherein the measured signal intensity is a reference intensity signal indicator (RSSI).

26. A method for sidelink positioning, Receiving a Sidelink Positioning Reference Signal (SL-PRS) transmission from one or more other UEs, To measure the signal strength of each of the received SL-PRS transmissions, Based on the measured signal strength of each of the received SL-PRS transmissions, feedback information is transmitted to one or more devices. Methods that include...

27. The method according to claim 26, wherein the feedback information is transmitted using side link control information (SCI).

28. Receiving an SL-PRS transmission from one or more other UEs is possible. Including receiving an SL-PRS transmission from one other UE, The method according to claim 26.

29. The method according to claim 26, wherein the feedback information includes one or more UE identifiers, and each of the one or more UE identifiers corresponds to a UE from which an SL-PRS transmission satisfying a predetermined signal intensity threshold was received.

30. The method according to claim 29, wherein the UE identifier can include a UEID or a session ID.

31. The method according to claim 26, wherein one or more of the devices include a location management function (LMF), a sidelink LMF (SL-LMF), or a server UE.

32. The method according to claim 26, wherein one or more other devices include the other UE.

33. The method according to claim 26, wherein the measured signal intensity is the reference signal received power (RSRP) intensity.

34. The method according to claim 26, wherein the measured signal intensity is a reference intensity signal indicator (RSSI).

35. One or more processors comprising circuits that execute one or more instructions, wherein when the one or more instructions are executed, the one or more processors are made to perform an operation, and the operation is Transmitting the Sidelink Positioning Reference Signal (SL-PRS) to another UE, Receiving feedback information generated from other UEs based on the measured signal strength of the transmitted SL-PRS transmission, Based on the received feedback information, an SL-PRS multiplexing group is configured, One or more processors, including [the specified component].

36. The operation according to claim 35, wherein the feedback information is transmitted using side link control information (SCI).

37. The operation according to claim 35, wherein the feedback information includes one or more UE identifiers, and each of the one or more UE identifiers corresponds to a UE that has transmitted an SL-PRS transmission that satisfies a predetermined signal intensity threshold.

38. The operation according to claim 37, wherein the UE identifier may include a UEID or a session ID.

39. The operation according to claim 35, wherein the measured signal strength is the reference signal received power (RSRP) strength.

40. The operation according to claim 35, wherein the measured signal intensity is a reference signal indicator (RSSI).

41. A method for sidelink positioning, Transmitting the Sidelink Positioning Reference Signal (SL-PRS) to another UE, Receiving feedback information generated from other UEs based on the measured signal strength of the transmitted SL-PRS transmission, Based on the received feedback information, an SL-PRS multiplexing group is configured, Methods that include...

42. The method according to claim 41, wherein the feedback information is transmitted using side link control information (SCI).

43. The method according to claim 41, wherein the feedback information includes one or more UE identifiers, and each of the one or more UE identifiers corresponds to a UE that has transmitted an SL-PRS transmission satisfying a predetermined signal intensity threshold.

44. The method according to claim 43, wherein the UE identifier can include a UEID or a session ID.

45. The method according to claim 41, wherein the measured signal intensity is the reference signal received power (RSRP) intensity.

46. The method according to claim 41, wherein the measured signal intensity is a reference signal indicator (RSSI).

47. A method performed by a user device (UE), This includes determining the time difference between the sidelink reception time TUE-RX and the transmission time TUE-TX. TUE-RX includes timing for receiving sidelink subframe #i, TUE-TX The transmission timing of the sidelink subframe #j of the sidelink positioning reference signal of the aforementioned UE, or The transmission timing of sidelink subframe #j which is temporally closest to the received sidelink subframe #i, One of them is method.

Images