Systems and methods for sidelink positioning enhancement signaling
By introducing a flexible SL-PRS resource allocation and congestion control mechanism into side-link positioning, the problems of insufficient resource allocation and ineffective congestion control in existing technologies are solved, achieving more efficient and accurate positioning results.
Patent Information
- Application Number
- CN202380096978.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-04-07
- Publication Date
- 2025-11-11
AI Technical Summary
In existing technologies, the side-link positioning process suffers from insufficient flexibility in resource allocation and ineffective congestion control, resulting in limited positioning accuracy and efficiency.
By introducing flexibility in SL-PRS resource allocation granularity, including allocation based on time slots and sub-channels, and combining congestion control parameters and inter-UE coordination mechanisms, the transmission and reception process of SL-PRS is optimized, supporting multiple positioning methods such as RTT and TDOA.
It improves the accuracy and efficiency of sidelink positioning, enhances resource utilization, reduces congestion, and improves the flexibility and reliability of the positioning process.
Smart Images

Figure CN120937422A_ABST
Abstract
Description
Technical Field
[0001] This disclosure generally relates to wireless communication, and more specifically, to side link communication. Background Technology
[0002] In fifth-generation mobile network systems (5GC), sidelinks are a key technology in new air interface (NR) systems. Sidelink characteristics can include positioning processes to determine various aspects of sidelink communication, such as resource allocation, location, measurement, and reporting. Summary of the Invention
[0003] The exemplary arrangements disclosed herein are intended to address problems related to one or more issues existing in the prior art, and provide additional features that will become apparent when taken in conjunction with the accompanying drawings and the following detailed description. According to various arrangements, exemplary systems, methods, apparatuses, and computer program products are disclosed herein. However, it should be understood that these arrangements are presented by way of example and not as limiting, and that various modifications can be made to the disclosed arrangements while remaining within the scope of this disclosure, as will be apparent to those skilled in the art upon reading this disclosure.
[0004] In some configurations, a side link positioning reference signal (SL-PRS) configuration can be received. A first wireless communication device can receive the SL-PRS configuration. The first wireless communication device can determine SL-PRS transmission parameters based on congestion control parameters. The first wireless communication device can transmit the SL-PRS to a second wireless communication device using inter-user equipment (UE) coordination (IUC) information, wherein the second wireless communication device can measure the SL-PRS during a measurement period.
[0005] In some configurations, the SL-PRS can be received. A second wireless communication device can receive the SL-PRS from the first wireless communication device using IUC information. The second wireless communication device can measure the SL-PRS during a measurement period, wherein the first wireless communication device can receive the SL-PRS configuration and determine the SL-PRS transmission parameters based on congestion control parameters.
[0006] The above and other aspects and their implementations are described in more detail in the accompanying drawings, description and claims. Attached Figure Description
[0007] Various exemplary arrangements of this solution are described in detail below with reference to the accompanying drawings. The drawings are provided for illustrative purposes only and depict only exemplary arrangements of this solution to facilitate the reader's understanding. Therefore, the drawings should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of illustration.
[0008] Figure 1 An example cellular communication system based on some arrangement is shown.
[0009] Figure 2 A block diagram of an example base station and an example user equipment assembly based on some arrangements is shown.
[0010] Figure 3 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0011] Figure 4 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0012] Figure 5 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0013] Figure 6 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0014] Figure 7 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0015] Figure 8 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0016] Figure 9 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0017] Figure 10 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0018] Figure 11 This is a schematic diagram illustrating an example side-link configuration based on some arrangements.
[0019] Figure 12 This is a schematic diagram illustrating example side link configurations according to various arrangements.
[0020] Figure 13 This is a schematic diagram illustrating example wireless communication according to various arrangements.
[0021] Figure 14 This is a schematic diagram illustrating example wireless communication according to various arrangements.
[0022] Figure 15 This is a schematic diagram illustrating example wireless communication according to various arrangements.
[0023] Figure 16 This is a schematic diagram illustrating example wireless communication according to various arrangements.
[0024] Figure 17 This is a schematic diagram illustrating example wireless communication according to various arrangements.
[0025] Figure 18 This is a schematic diagram illustrating example wireless communication systems according to various arrangements.
[0026] Figure 19 This is a flowchart illustrating example methods for enhancing lateral link positioning according to various arrangements.
[0027] Figure 20 This is a flowchart illustrating example methods for enhancing lateral link positioning according to various arrangements. Detailed Implementation
[0028] Various exemplary arrangements of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to make and use this solution. It will be apparent to those skilled in the art that, upon reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of this solution. Therefore, this solution is not limited to the exemplary arrangements and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.
[0029] In wireless communication systems supporting sidelink communication, wireless devices can communicate with each other. As part of the sidelink communication process, the wireless communication system can support Sidelink Positioning Reference Signal (SL-PRS), measurement and reporting of sidelink (SL) positioning considering various positioning methods (e.g., round-trip time (RTT), time difference of arrival (TDOA), angle-based positioning methods), and SL-PRS resource allocation (considering both dedicated and shared resource pools for SL-PRS, and both resource allocation scheme 1 and scheme 2). For SL communication, the time granularity is the time slot, and the frequency granularity is the sub-channel. SL-PRS resources and / or SL-PRS resource sets can be defined and used as the resource allocation granularity. In some cases, SL-PRS sequence configuration, congestion control for SL positioning, and inter-UE coordination (IUC) mechanisms can be designed based on the granularity of resource allocation. The arrangements disclosed herein provide enhancements (e.g., additions, updates, and changes) to signaling used for sidelink positioning.
[0030] Figure 1 An example wireless communication system 100 according to an implementation of this disclosure is shown, in which the techniques disclosed herein can be implemented. In the following discussion, the wireless communication system 100 can implement any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as system 100. Such an example system 100 includes a BS 102 and a UE 104 capable of communicating with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within the respective geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one BS operating on its allocated bandwidth to provide sufficient radio coverage to its intended users.
[0031] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are generally described as non-limiting examples of "communication nodes" capable of practicing the methods disclosed herein. Depending on various implementations of this scheme, such communication nodes can have wireless and / or wired communication capabilities.
[0032] In some implementations, the wireless communication system 100 may support MIMO communication. For example, MIMO is a key technology in New Radio (NR) systems. MIMO can function in systems such as Frequency Division Duplex (FDD) and Time Division Duplex (TDD). MIMO technology can utilize reporting mechanisms (e.g., CSI) to support communication. CSI reports can include various types, sections, groups, and fields. The techniques described herein can provide enhancements to various aspects of CSI reporting and the reporting process. For example, a wireless communication device may receive multiple reference signals and configuration parameters from a network. The wireless communication device may determine a CSI report based on the multiple reference signals and configuration parameters, wherein the CSI report includes CSI section 1 and CSI section 2. The wireless communication device may report the CSI report to the network. In some cases, the reporting process may include one or more of the following: configuration parameters can be configured to enable two or more CQIs in the CSI report; the reference signals are aperiodic or semi-persistent; and each of the following: CSI window length, DD basic unit size, offset between two CSI reference signal (CSI-RS) resources, and length of the DD basic vector is greater than or equal to a threshold. Alternatively or additionally, the wireless communication device may send a User Equipment (UE) Capability Report to the network, indicating the number of CQI reports supported by the wireless communication device, where the number is a positive integer. Among various other uses, the wireless communication system may implement a codebook to further support CQI reporting.
[0033] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some implementations of this scheme is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative implementation, as described above, system 200 can be used in applications such as... Figure 1 The wireless communication environment 100 is a wireless communication environment in which communication (e.g., transmission and reception) data symbols are used.
[0034] System 200 typically includes a base station (BS) 202 and a user interface (UE) 204. BS 202 includes a base station (BS) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a UE transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.
[0035] System 200 may also include, in addition to Figure 2 Any number of modules other than those shown. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the implementations disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functionality. Whether such functionality is implemented as hardware, firmware, or software depends on the specific application and design constraints imposed on the system as a whole. Those skilled in the art can implement such functionality in a manner suitable for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.
[0036] According to some implementations, UE transceiver 230 may be referred to herein as uplink transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to antenna 232. A duplex switch (not shown) may selectively couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, according to some implementations, BS transceiver 210 may be referred herein as "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to antenna 212. A downlink duplex switch may selectively couple the downlink transmitter or receiver to downlink antenna 212 in a time-duplex manner. The operation of the two transceiver modules 210 and 230 can be coordinated in time such that the uplink receiver circuitry is coupled to downlink antenna 232 so that transmissions via wireless transmission link 250 are received while the downlink transmitter is coupled to downlink antenna 212. In some implementations, there is tight time synchronization with minimal protection time between changes in the duplex direction.
[0037] UE transceiver 230 and BS transceiver 210 are configured to communicate via radio data communication link 250 and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative implementations, UE transceiver 210 and BS transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G and 6G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and related protocols. Rather, UE transceiver 230 and BS transceiver 210 can be configured to support optional or additional radio data communication protocols, including future standards or variations thereof.
[0038] Depending on the implementation, for example, BS 202 can be an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some implementations, UE 204 can be various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 can be implemented or implemented using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof for performing the functions described herein. In this way, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.
[0039] Furthermore, the methods described in conjunction with the implementations disclosed herein can be implemented directly in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Memory modules 216 and 234 can be implemented as RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some implementations, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230 respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.
[0040] Network communication module 218 typically refers to the hardware, software, firmware, processing logic, and / or other components of BS 202 that enable bidirectional communication between BS transceiver 210 and other network components and communication nodes configured to communicate with BS 202. For example, network communication module 218 may be configured to support Internet or WiMAX services. In a typical deployment (but not limited to), network communication module 218 provides an 802.3 Ethernet interface, enabling BS transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). The terms “configured for,” “configured as,” and variations thereof, used herein for a particular operation or function, refer to devices, components, circuits, structures, machines, signals, etc., physically constructed, programmed, formatted, and / or arranged to perform a particular operation or function.
[0041] Figure 3 This is a schematic diagram illustrating example side-link configuration 300 according to various arrangements. Side-link configuration 300 may include SL bandwidth portion (BWP) 302, receive (Rx) pool 304, transmit (Tx) pool 306 for a first scheme (e.g., scheme 1), Tx pool 308 for a second scheme (e.g., scheme 2), exceptional Tx pool 310, SL-PRS resource set list 312, SL-PRS resource list 314, and physical side-link control channel (PSCCH) configuration 316.
[0042] Some wireless communication systems supporting sidelinks can use the PSCCH / Physical Sidelink Shared Channel (PSSCH). For PSCCH / PSSCH resource allocation in SL communication, the time granularity can be slot-based, and subchannels can be defined as PSSCH frequency resource units, where the size of the subchannel can be configured per resource pool. The SL channel busy rate (CBR) and SL channel occupancy rate (CR) for SL congestion control can both be defined based on subchannel busy indication or subchannel occupancy rate. However, for SL positioning, the SL-PRS allocation granularity can apply slot-based and subchannel-based SL-PRS resource allocation, or sub-slot-based SL-PRS resource allocation, or allocation based solely on SL-PRS resources. If a different resource allocation granularity than that used for SL communication is applied, corresponding SL-PRS configurations / indicators can be designed, including congestion control and IUC for SL-PRS.
[0043] Support for lateral link positioning in the NR system includes at least three aspects: the design of the SL-PRS; the measurement and reporting of SL positioning considering various positioning methods (e.g., RTT, TDOA, angle-based positioning methods); and resource allocation for SL-PRS (e.g., considering both dedicated resource pools and shared resource pools for SL-PRS, and both resource allocation scheme 1 and scheme 2). Regarding SL-PRS resource allocation, both scheme 1 (e.g., a network-centric operational SL-PRS resource allocation scheme) and scheme 2 (e.g., a UE-autonomous SL-PRS resource allocation scheme) are introduced to support SL positioning / ranging.
[0044] In some cases, wireless communication equipment may include a UE. The UE may be a vehicle UE, a pedestrian UE, a roadside unit (RSU), a positioning reference unit (PRU), or any UE supporting vehicle-to-everything (V2X) services and / or lateral link communication. The UE may or may not have a known location. For descriptive purposes, SL-PRS IUC may represent inter-UE coordination for lateral link positioning.
[0045] In some implementations, the sidelink configuration 300 can support SL-PRS configuration and resource indication. For example, the UE can be configured by a higher layer to use one or more resource pools for SL positioning. The resource pool used for SL positioning (e.g., the SL-PRS resource pool) can be a dedicated resource pool for SL-PRS or a shared resource pool with SL communication. The SL-PRS resource pool can be used to transmit or receive SL-PRS and can be associated with SL-PRS resource allocation scheme 1 or SL-PRS resource allocation scheme 2.
[0046] In the time and frequency domains, an SL-PRS resource pool can be interpreted as a set of time and frequency resources available for SL-PRS transmission / reception. In some cases, this set of time and frequency resources can be used for corresponding PSCCH / PSSCH / PSFCH transmission / reception. The SL-PRS resource pool configuration is pre-configured or configured via Radio Resource Control (RRC) signaling from higher-layer signaling from another UE (e.g., a Side Link Positioning Protocol (SLPP)) or Location Management Function (LMF) (e.g., an LTE Positioning Protocol (LPP)) or gNB. For example, this configuration might indicate that a bandwidth and a comb size are expected for all SL-PRS resources in an SL-PRS resource pool.
[0047] Unlike SL communication, where PSSCH resource allocation is time-slot-based and frequency-slot-based, SL-PRS is a reference signal and similar to other reference signals (e.g., downlink (DL)-PRS). SL-PRS can be configured and allocated to UEs based on SL-PRS resources. SL-PRS resources from different UEs can be multiplexed at either a comb-based or time-division multiplexing (TDM) level. For an SL-PRS resource pool, one or more indicators can be introduced. For example, various indicators may include permitted / supported indicators, which may include: comb-based multiplexing for SL-PRS resources from different UEs only; time-division multiplexing (TDM)-based multiplexing for SL-PRS resources from different UEs only; a combination of comb-based and TDM-based multiplexing for SL-PRS resources from different UEs; and / or configured indicators, which may include: comb-based multiplexing for SL-PRS resources from different UEs only; TDM-based multiplexing for SL-PRS resources from different UEs only; and / or a combination of comb-based and TDM-based multiplexing for SL-PRS resources from different UEs. The techniques disclosed herein can support SL-PRS configuration and SL-PRS resource allocation / indication.
[0048] In the first example, higher-level aspects can be supported. Each SL-PRS resource pool can include one or more SL-PRS resource sets, wherein each SL-PRS resource set consists of one or more SL-PRS resources. Within an SL-PRS resource pool, each SL-PRS resource or SL-PRS resource set can be associated with a PSCCH / sideline link control information (SCI) configuration (e.g., the configuration of the corresponding SCI for the SL-PRS resource or resource set). Each SL-PRS resource or SL-PRS resource set can be configured with an identifier (ID) (e.g., SL-PRS resource ID, SL-PRS resource set ID).
[0049] For example, such as Figure 3 As shown, one or more SL-PRS resource pools are configured (pre-configured) within the SL BWP 302 of the carrier. Each UE can be configured with M Rx SL-PRS resource pools 304 (e.g., for reception), N Tx SL-PRS resource pools 306 (e.g., for transmission) for Scheme 1, N Tx SL-PRS resource pools 308 for Scheme 2, and an exceptional L Tx SL-PRS resource pool 310. Each SL-PRS resource configuration can be associated with a PSCCH / SCI configuration 316. This configuration can include the time resources and / or frequency resources of the PSCCH / SCI (e.g., lists 312 and 314). These configurations can include the time interval between the PSCCH / SCI and the associated SL-PRS resources, the start symbol, and the number of symbols in the PSCCH / SCI.
[0050] refer to Figure 4 (A schematic diagram of example side-link configuration 400 according to various arrangements is shown.) Each SL-PRS resource set configuration can be associated with a PSCCH / SCI configuration 416. Configuration 416 may include indications of the time resources and / or frequency resources of the PSCCH / SCI. Configuration 416 may include the time slot between the PSCCH / SCI and the associated SL-PRS resource set, the start symbol, and the number of symbols for the PSCCH / SCI. Similar to... Figure 3 , Figure 4 It may include SL BWP 402, Rx pool 404, Tx pool of scheme 1 406, Tx pool of scheme 2 408, exception Tx pool 410, SL-PRS resource set list 412, SL-PRS resource list 414 and PSCCH configuration 416.
[0051] Figure 5 This is a schematic diagram illustrating example side-link configurations 500 according to various arrangements. Side-link configuration 500 may include an SL BWP 502, an Rx pool 504, a Tx pool 506 for Scheme 1, a Tx pool 508 for Scheme 2, an exceptional Tx pool 510, an SL-PRS resource list 514, and a PSCCH configuration 516.
[0052] In the second example, higher-level aspects can be supported. Some beam-related functions of the SL may not yet be established, and the SCI can be used to indicate time-domain configurations (e.g., time resource allocation, resource reservation periods). In some cases, an SL-PRS resource set may not be introduced. For example, each SL-PRS resource pool may include one or more SL-PRS resources (e.g., Listing 514) without an SL-PRS resource set configuration. Each SL-PRS resource can be associated with a PSCCH configuration (e.g., the configuration of the SCI corresponding to the respective SL-PRS resource).
[0053] Figure 6 This is a schematic diagram illustrating example sidelink configuration 600 according to various arrangements. Sidelink configuration 600 may include SL BWP 602, Rx pool 604, Tx pool 606 for scheme 1, Tx pool 608 for scheme 2, exceptional Tx pool 610, SL-PRS resource set list 612, and PSCCH configuration 614.
[0054] In the third example, higher-level aspects can be supported. The SL-PRS resource pool can include PSCCH configuration and SL-PRS configuration, wherein the SL-PRS configuration (e.g., configuration 614) can include a list of SL-PRS resources or SL-PRS resource sets (e.g., list 612). For the SL-PRS configuration in the resource pool, the configuration can include the (minimum) time interval between the SL-PRS and the associated PSCCH, the resource block (RB) set (e.g., the bandwidth of the resource pool may be different from the bandwidth of the SL-RS), and / or the SL-PRS period.
[0055] Each SL-PRS resource or resource set configuration may include one or more parameters. For example, parameters may include UEID (e.g., indicating which UE uses the corresponding SL-PRS resource / resource set configuration), SL-PRS bandwidth, comb size, SL-PRS resource set ID, SL-PRS periodicity of periodic SL-PRS, resource set level slot offset, SL-PRS resource repetition factor, time interval between two repetition instances of an SL-PRS resource, number of symbols for each SL-PRS resource within a slot, mute option, SL-PRS resource power, SL-PRS resource ID, SL-PRS sequence ID, comb size and RE offset, SL-PRS resource level slot offset, symbol offset, SL-PRS QCL information, and / or SL-PRS resource priority subset, SL PRS resource frequency location and bandwidth, SCS, resource type (e.g., periodic / semi-persistent / aperiodic SL PRS), and priority (priority of SL PRS resource / SLPRS resource set or priority of SL-PRS transmission).
[0056] In some cases, SL-PRS auxiliary data may include SL-PRS resources configured for one or more UEs. For example, in SL-TDOA, a UE or LMF may indicate information about the SL-PRS resource configurations for multiple anchor UEs to a target UE.
[0057] In some examples, lower-level aspects can be supported. Resource pool configurations can be higher-level signaling and / or lower-level signaling (e.g., SCI, SL Media Access Control (MAC) control element (CE)) and can be used to reserve / indicate one or more SL-PRS resources / configurations. It can support one or more of the following: An SCI indicates one or more SL-PRS resource IDs; an SCI indicates one or more SL-PRS resource set IDs (e.g., an SCI triggers / reserves / indicates an SL-PRS resource set consisting of multiple SL-PRS resources, or an SCI triggers / reserves / indicates more than one SL-PRS resource); an SCI indicates an SL-PRS resource pool ID; an SCI indicates a resource pool ID and an SL-PRS resource ID; an SCI indicates an SL-PRS resource set ID and an SL-PRS resource pool ID; an SCI indicates a resource pool ID, an SL-PRS resource set ID, and an SL-PRS resource ID; an SCI indicates the time and frequency resource allocation of SL-PRS (e.g., the frequency range indicated in the SCI can be equal to or less than the SL-PRS bandwidth configured in the SL-PRS resource pool); and / or an SCI indicates the comb size, slot offset, symbol offset, number of symbols, frequency location, number of RBs, and periodicity of one or more SL-PRS resources. An SCI can be a single-level SCI, a first-level SCI, or a second-level SCI.
[0058] For an SCI indicating an SL-PRS resource pool ID, if SL-PRS resource 1 in SL-PRS resource pool 1 is the same as SL-PRS resource 3 in SL-PRS resource pool 2, then if the SCI only indicates that the resource ID is equal to 1, the RxUE may have difficulty determining the information configured for resource 1 without knowing the resource pool ID. In some cases, when the SCI indicates an SL-PRS resource pool ID, different UEs may have different understandings / interpretations of the same SL-PRS resource pool ID. To ensure consistent understanding among UEs, the UE or LMF can provide multiple SL-PRS resource pool configurations for each UE via SLPP or LPP signaling. The mentioned multiple UEs can participate in a single positioning session.
[0059] For SL-PRS bandwidth configuration, at least one of the following options can be supported. The first option is that the SL-PRS bandwidth configuration can be indicated in the SCI. For dedicated or shared resource pools, the bandwidth can be equal to or less than the resource pool's bandwidth. (For example, for shared resource pools, if they transmit in the same time slot, the bandwidth is the same as the PSSCH bandwidth). The second option is that the SL-PRS bandwidth depends on the pool-level configuration (e.g., SL-ResourcePool can include SL-PSSCH-config / SL-PSCCH-config / SL-PSFCH-config and SL-PRS-Config). The SL-PRS bandwidth can be one of SL-PRS-Config, and one or more parameters (e.g., SL-PRS priority, SL-PRS power control) can be included in the SL-PRS. The third option is that the SL-PRS bandwidth depends on the resource pool configuration and the SCI indication (e.g., common / cross-frequency resources). In this case, the SCI can indicate the SL PRS resource ID, where the SL PRS resource is configured in the resource pool, and the bandwidth is still indicated at a higher level. In some cases, the following can contribute to the flexibility of SL-PRS bandwidth configuration: a) Similar to the bandwidth of DL-PRS configured for each Positioning Frequency Layer (PFL), the SL-PRS bandwidth can be configured for each dedicated / shared resource pool. In other words, the SL-PRS bandwidth is the same as the bandwidth of the resource pool. The UE can be (pre-)configured with multiple resource pools to ensure that SL-PRS with varying bandwidths can be transmitted. b) To increase configuration flexibility, the SL-PRS bandwidth can be equal to or less than the bandwidth of the resource pool. For example, bandwidth is a parameter configured for each SL PRS resource. For shared resource pools, the SL-PRS bandwidth can be indicated in a new Level 2 SCI (e.g., an SCI different from another SCI, such as SCI 2-D), or a reused Level 2 SCI. The new or reused SCI can include the SL-PRS bandwidth or include an identifier for the SL-PRS resource. If the lower layer indicates the SL-PRS bandwidth, the flexibility of SL-PRS configuration can be increased.
[0060] Figure 7 This is a schematic diagram illustrating an example side-link configuration 700 according to various arrangements. Configuration 700 may include a timeslot 702, which includes a resource 704 (e.g., SL-PRS resource) associated with a control channel 706 (e.g., PSCCH).
[0061] In some cases, SL-PRS sequences can be supported. For example, a sequence of SL-PRS (e.g., pseudo-random) r(m) can be generated according to the following formula:
[0062]
[0063] Where c(i) is a pseudo-random sequence, and its initialization function is designed as c init This is a key factor in the generation of SL-PRS sequences. The pseudo-random sequence c(i) of SL-PRS can be initialized according to the following formula:
[0064]
[0065] Adding a high-order offset to align with the sequence design of DL-PRS and enabling multiplexing between SL-PRS and SL CSI-RS can bring technical advantages. The pseudo-random sequence c(i) of SL-PRS can be initialized according to the following formula:
[0066]
[0067] To generate SL-PRS sequence ID The configuration can support one or more options. These options can include: (1) the SL-PRS sequence ID is a parameter configured by the higher layer; (2) for the SCI associated with the SL-PRS, the SL-PRS sequence ID is associated with the CRC; (3) the SL-PRS sequence ID is associated with the UEID information. If the SL-PRS sequence ID is a parameter configured by the higher layer, the SL-PRS sequence ID can be configured for each SL-PRS resource in the resource pool configuration. For example, the SL-PRS sequence ID can be configured for each SL-PRS resource, for multiple SL-PRS resources, or for each set of SL-PRS resources. Alternatively, the SL-PRS sequence ID can be configured for each UE. Sequence ID related information can be pre-configured in the resource pool for the UE or carried separately in the SCI. The sequence ID indicated in the SCI is a subset of the sequence IDs (pre-)configured in the higher layer. For example, the value range of the SL-PRS sequence ID is 0-4095. If the higher layers (LMF via LPP, UE via SLPP, gNB via RRC) configure four SL-PRS sequence IDs, the SCI can use only two bits to indicate which sequence ID to use among these four. By using this method, UE privacy can be protected and reliability increased.
[0068] If an SCI triggers / reserves / indicates an SL-PRS resource (e.g., reference...) Figure 7 Furthermore, since the SL-PRS sequence ID is based on a 12-bit representation of the CRC of the PSCCH associated with the SL-PRS, each SL-PRS resource 704 can be associated with a PSCCH 706.
[0069] refer to Figure 8 (For example, a diagram showing an example side-link configuration 800 according to various arrangements) A single SCI 804 can trigger / reserve / indicate an SL-PRS resource set 802 consisting of multiple SL-PRS resources (e.g., an SL-PRS resource set 802 consisting of four SL-PRS resources 806, 808, 810, and 812), or a single SCI 804 can trigger / reserve / indicate more than one SL-PRS resource. In this case, different SL-PRS resources 806, 808, 810, and 812 can be triggered by the same SCI 804 sharing the same sequence ID if the SL-PRS sequence ID is based on a 12-bit representation of the CRC of the PSCCH associated with the SL-PRS. To ensure that different SL-PRS resources 806, 808, 810 and 812 share different SL-PRS sequence IDs, SCI 804 can indicate ID offsets to ensure that each SL-PRS resource has a unique sequence ID (e.g., different SL-PRS resources reserved by SCI use different sequence ID offsets).
[0070] For example, based on SCI 804 associated with an SL-PRS transport, if the sequence ID is n, then the sequence ID of SL-PRS resource 806 is "n+offset0", the sequence ID of SL-PRS resource 808 is "n+offset1", the sequence ID of SL-PRS resource 810 is "n+offset2", and the sequence ID of SL-PRS resource 812 is "n+offset3". If m+offset > 4095, then (m+offset) mod 2 can be used. 12 Alternatively, higher-layer signaling (e.g., RRC, SLPP, LPP) can be used to indicate the sequence ID offset for each SL-PRS resource. The final SL-PRS sequence ID can be based on the PSCCH and the corresponding CRC of the ID offset indicated by higher layers, which can increase UE privacy. The techniques described in this paper can ensure that different SL-PRS resources share different SL-PRS sequence IDs, thereby increasing interference randomization and sequence correlation properties between SL-PRS resources of multiple UEs.
[0071] Figure 9 This is a schematic diagram illustrating example sidelink configurations 900 according to various arrangements. Sidelink configurations 900 may include SCIs 902, 904, 906, and 908, as well as various resource modes, including SL-PRS 910, 912, 914, and 916.
[0072] In some cases, configuration 900 can support congestion control for SL positioning. A congestion control mechanism for SL-PRS can be introduced, supporting the Quality of Service (QoS) of SL positioning (e.g., SL-PRS Resource Allocation Scheme 2). For example, during the UE SL-PRS resource selection process, the UE can measure the SL-PRS Channel Busy Rate (CBR). Combining the CBR measurement results with the SL-PRS transmission priority, the corresponding transmission parameters of SL-PRS can be further determined or adjusted. SL positioning QoS parameters may include horizontal accuracy, vertical accuracy, vertical request, response time, accuracy with respect to distance or direction, SL-PRS priority, SL-PRS Resource Allocation Scheme 2 selection window size, retransmission time, minimum required communication range, and congestion control parameters. QoS parameters can be QoS requirements sent to the UE via RRC from the gNB, via LPP from the LMF, or via SLPP from another UE (e.g., a server UE), or QoS parameters for sidelink positioning QoS flows. The UE can transmit QoS parameters for sidelink positioning QoS flows to another UE, the gNB, or the LMF.
[0073] In some cases, SL-PRS CBR can be described. SL-PRS congestion control (e.g., congestion control parameters) can help adjust / determine SL-PRS transmission parameters based on channel busyness and SL-PRS transmission priority. For example, SL-PRS channel occupancy rate (CR) and SL-PRS CBR are both parameters used for congestion control. SL-PRS CBR can define the channel busy rate (e.g., based on Reference Received Power (RSRP) and Received Signal Strength Indicator (RSSI)) within a configured (pre-configured) time window, while SL-PRS CR can define the channel occupancy rate for an SL-PRS transmission. If the UE is configured with an indicator CR... SL-PRS,Limit The higher-level parameters are obtained, and the SL-PRS is transmitted. Then, the UE can ensure various restrictions on any priority value k of the SL-PRS according to the following formula (the lower the priority value k, the higher the priority):
[0074]
[0075] Among them, CR SL-PRS (i) is the CR evaluated within the time window / period of an SL-PRS transmission with priority i (e.g., priority can be indicated by SCI), and CR SL-PRS,Limit(k) corresponds to the higher-layer parameters associated with priority k and the CBR range, which includes the SL-PRS CBR measured with another time window / period. For example, if the UE is configured with SL-PRS-CR-limit and transmits SL-PRS in slot N, the UE can ensure various limits, where CR is evaluated in slot nN within window (M1) and CBR is evaluated in slot nN within window (M2).
[0076] The definition of the SL-PRS CBR for a dedicated SL-PRS resource pool can differ from that for a shared resource pool. Generally, regardless of whether it's a dedicated or shared resource pool, the SCI is used to reserve / trigger / indicate SL-PRS resources. Relationships can exist between the SCI and associated SL-PRS resources (e.g., one SCI resource / configuration is associated with one SL-PRS resource, or one SCI is associated with multiple SL-PRS resources), and the SCI can be located at a different time position than the SL-PRS (e.g., time slot, symbol). SL-PRS CR and SL-PRS CBR can be based on PSCCH / SCI or SL-PRS, or both, where PSCCH / SCI is associated with the SL-PRS transport. In this scenario, one or more of the following can be supported for SL positioning congestion control: evaluating the CR for SL positioning based on SL-PRS; evaluating the CR for SL positioning based on PSCCH / SCI if each SL-PRS transmission is associated with SCI / PSCCH; evaluating the CR for SL positioning based on both PSCCH / SCI and SL-PRS (e.g., one or more of the following examples can be supported: CR is the maximum CR between the CR evaluated based on PSCCH / SCI and the CR evaluated based on SL-PRS. Or CR is the CR evaluated based on PSCCH / SCI). The CR is the average or weighted average of the CR evaluated based on SL-PRS. The weighting factor can be defined by higher-level signaling (e.g., the factor can be configured for each SL-PRS resource pool via RRC signaling, or until pre-configured, or via LPP signaling or SLPP signaling). Alternatively, the CR is the minimum CR between the CR evaluated based on PSCCH / SCI and the CR evaluated based on SL-PRS; if SL-PRS, PSCCH, and PSSCH are all in the same resource pool, the CR used for SL positioning is evaluated based on PSCCH / PSSCH; based on SL... RSSI measurements of PRS are used to measure the CBR for SL positioning; RSSI measurements based on SCI / PSCCH are used to measure the CBR for SL positioning; RSSI measurements based on SL PRS and SCI / PSCCH are used to measure the CBR for SL positioning (e.g., one or more of the following examples may be supported: CBR is the maximum CBR between the CBR evaluated based on PSCCH / SCI and the CBR evaluated based on SL-PRS. Or CBR is the average or weighted average of the CBR evaluated based on PSCCH / SCI and the CBR evaluated based on SL-PRS. The weighting factor may be defined by higher-level signaling (e.g., the factor may be configured for each SL-PRS resource pool via RRC signaling, or until pre-configured, or via LPP signaling or via SLPP signaling).Alternatively, the CBR may be the minimum CBR between the CBR assessed based on PSCCH / SCI and the CBR assessed based on SL-PRS; and / or the CBR for SL positioning may be measured based on RSSI measurements of PSCCH / PSSCH.
[0077] For example, if the PSCCH / SCI and SL-PRS have a one-to-one, one-to-many, or many-to-one mapping relationship, and the SL-PRS and its corresponding PSCCH / SCI are transmitted in the same time slot, then measuring the channel busy rate of the PSCCH can be similar to measuring the channel busy rate of the SL-PRS. CR and CBR based on PSCCH / SCI can provide accuracy and reduce complexity compared to calculating CR and CBR for both SL-PRS and PSCCH / SCI.
[0078] In some cases, dedicated resource pools for SL-PRS can be supported. The definitions of SL-PRS CBR and CR can be associated with the granularity of SL-PRS resource allocation and the SL-PRS resource configuration within the SL-PRS resource pool (e.g., SL-PRS CBR is associated with the number of SL-PRS resources and the comb size). For example, if the SL-PRS resource allocation time granularity is per time slot and the frequency granularity is per sub-channel, another approach could include defining SL-PRS CR and SL-PRS CBR based on the occupancy / partiality of sub-channels across multiple time slots. If the SL-PRS resource allocation granularity is per SL-PRS resource and the sub-channels are not defined in a dedicated SL-PRS resource pool, defining SL-PRS CR or CBR based on sub-channels can be difficult. In one example, the definitions of CR and CBR can be associated with the SL-PRS resource configuration within the SL-PRS resource pool (e.g., whether the bandwidth and comb pattern of the SL-PRS resources in the resource pool are the same or different). It can support the mapping relationship between SL-PRS transmission parameters, SL-PRS CBR range, and SL-PRS transmission priority.
[0079] In the first embodiment, refer to Figure 9 The bandwidth and comb pattern of SL-PRS resources in a dedicated SL-PRS resource pool can be the same, and comb-based multiplexing of SL-PRS from different UEs can be applied.
[0080] If the bandwidth and comb pattern of SL-PRS resources in a dedicated SL-PRS resource pool are the same, and comb-based multiplexing of SL-PRS from different UEs is only allowed / supported in the dedicated SL-PRS resource pool, then the definition and configuration of SL-PRS CR and SL-PRS CBR are associated with the number of occupied SL-PRS resources and the comb size. Alternatively, the definition and configuration of SL-PRS CR and SL-PRS CBR are associated with the number of occupied comb offsets, SL-PRS sequence IDs, or the number of occupied PSCCH / SCIs, or with PSCCH / SCIs and SL-PRS.
[0081] In some cases, for CR SL positioning with an evaluation time period / window, the CR window size depends on a higher-layer (pre-)configuration. For example, the CR time window size can be configured via RRC signaling based on the SL-PRS resource pool. The CR time window size can also be configured for each SL-PRS resource, each SL-PRS transmission priority, or each SL-PRS comb size. The CR time window can also be configured by the UE via SLPP signaling, or by the LMF via LPP signaling. The CR window size can also be related to the SL-PRS sensing window size and / or selection window size and / or SL-PRS periodicity and / or SL-PRS resource reservation period. Or more specifically, the CR window size can also be related to the maximum number of SL-PRS sensing window sizes and / or the maximum number of selection window sizes.
[0082] In some cases, the CR for SL positioning can be evaluated for each transport, for each SL-PRS resource, or the CR can be associated with an SCI (e.g., if an SCI reserves one or more SL-PRS resources, the CR can be evaluated for one or more SL-PRS resources).
[0083] In some cases, the CR for SL positioning can be calculated according to SL-PRS priority. For example, the CR for positioning can be associated with the number of SL-PRS resources. The CR for SL positioning can be defined as the total number of SL-PRS resources used for its transmission (used or anticipated) divided by the total number of SL-PRS resources configured in the transmission pool within the CR time window. The CR for positioning can also be associated with the number of transmission opportunities for SL-PRS resources. If an SL-PRS resource has a repetitive characteristic, and therefore an SL-PRS resource can have multiple transmission opportunities, then the number of SL-PRS resources can be replaced by the number of SL-PRS resource opportunities. (Reference) Figure 9Channel capacity can be correlated with the SL-PRS comb size. The evaluation of CR can also be correlated with the SL-PRS comb size. For example, if the comb size is 4, comb-based multiplexing can allow up to 4 UEs to multiplex (assuming the number of symbols in the 4 SL-PRS resources 910, 912, 914, and 916 is the same). If the comb size is 6, it may be possible to multiplex 6 SL-PRS resources (not shown). If the number of symbols within the time slots used for SL-PRS resources is flexibly configured, the CR used for SL positioning is also correlated with the number of symbols in each SL-PRS resource.
[0084] In some cases, CBR for SL positioning can be supported. The CBR window size depends on the higher-layer (pre-)configuration for the evaluation time period / window. For example, the CBR time window size can be configured for each SL-PRS resource pool via Radio Resource Control (RRC) signaling. The CBR time window size can also be configured for each SL-PRS resource, each SL-PRS transmission priority, or each SL-PRS comb size. The CBR time window can also be configured by the UE via SLPP signaling, or by the LMF via LPP signaling.
[0085] The CBR window size can also be related to the sensing window size, the SL-PRS selection window size, the SL-PRS periodicity, and / or the SL-PRS resource reservation period. The CBR window size can also be related to the maximum number of SL-PRS sensing window sizes and / or the maximum number of selection window sizes.
[0086] In some cases, the CBR used for SL positioning can be associated with the portion of SL-PRS resources occupied by its signal strength (e.g., SL-PRS RSSI) that exceeds a threshold. For example, SL-PRS RSSI can be defined as the linear average of the total received power (in W) observed in the configured SL-PRS resources within an OFDM symbol of a time slot. Accordingly, SL-PRS CBR can be defined as the portion of SL-PRS resources in the SL-PRS resource pool where the SL-PRS RSSI measured by the UE exceeds a (pre-)configured threshold.
[0087] For example, SL-PRS RSSI can be defined as the linear average of the total received power (in W) observed in the configured PSCCH resources within the OFDM symbols of a time slot. Correspondingly, SL-PRS CBR can be defined as the portion of the PSCCH resources in the SL-PRS resource pool whose SL-PRS RSSI measured by the UE exceeds a (pre-)configured threshold. (Reference) Figure 9If SCI1902, SCI2904, SCI3906, and SCI4908 are busy and occupied, the corresponding SL-PRS resources 910, SL-PRS resources 912, SL-PRS resources 914, and SL-PRS resources 916 may also be occupied. Therefore, the UE may experience difficulties transmitting SL-PRS in this resource pool (e.g., at least at this time). In some cases, the SL-PRS RSSI threshold is as high as the higher-layer (pre-)configured level.
[0088] In some cases, congestion control-related SL-PRS transmission parameters can be supported. The mapping between congestion control-related SL-PRS transmission parameters and / or SL-PRS transmission parameters and CBR measurements / SL-PRS priorities depends on higher-layer (pre-)configuration. Higher-layer signaling can be RRC signaling, MAC CE, SLPP between UEs, LMF, and LPP between UEs. The determination of congestion control-related SL-PRS transmission parameters is associated with the definition of CR and CBR used for SL positioning. In a first example, if the definition of CR and CBR used for SL positioning is associated with the amount of SL-PRS resources, then the SL-PRS transmission parameters should include an indication of the SL-PRS resources containing a comb offset. In a second example, if the definition of CR and CBR used for SL positioning is associated with the comb size of the SL-PRS resources, then the SL-PRS transmission parameters should include an indication of the SL-PRS comb size. In a third example, if the definition of CR and CBR used for SL positioning is associated with PSCCH, then the SL-PRS transmission parameters should include an indication of the PSCCH resources. In the fourth example, if the definitions of the CR and CBR used for SL positioning are associated with the SL-PRS sequence ID, then the SL-PRS transmission parameters should include an indication of the SL-PRS sequence ID. In the fifth example, the SL-PRS transmission parameters include the maximum transmission power of the SL-PRS.
[0089] Figure 10 This is a schematic diagram illustrating example side-link configuration 1000 according to various arrangements. Configuration 1000 may include various SCIs 1002, 1004, 1006 and 1008 and various SL-PRS 1010, 1012, 1014 and 1016.
[0090] In the second embodiment, SL-PRS resources with the same bandwidth / comb size but different number of symbols are reused. Figure 10 The time slot can support the space / capacity of 2 SL-PRS resources, with a comb size of 4 and a symbol count of 4. Therefore, in order to accurately measure the channel busy state, the CR / CBR definition for SL positioning can be accurate to the symbol level and / or resource level.
[0091] Figure 11 This is a schematic diagram illustrating an example side-link configuration 1100 according to some arrangements. Configuration 1100 may include various SCIs 1102, 1104, 1106 and 1108 and various SL-PRS 1110, 1112, 1114 and 1116.
[0092] In the third embodiment, the bandwidth and comb pattern of SL-PRS resources in a dedicated SL-PRS resource pool can be the same (e.g., TDM-based multiplexing of SL-PRS from different UEs). If the bandwidth and comb pattern of SL-PRS resources in a dedicated SL-PRS resource pool are the same, and only TDM-based multiplexing of SL-PRS from different UEs is allowed / supported in the dedicated SL-PRS resource pool, then the definition and configuration of SL-PRS CR and SL-PRS CBR are associated with the number of SL-PRS resources occupied and the number of symbols per SL-PRS resource.
[0093] Alternatively, the definition and configuration of SL-PRS CR and SL-PRS CBR may be associated with the amount of PSCCH resources occupied, or the definition and configuration of each of SL-PRS CR and SL-PRS CBR may be associated with both the amount of PSCCH resources occupied and the corresponding reserved SL-PRS resources, or the definition and configuration of SL-PRS CR and SL-PRS CBR may be associated with the amount of comb offsets or SL-PRS sequence IDs occupied.
[0094] In some examples, the CR for SL positioning is evaluated for each transport or for each SL-PRS resource, or the CR for positioning is associated with an SCI (e.g., if an SCI reserves one or more SL-PRS resources, the CR is evaluated for one or more SL-PRS resources). In some examples, the CR for SL positioning can be calculated according to SL-PRS priority.
[0095] In some examples, the CR used for positioning is associated with the number of SL-PRS resources. In the first example, the CR used for SL positioning can be defined as the total number of SL-PRS resources (used or anticipated) used for its transmission divided by the total number of SL-PRS resources configured in the transmission pool within the CR time window. In the second example, the CR used for positioning is also associated with the number of transmission opportunities for SL-PRS resources. If an SL-PRS resource has a repeating characteristic, and therefore an SL-PRS resource can have multiple transmission opportunities, then the number of SL-PRS resources can be replaced by the number of SL-PRS resource opportunities. For any example, such as Figure 11As shown, channel capacity is closely related to the number of SL-PRS symbols within a time slot, and the evaluation of CR is associated with the number of symbols in the SL-PRS resource. For example, if the number of symbols is 2, TDM-based multiplexing will allow 4 UEs to multiplex. On the other hand, if the number of symbols is 8, only 1 SL-PRS resource (e.g., any one of SL-PRS 1110, 1112, 1114, or 1116) can be allowed in a time slot. For example, the SL-PRS CR evaluated in time slot n is defined as the total number of symbols used for its transmission in time slot [na, n-1] and authorized in time slot [n, n+b] divided by the total number of symbols configured in the SL-PRS transmission configuration on [na, n+b].
[0096] In some cases, CBR for SL positioning is supported. CBR for SL positioning can be associated with the portion of SL-PRS resources occupied where the signal strength exceeds a threshold. In the first example, SL-PRS RSSI can be defined as the linear average of the total received power (in W) observed in the configured SL-PRS resources within the OFDM symbols of a time slot. Accordingly, SL-PRS CBR can be defined as the portion of SL-PRS resources in the SL-PRS resource pool where the SL-PRS RSSI measured by the UE exceeds a (pre-)configured threshold.
[0097] In the second example, SL-PRS RSSI can be defined as the linear average of the total received power (in W) observed in the configured PSCCH resources within the OFDM symbols of a time slot. Correspondingly, SL-PRS CBR can be defined as the portion of the PSCCH resources in the SL-PRS resource pool whose SL-PRS RSSI measured by the UE exceeds a (pre-)configured threshold. Figure 11 As shown, if SCI 11102, SCI 21104, SCI 31106, and SCI 41108 are busy and occupied, the corresponding SL-PRS resources 1110, SL-PRS resources 1112, SL-PRS resources 1114, and SL-PRS resources 1116 will also be occupied, and the UE may encounter difficulties transmitting SL-PRS in this resource pool (e.g., at least at this time). In some cases, the SL-PRS RSSI threshold is as high as the higher-layer (pre-)configured level.
[0098] In some cases, SL-PRS transmission parameters related to congestion control are associated with one of the SL-PRS resource configurations (e.g., number of symbols) or the maximum transmission power of the SL-PRS.
[0099] Figure 12This is a schematic diagram illustrating example side-link configuration 1200 according to various arrangements. Configuration 1200 may include various SCIs 1202, 1204, 1206, and 1208, and various SL-PRSs 1210, 1212, 1214, and 1216. Configuration 1200 can support SL-PRS resource multiplexing with different bandwidths and symbol numbers.
[0100] In the third implementation, flexible configuration and resource indication of bandwidth and comb size associated with SL-PRS are supported. If SL-PRS bandwidth and comb size are flexibly configured in the SL-PRS resource pool, or if there is only one comb size and bandwidth in the SL-PRS resource pool, SCI can be used to indicate bandwidth that is different from the bandwidth defined in the SL-PRS resource pool.
[0101] In the first example, the definition and configuration of SL-PRS CR and SL-PRS CBR can be associated with the frequency domain mode (e.g., the number of busy / occupied REs) and time domain mode (e.g., the number of busy / occupied symbols) of the SL-PRS resource. For example, SL-PRS CR and / or CBR can be defined based on each comb size. For instance, if a UE needs to transmit two SL-PRS resources (one with comb size 2 and one with comb size 4), the UE can measure the CBR for comb size 2 and comb size 4 separately. In some cases, due to channel busyness, SL-PRS resources with comb size 2 cannot be transmitted, but SL-PRS resources with comb size 4 can be transmitted.
[0102] In the second example, the definition and configuration of SL-PRS CR and SL-PRS CBR are associated with the PSCCH, or the definition and configuration of SL-PRS CR and SL-PRS CBR are associated with the PSCCH and the corresponding SL-PRS resources. For example, a CR used for SL positioning can be defined as the total number of REs (used or anticipated) used for its transmission divided by the total number of REs configured in the transmission pool within the CR time window.
[0103] In some cases, shared resource pools can be supported. The design of the SL-PRS in a shared resource pool should ensure backward compatibility. For RSSI, a new SL-PRS RSSI can be introduced, or an existing SL RSSI can be reused with slight modifications. For example, for a new SL-PRS RSSI, the SL-PRS RSSI can be defined as the linear average of the total received power (in W) observed in the configured sub-channels of the OFDM symbols configured for the SL-PRS, starting from the second OFDM symbol. Alternatively, the SL-PRS RSSI can be defined as the linear average of the total received power (in W) observed in the configured sub-channels of the OFDM symbols configured for the PSCCH and SL-PRS, starting from the second OFDM symbol. For a modified SLRSSI, the SL RSSI is defined as the linear average of the total received power (in W) observed in the configured sub-channels of the OFDM symbols configured for the PSCCH and PSSCH or SL-PRS, starting from the second OFDM symbol.
[0104] The CR or CBR window size can also be related to the sensing window size, the SL-PRS selection window size, the SL-PRS periodicity, and / or the SL-PRS resource reservation period. For example, the CR or CBR window size can also be related to the maximum number of sensing window sizes and / or selection window sizes for SL-PRS. The CR and CBR window sizes can differ from the window sizes for SL communication. Furthermore, even in a shared resource pool, when PSSCH and SL-PRS are transmitted within the same time slot, the priorities of SL-PRS and PSSCH can differ. In this case, the CR of SL-PRS and PSSCH can be evaluated separately.
[0105] In some cases, SL-PRS congestion control processing time is supported. For example, SL-PRS congestion control processing time is based on subcarrier spacing (SCS) and UE capability, where SCS corresponds to the subcarrier spacing of the sidelink channel to which SL-PRS will be transmitted. SL-PRS congestion control can also be associated with the CR or CBR window size (e.g., N) used for SL positioning. The UE can report one or more of its SL-PRS congestion control processing capabilities to the UE (SLPP signaling), LMF (LPP signaling), or gNB (RRC signaling). The UE, LMF, or gNB (e.g., the base station) can also request a UE to report its capabilities regarding SL-PRS congestion control processing capabilities.
[0106] Alternatively, if the CR or CBR window size is the same as the size of the SL communication or shared resource pool, the UE can use the same congestion control processing time for either timing capability 1 or timing capability 2. The UE can report whether the congestion control processing capability is applicable to SL communication or SL positioning, or both.
[0107] Figure 13 This is a schematic diagram illustrating example wireless communication 1300 according to various arrangements. Wireless communication 1300 may include UE 1302 and device 1304 (e.g., server UE, base station). Device 1304 may transmit request 1306 (e.g., SL-PRS CBR measurement request) to UE 1302, and UE 1302 may transmit report 1308 (e.g., SL-PRS CBR measurement report) to device 1304.
[0108] For example, in SL positioning, for better congestion control (e.g., adjusting SL-PRS resource pool configuration, adjusting SL-PRS resource configuration), the UE can report SL-PRS CBR measurements to the gNB or other UEs or LMF. The UE can report its CBR measurements to one or more UEs, and the UE can request one or more UEs to provide CBR measurements for SL positioning.
[0109] For SL-PRS CBR measurement request 1306, device 1304 may send signaling (e.g., RRC, MACCE, DCI, LPP, via higher-layer signaling, SLPP, PC5-RRC, PC5-S, application layer) to UE 1302 to request CBR measurement. This request signaling may include at least one of the following: SL-PRS resource pool ID, SL-PRS CBR measurement, timestamp of CBR measurement, time window of CBR measurement, comb size, SL-PRS resource ID, SL-PRS resource set ID, CBR of SL-PRS or CBR of SCI or CBR for SL-PRS and SCI, CBR measurement of a specific comb size, and / or expected time window.
[0110] For SL-PRS CBR measurement report 1308, UE 1302 can report SL-PRS CBR measurements to device 1304 (e.g., via higher-layer signaling, SLPP, PC5-RRC, PC5-S, application layer, RRC, MAC CE, DCI, LPP). The reporting signaling can include at least one of the following: SL-PRS resource pool ID, SL-PRS CBR measurement, timestamp of CBR measurement, time window of CBR measurement, comb size, SL-PRS resource ID, SL-PRS resource set ID, CBR of SL-PRS or CBR of SCI, or CBR for both SL-PRS and SCI, and / or CBR measurement for a specific comb size. Furthermore, UE 1302 can report its ability to support SL-PRS CBR measurements to the UE, gNB, or LMF.
[0111] Figure 14 This is a schematic diagram illustrating the flow of example wireless communication 1400 according to various arrangements. Communication 1400 may be related to latency. CBR measurement request 1402 and corresponding CBR report 1404 should be completed within the expected time window 1406. The timing requirement / latency may be included in each CBR measurement request, or may be (pre-)configured via higher-layer signaling between UEs (e.g., SLPP) or between UE and gNB / LMF (e.g., RRC, LPP).
[0112] Figure 15 This is a schematic diagram illustrating the flow of an example wireless communication 1500 according to various arrangements. Wireless communication 1500 may include UE 1502 and UE 1504. UE 1502 may transmit a request 1506 (e.g., a request for CBR results of a Tx SL-PRS resource pool) to UE 1504; UE 1504 may transmit feedback 1508 (e.g., CBR result feedback) to UE 1502; and UE 1502 may send a transmission 1510 (e.g., SL-PRS transmission based on CBR results) to UE 1504.
[0113] For example, in scenarios involving multiple anchor UEs and one target UE in a positioning session, or involving the positioning of the target UE, if the target UE provides SL-PRS resource transmission information to multiple anchor UEs, the anchor UEs can save energy. In this case, the UE can calculate the SL-PRS CBR of one or more UEs. The UE can assist the SL-PRS transmission of other UEs by performing CBR measurements on other UEs. The CBR calculation of another UE can be triggered by a request from the UE, by higher-layer signaling from the gNB, or by the higher layer of the UE.
[0114] The techniques described herein can support one or more of the following processes. UE 1502 can request another UE 1504 to calculate UE 1502's CBR measurement. Request signaling 1506 may include whether CBR assistance is needed, SL-PRS resource pool information for CBR, SL-PRS resources of UE 1502 to be transmitted, CBR for SL-PRS or CBR for SCI, or CBR for both SL-PRS and SCI, CBR measurement for a specific comb size, and / or response time requirements. In response to request 1506, UE 1504 can send feedback 1508 to UE 1502. Feedback 1508 may include: CBR measurement, SL-PRS resource pool information, CBR for SL-PRS or CBR for SCI, or CBR for both SL-PRS and SCI, CBR measurement for each comb pattern, and / or CBR measurement failure. Once UE1502 receives the CBR measurement taken by UE1504, UE1502 transmits SL-PRS and defines the corresponding SL-PRS transmission parameters based on the CBR provided by UE1504.
[0115] In some latency-related scenarios, auxiliary CBR measurement requests and corresponding CBR responses should be completed within a single time window. This timing requirement can be included in each CBR measurement request or can be (pre-)configured via higher-level signaling between UEs or between the UE and the gNB / LMF. Furthermore, the UE can report to the UE, gNB, or LMF whether it supports assisting other UEs in CBR measurements. The UE can also report to the UE, gNB, or LMF whether it supports receiving CBR measurements from other UEs.
[0116] Figure 16 This is a schematic diagram illustrating the flow of example wireless communication 1600 according to various arrangements. Communication 1600 may include UE 1602 and UE 1604 in side link communication.
[0117] For UE-initiated SL-PRS resource allocation, the transmission of IUC information for sidelink positioning among multiple UEs can lead to various advantages of maximum resource utilization and minimum resource conflict. In SL communication, at 1606, UE 1602 can request an SL-PRS IUC. At 1608, UE 1604 can determine one or more resource conflicts (IUC scheme 2) or determine whether to recommend a set of resources for UE 1602's SL-PRS transmission (IUC scheme 1). At 1610, UE 1604 can report the SL-PRS IUC information to UE 1602. At 1612, prior to the SL-PRS transmission at 1616, UE 1602 can select (reselect) SL-PRS resources for sidelink positioning based on the SL-PRS IUC information.
[0118] In some cases, the use of IUC in SL positioning may include indicating whether a set of SL-PRS resources is preferred or not; indicating potential / expected / detected resource conflicts; and / or IUC frames used to allocate SL-PRS resources or transmit SL-PRS configuration / resource allocation between UEs, where one UE can reserve SL-PRS resources for another UE. For example, UE 1602 may request UE 1604 to allocate or reserve SL-PRS resources. UE 1604 may further reserve or allocate the corresponding SL-PRS resources and pass this information to UE 1602. The delay limits / time requirements of SL-PRS IUC reports triggered by explicit requests from associated SL-PRS IUCs may be (pre-)defined / configured by the network at the RC or MAC layer, or by the UE via SLPP, SCI, SL MACCE, PC5-RRC layer, PC5-S layer, or by LMF via LPP signaling.
[0119] In some cases, SL-PRS IUC signaling can be supported. For example, for SL-PRS IUC used for recommendation (preferred / non-preferred), IUC triggering and / or IUC reporting can be supported. In the first example, SL-PRS IUC can be triggered by an explicit request from the UE or by a condition. The container for the explicit request can be SCI, MAC CE, or SCI and MAC CE, SLPP, LPP, or RRC. The IUC request may include additional bits indicating that the requested IUC information is generated based on SCI or SL-PRS, or both SCI and SL-PRS. Specifically, UE 1602 can request IUC information from UE 1604 regarding preferred / non-preferred resources based on PSCCH occupancy, SL-PRS occupancy, or both PSCCH and SL-PRS occupancy. One or more of the following parameters / information may also be included in the IUC request signaling: SL communication or SL-PRSIUC indicator (e.g., 1 bit), offer or request indicator (e.g., 1 bit), preferred or non-preferred resource (1 bit), selection window position, SL-PRS transmission priority, SL-PRS resource ID, SL-PRS resource set ID, SL-PRS resource reservation period or SL-PRS period, comb size, SL-PRS bandwidth and / or SL-PRS sequence ID.
[0120] In the second example, the container for the SL-PRS IUC report (e.g., UE 1604 reporting an IUC to UE 1602) can be SCI, MAC CE, or a combination of SCI and MAC CE, SLPP, LPP, or RRC. The IUC report may include additional bits indicating whether the IUC information is generated based on SCI or SL-PRS. Specifically, UE 1604 may inform UE 1602 that the preferred / non-preferred resource is obtained based on the PSCCH occupancy rate, the SL-PRS occupancy rate, or both the PSCCH and SL-PRS occupancy rates. The IUC report signaling may also include one or more of the following parameters / information: SL communication or SL-PRS IUC indicator (e.g., 1 bit), offer or request indicator (e.g., 1 bit), preferred or non-preferred resource (1 bit), one or a list of preferred / non-preferred SL-PRS resources, the first resource location of each preferred / non-preferred SL-PRS resource, SL-PRS periodicity, comb size, SL-PRS bandwidth, and / or SL-PRS sequence ID.
[0121] Figure 17 This is a schematic diagram illustrating an example wireless communication 1700 according to various arrangements. Communication 1700 may include UE 1702 and UE 1704 in side link communication. Time 1712 may be the time to reply to message 1706 after receiving it, time 1714 may be the RTT from sending message 1706 to receiving message 1708, time 1716 may be the time to transmit message 1710 when message 1708 is received, and time 1718 may be the RTT from transmitting message 1708 to receiving message 1710.
[0122] Communication 1700 can support combinations of SL-PRS IUCs with different positioning methods. For SL-RTT (e.g., bilateral RTT), SL-PRS IUC information contained in the SCI or SL MAC CE can be transmitted along with SL-PRS 1 transmission (e.g., message 1706). The IUC information may include preferred or non-preferred resources, or SL-PRS resources reserved / allocated for SL-PRS2 transmission (e.g., message 1708). This can initiate the transmission for RTT positioning and assist the transmission of UE 1704.
[0123] Figure 18This is a schematic flowchart illustrating an example wireless communication system 1800 according to various arrangements. System 1800 may include UE 1802, UE 1804, UE 1806, and UE 1808 in sidelink communication (e.g., SL-TDOA). Each of UEs 1802, 1804, and 1806 may transmit corresponding SL-PRS 1810, 1812, and 1814 with UE 1808. For example, UE 1808 (e.g., a target UE) may receive SL-PRS from three anchor UEs 1802, 1804, and 1806, wherein anchor UE 1802 transmits SL-PRS 1810, anchor UE 1804 transmits SL-PRS 1812, and anchor UE 1806 transmits SL-PRS 1814. From the perspective of the target UE 1808, UE 1808 can arrange SL-PRS measurements by transmitting SL-PRS IUC to multiple anchor UEs 1802, 1804 and 1806 through the target UE 1808.
[0124] Figure 19 This is a flowchart illustrating an example method 1900 for lateral link positioning enhancement according to various arrangements. In some cases, method 1900 may include configurations for a wireless communication device to receive SL-PRS configurations.
[0125] In 1902, the first wireless communication device can receive the SL-PRS configuration. In 1904, the first wireless communication device can determine the SL-PRS transmission parameters based on congestion control parameters. In 1906, the first wireless communication device can transmit the SL-PRS to the second wireless communication device using IUC information, wherein the second wireless communication device measures the SL-PRS during the measurement period.
[0126] For example, SL positioning measurement cycles can be supported. When the physical layer receives the last of the NR-ProvideAssistanceData message and the NR-RequestLocationInformation message from the first UE via SLPP, the second UE can be able to measure multiple (up to UE capability) UESL-PRSRSTD / RSRP / RSRPP / Rx-Tx time difference measurements in the configured resource pool within the measurement cycle.
[0127] The measurement period requirements for DL-PRS can be defined based on the Positioning Frequency Layer (PFL), where each PFL is configured with SCS, CP, DL-PRS bandwidth, etc. The UE may not be able to simultaneously process / measure DL-PRS from different PFLs. However, a carrier in SL communication can include only one BWP. For example, the SL SCS and CP are configured according to the SL BWP so that all resource pools within a single BWP of the carrier share the same SCS. Therefore, if multiple resource pools come from the same BWP, the UE can simultaneously process and measure SL-PRS resources from multiple Tx resource pools. The measurement period requirements for SL-PRS can be defined based on the SL BWP, as shown in the figure below:
[0128]
[0129] Where i is the index of SL-BWP, and L is the total number of SL-bwp if SLCA (carrier aggregation) is introduced and there are one or more SL BWPs.
[0130] Since there is only one SL BWP, then L=1:
[0131]
[0132] The measurement cycle requirements for SL positioning are associated with one or more of the following: the maximum resource reservation time indicated in SCI 1-A (e.g., 32 time slots); the sensing window size used for SL positioning; the selection window size for SL positioning; other delay-related parameters; and SL-PRS. CBR, CR, CRlimt; SL-PRS transmission priority; SL-PRS period or SL-PRS resource reservation period indicated in SCI (e.g., if different SL-PRS resources have different periods, the measurement period requirement is associated with the least common multiple (LCM) of multiple SL-PRS periodicities); Sample number: 1, 2, 4 or other values; (N, T) for SL-PRS (e.g., the duration N of an SL-PRS symbol in ms / slot / symbol, which the UE can process for each Tms / slot / symbol, where (N, T) for SL-PRS is the UE capability and the measurement period requirement can be defined based on that capability); Maximum number of SL-PRS resources in a slot; TEG-related scaling factor; Beam scanning factor; and whether the dual-sided RTT (DS-RTT) method is used. For example, if a biplane RTT is used, the measurement cycle requirement for a biplane RTT is larger than that defined for a single-plane RTT (SS-RTT), adding an extra offset, or multiplying the equation based on the single-plane RTT by a scaling factor.
[0133] In some cases, for DS-RTT, compared to the measurement period of SS-RTT, an offset Δ can be introduced into the measurement period equation of DS-RTT, where Δ ≥ 0:
[0134]
[0135] Alternatively, a scaling factor S can be introduced, where S≥1 or S>1:
[0136]
[0137] Introducing an offset or scaling factor for DS-RTT reveals that the complexity and latency of UE measuring DL-PRS using the DS-RTT method are greater than those using the SS-RTT method.
[0138] Figure 20 This is a flowchart illustrating an example method 2000 for lateral link positioning enhancement according to various arrangements. In some cases, method 2000 may include a configuration for a wireless communication device to receive an SL-PRS.
[0139] In 2002, the second wireless communication device could receive SL-PRS from the first wireless communication device using IUC information. In 2004, the second wireless communication device could measure SL-PRS during a measurement period, wherein the first wireless communication device received the SL-PRS configuration and determined the SL-PRS transmission parameters based on congestion control parameters.
[0140] Although various arrangements of this solution have been described above, it should be understood that they are given by way of example only and not by way of limitation. Similarly, various schematic diagrams may be provided to illustrate example architectures or configurations, which are provided to enable those skilled in the art to understand the exemplary features and functionality of this solution. However, those skilled in the art will understand that this solution is not limited to the example architectures or configurations shown, but can be implemented using a variety of alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of some arrangements may be combined with one or more features of another arrangement described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary arrangements described above.
[0141] It should also be understood that any reference to elements in this document using names such as "first," "second," etc., generally does not restrict the number or order of those elements. Rather, these names are used herein as a convenient means of distinguishing between two or more elements or examples of a single element. Therefore, references to first and second elements do not imply that only two elements can be used, or that the first element must somehow precede the second element.
[0142] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.
[0143] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software module"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally according to their functionality. Whether this functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.
[0144] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented or executed by integrated circuits (ICs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof, including general-purpose processors. Logic blocks, modules, and circuits may further include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.
[0145] If implemented in software, the functionality can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, with communication media including any medium capable of transferring a computer program or code from one place to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer.
[0146] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements to perform the relevant functions described herein. Furthermore, for the purposes of discussion, various modules are described as discrete modules; however, it will be apparent to those skilled in the art that two or more modules can be combined to form a single module that performs the relevant functions according to the arrangement of this scheme.
[0147] Additionally, memory or other storage and communication components may be employed in the arrangement of this scheme. It should be understood that, for clarity, the above description has referenced different functional units and processors in describing the arrangement of this scheme. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains can be used without departing from this scheme. For example, a function illustrated as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable devices for providing the described functions and do not indicate a strict logical or physical structure or organization.
[0148] Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the implementations shown herein, but should be given the broadest scope as set forth in the following claims, consistent with the novel features and principles disclosed herein.
Claims
1. A wireless communication method, comprising: The first wireless communication device receives the SL-PRS configuration for the side link positioning reference signal SL-PRS; The first wireless communication device determines the SL-PRS transmission parameters based on congestion control parameters; The first wireless communication device transmits the SL-PRS to the second wireless communication device using UE-coordinated IUC information, wherein the second wireless communication device measures the SL-PRS during the measurement period.
2. The method according to claim 1, wherein, The SL-PRS configuration corresponds to the resource pool of the SL-PRS.
3. The method according to claim 2, wherein, The resource pool includes one of the following: Resources for comb-based multiplexing of multiple wireless communication devices; Time division multiplexing (TDM) resources for the plurality of wireless communication devices; or The combination of comb-based multiplexing resources and TDM resources for the plurality of wireless communication devices.
4. The method according to claim 2, wherein, The resource pool includes at least the SL-PRS configuration and the physical side link control channel (PSCCH) configuration.
5. The method according to claim 2, wherein, The resource pool includes one or more of the following: At least one SL-PRS resource; or At least one SL-PRS resource set; Each of the at least one SL-PRS resource or each of the at least one SL-PRS resource set is associated with a Physical Side Link Control Channel (PSCCH) configuration or a Side Link Control Information (SCI) configuration.
6. The method according to claim 2, wherein, The resource pool includes at least one SL-PRS resource; and The resource pool is associated with the physical side link control channel (PSCCH) configuration.
7. The method according to claim 2, wherein, One of the following: The resource pool is identified by a resource pool identifier (ID), and the side link control information (SCI) indicates the resource pool ID; or The resource pool includes SL-PRS resources identified by resource IDs, and the SCI indicates the resource ID; or The resource pool includes SL-PRS resource sets identified by resource set IDs, and the SCI indicates the resource set IDs.
8. The method according to claim 1, wherein, The SL-PRS sequence ID offset is indicated by the side link control information (SCI).
9. The method according to claim 1, wherein, The SL-PRS sequence ID offset is indicated by the higher layer.
10. The method of claim 1, wherein the congestion control parameter is determined to include at least one of SL-PRS channel occupancy rate CR or SL-PRS channel busy rate CBR.
11. The method according to claim 1, wherein, The congestion control parameters are associated with at least one of the Physical Side Link Control Channel (PSCCH) or Side Link Control Information (SCI) or SL-PRS.
12. The method according to claim 1, wherein, The congestion control parameters are defined based on the SL-PRS resource allocation granularity and the SL-PRS configuration for the resource pool used by the SL-PRS.
13. The method according to claim 12, wherein, At least one of the following: The congestion control parameters are defined using the amount of resources occupied by the SL-PRS and the comb size; The congestion control parameters are defined using the number of occupied comb offsets, the sequence ID of the SL-PRS, the number of occupied physical side link control channels (PSCCH / SCI), or both the PSCCH / SCI and the SL-PRS.
14. The method according to claim 12, wherein, The congestion control parameters are associated with the evaluation time window; and The size of the evaluation time window is pre-configured / configured by the higher-level management.
15. The method according to claim 12, wherein, At least one of the following: The congestion control parameter is associated with at least one of one or more occupied resources of the SL-PRS, wherein the at least one of the one or more occupied resources has a first signal strength higher than a first threshold; or The congestion control parameters are associated with at least one physical-side link control channel (PSCCH) resource in the resource pool of the SL-PRS, the at least one PSCCH resource having a second signal strength higher than a second threshold.
16. The method according to claim 12, wherein, The congestion control parameters are defined using symbols or resource elements (REs).
17. The method according to claim 12, wherein, At least one of the following: The congestion control parameters are defined using the number of resources occupied by the SL-PRS and the number of time resources for each resource of the SL-PRS. The congestion control parameters are defined using the amount of physical-side link control channel (PSCCH) resources occupied; or The congestion control parameters are defined using the amount of PSCCH resources occupied and the corresponding reserved SL-PRS resources.
18. The method according to claim 12, wherein, The congestion control parameters are defined using frequency domain and time domain modes; or Define the congestion control parameters for each comb size.
19. The method according to claim 1, wherein, The SL-PRS transmission parameters are defined using the window size of the congestion control parameters; The method also includes the processing capability of the first wireless communication device to report the congestion control parameters to the network or the second wireless communication device.
20. The method according to claim 19, wherein, The processing capability indicates whether the first wireless communication device applies the congestion control parameters to at least one of SL communication or SL positioning.
21. The method according to claim 1, comprising: The first wireless communication device receives a measurement request for the congestion control parameters from the network or from the second wireless communication device; The first wireless communication device sends a report of the first measurement of the congestion control parameters to the network or the second wireless communication device.
22. The method according to claim 21, wherein, The measurement request includes at least one of the following: Resource pool identifier ID; The second measurement of the congestion control parameters; The timestamp of the first measurement of the congestion control parameters; The first measurement time window of the congestion control parameters; Comb-like size; Resource ID; Resource set ID; The congestion control parameters of at least one of the SL-PRS or the side link control information SCI; A third measurement of at least one comb-sized congestion control parameter; or The expected time window for transmitting the report.
23. The method according to claim 21, wherein, The report includes at least one of the following: Resource pool identifier ID; The first measurement of the congestion control parameters; The timestamp of the first measurement of the congestion control parameters; The first measurement time window of the congestion control parameters; Comb-like size; Resource ID; Resource set ID; The congestion control parameters of at least one of the SL-PRS or SCI sidelink control information; or A second measurement of at least one of the congestion control parameters of comb size.
24. The method according to claim 1, wherein, The second wireless communication device reports to the first wireless communication device or the network that the second wireless communication device supports assisting another wireless communication device in measuring the congestion control parameters; The second wireless communication device measures the congestion control parameters and sends the measurement results of the congestion control parameters to the first wireless communication device.
25. The method according to claim 1, wherein, The IUC information includes IUC frames, which allocate resources, transmit configurations, or allocate resources among multiple wireless communication devices, wherein the second wireless communication device reserves resources for the SL-PRS of the first wireless communication device.
26. The method according to claim 1, comprising: The first wireless communication device sends an IUC request to the second wireless communication device; The first wireless communication device receives an IUC report containing the IUC information from the second wireless communication device; as well as The first wireless communication device selects resources for transmitting the SL-PRS based on the IUC information.
27. The method according to claim 26, wherein, The IUC request indicates that the IUC information is generated based on at least one of the Side Link Control Information (SCI) or the SL-PRS. The IUC request includes at least one of the following: resource identifier ID, resource set ID, first comb size, second bandwidth of the SL-PRS, or first sequence ID of the SL-PRS; The IUC report includes an indication of generating the IUC information based on at least one of the SCI or the SL-PRS; or The IUC report includes at least one of a preferred or non-preferred resource list, a second comb size, a second bandwidth of the SL-PRS, or a second sequence ID of the SL-PRS.
28. The method according to claim 1, wherein, The measurement period is determined based on at least one of the following: Maximum resource reservation time; The sensor window size used for SL positioning; The size of the selection window used for SL positioning; Delay parameter; Congestion control parameters; Transmission priority; The periodicity or resource reservation period of the SL-PRS; Sample number; The N and T of the SL-PRS; The maximum number of resources of the SL-PRS in the time slot; The scaling factor of the timing error group TEG; Beam scanning factor; or Whether to use bilateral round-trip time (DS-RTT).
29. The method according to claim 28, wherein, The measurement period of the DS-RTT is determined based on the following: Added offset; or Scale factor.
30. A wireless communication device, comprising at least one processor and a memory, wherein, The at least one processor is configured to read code from the memory and implement the method according to claim 1.
31. A computer program product comprising computer-readable program medium code stored thereon, the code causing the at least one processor, when executed by at least one processor, to implement the method of claim 1.
32. A wireless communication method, comprising: The second wireless communication device uses UE-coordinated IUC information to receive the first wireless communication device's side-link positioning reference signal SL-PRS; as well as The second wireless communication device measures the SL-PRS during the measurement period, wherein the first wireless communication device receives the SL-PRS configuration of the SL-PRS, and the first wireless communication device determines the SL-PRS transmission parameters based on the congestion control parameters.
33. A wireless communication device, comprising at least one processor and a memory, wherein, The at least one processor is configured to read code from the memory and implement the method according to claim 32.
34. A computer program product comprising computer-readable program medium code stored thereon, the code causing the at least one processor, when executed by at least one processor, to implement the method of claim 32.