RS transmission opportunity and authorization in wireless communications

Abstract

The present document relates generally to wireless communications including a user equipment that determines an authorization of one or more grants for a reference signal (RS) resource allocation. The user equipment determines one or more RS characteristics in each of the one or more RS transmission opportunities in the grant. Further, the user equipment transmits the RS in each RS transmission duration corresponding to a respective one of the one or more transmission opportunities.

Description

Technical Field

[0001] This document generally relates to opportunities and licenses for the transmission of reference signals (RS) in wireless communications. Background Technology

[0002] In wireless communication systems, sidelink (SL) positioning reference signal (PRS) may be enabled to support sidelink positioning of communication nodes. Regarding sidelink data transmission, the medium access control (MAC) layer of the transmitting user equipment can perform license determination, logical channel prioritization (LCP), and hybrid automatic repeat request (HARQ) processes. We look forward to proposing ways to improve SL-PRS communication. Summary of the Invention

[0003] This document relates to methods, systems, apparatuses, and devices for wireless communication. In some embodiments, a method for wireless communication includes: a user equipment determining a license in one or more licenses allocated for a reference signal (RS) resource; the user equipment determining one or more RS characteristics in each of the one or more RS transmission opportunities in the license; and the user equipment transmitting an RS during each RS transmission duration corresponding to a corresponding transmission opportunity in one of the one or more transmission opportunities.

[0004] In some other embodiments, an apparatus (e.g., a network device) is disclosed. The apparatus may include one or more processors and one or more memories, wherein the one or more processors are configured to read computer code from the one or more memories to implement any of the methods described above.

[0005] In some other embodiments, a computer program product is disclosed. This computer program product may include a non-transitory computer-readable program medium having computer code stored thereon, which, when executed by one or more processors, causes the one or more processors to implement any of the methods described above.

[0006] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0007] Figure 1 An example block diagram of a wireless communication system is shown.

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

[0009] Figure 3 A schematic diagram of a dedicated pool time slot structure is shown.

[0010] Figure 4 A schematic diagram illustrating the use and non-use of periodically retained SL-PRS resources is shown.

[0011] Figure 5 A flowchart of an example method for wireless communication is shown.

[0012] Figure 6 This is a timing diagram illustrating an example of the MAC layer selecting more than one SL-PRS in a time slot.

[0013] Figure 7 A schematic diagram of an example structure of a MAC PDU is shown.

[0014] Figure 8 A schematic diagram of an example structure for an SL-SCH subheader is shown.

[0015] Figure 9 A schematic timing diagram is shown for an example of user equipment 102 selecting SL-PRS for transmission.

[0016] Figure 10 A schematic diagram illustrating the priority of transmission control is shown. Detailed Implementation

[0017] This specification describes various embodiments of systems, apparatuses, devices, and methods relating to reference signal (RS) transmission opportunities and licensed wireless communications.

[0018] Figure 1 A diagram of an example wireless communication system 100 is shown, which includes a plurality of communication nodes (or simply nodes) configured to communicate wirelessly with each other. Typically, the communication nodes include at least one user equipment 102 and at least one wireless access node 104. Figure 1 The example wireless communication system 100 is shown as including two user equipments 102 and a wireless access node 104, the two user equipments 102 including a first user equipment 102 (1) and a second user equipment 102 (2). However, various other examples of wireless communication systems 100 including any combination of one or more user equipments 102 and / or one or more wireless access nodes 104 are also possible.

[0019] Typically, user equipment described herein (such as user equipment 102) may include a single electronic device or apparatus capable of wireless communication over a network, or multiple electronic devices or apparatuses (e.g., a network of multiple electronic devices or apparatuses). User equipment may include, or be otherwise referred to as, a user terminal, user terminal equipment, or user equipment (UE). Furthermore, user equipment may be, or includes, mobile devices (such as mobile phones, smartphones, smartwatches, tablets, laptops, vehicles, or other vessels (as a non-limiting example, those driven by a person, motor, or engine, such as automobiles, airplanes, trains, ships, or bicycles)) or fixed or stationary devices (as a non-limiting example, such as desktop computers, or other computing devices that are typically stationary for extended periods (such as appliances, other relatively heavy devices including those for the Internet of Things (IoT), or computing devices used in commercial or industrial environments)). In various embodiments, user equipment 102 may include transceiver circuitry 106 coupled to antenna 108 to enable wireless communication with wireless access network node 104. Transceiver circuitry 106 may also be coupled to processor 110, which may also be coupled to memory 112 or other storage devices. The memory 112 may store instructions or code therein, which, when read and executed by the processor 110, cause the processor 110 to implement the various methods described herein.

[0020] Furthermore, generally speaking, a wireless access node (such as wireless access node 104) as described herein may include at least one device, electronic and / or network device or apparatus, and may include one or more base stations or other wireless network access points capable of wirelessly communicating with one or more user equipments and / or with one or more other wireless access nodes 104 via a network. For example, in various embodiments, wireless access node 104 may include at least one of the following: a 4G LTE base station, a 5G NR base station, a 5G centralized unit base station, a 5G distributed unit base station, a next-generation Node B (gNB), an enhanced Node B (eNB), or other similar or next-generation (e.g., 6G) base station, or a location management function (LMF). Wireless access node 104 may include transceiver circuitry 114 coupled to an antenna 116 (antenna 116 may include an antenna tower 118 in various ways) to enable wireless communication with user equipment 102 or another wireless access node 104. The transceiver circuit 114 may also be coupled to one or more processors 120, which may also be coupled to memory 122 or other storage devices. Memory 122 may store instructions or code therein that, when read and executed by processor 120, cause processor 120 to implement one or more of the methods described herein.

[0021] Figure 2 A block diagram of an example configuration of a radio access node 104 is shown. In this example configuration, the radio access node 104 may include a location management function (LMF) 202 and one or more radio access network (RAN) nodes 204. Some embodiments may include only one RAN node 204. Other embodiments (e.g., such as...) Figure 2 The RAN node 204(1) to 204(n) shown may include a plurality of RAN nodes 204(1) to 204(n), wherein n is two or more. In any embodiment of the various embodiments, the RAN node 204 may be or include a next-generation (NG) RAN node, gNB, ng-eNB, transmission reception point (TRP), and / or base station, examples of which are shown in Figure 2 As shown in the diagram. Furthermore, each component of the wireless access node 104 (e.g., LMF 202 and each RAN node 204) may include at least one network device, and / or may be configured in hardware or a combination of hardware and software, for example, as... Figure 1As shown for the wireless access node 104, it may be configured with a processor 120, a memory 122, a transceiver circuit 114, an antenna 116 and / or an antenna tower 118.

[0022] In addition, such as Figure 2 As shown, LMF 202 and each RAN node 204 can be configured to communicate with each other (transmit and receive), for example, to communicate signals or messages, and LMF 202 and each RAN node 204 can be configured to communicate (transmit and receive) with one or more user equipments 102 (directly or indirectly via another component of radio access node 104). For example, LMF 202 can communicate directly with user equipment 102. In a particular embodiment, LMF 202 can communicate directly with user equipment 102 according to the Long-Term Evolution (LTE) positioning protocol (LPP) (i.e., via LPP signaling). Similarly, RAN node 204 can communicate directly with user equipment 102. In a particular embodiment, RAN node 204 can communicate directly with user equipment 102 at least via radio resource control (RRC) signaling. Additionally, LMF 202 can communicate directly with each RAN node 204. In certain embodiments, LMF 202 can communicate directly with each RAN node 204 according to the New Radio Positioning Protocol A (NRPPa) (i.e., via NRPPa signaling). Furthermore, for at least some embodiments (e.g., as...), Figure 2 As shown, each RAN node 204 may include one or more sub-components. For example, RAN node 204 may include a gNB and / or at least one transmit-receive point (TRP) 208. Furthermore, unless otherwise specified herein, the term "network" or "network device" may include at least one gNB 206, at least one ng-eNB, at least one TRP 208, at least one base station, at least one RAN node 204 (e.g., at least one NG-RAN node), and / or at least one LMF 202. Further functionalities of the LMF 202 and RAN node 204 will be described in more detail below.

[0023] Additionally, returning Figure 1In various embodiments, two communication nodes in wireless system 100—such as user equipment 102 and wireless access node 104, two user equipment 102 without wireless access node 104, or two wireless access nodes 104 without user equipment 102—can be configured to wirelessly communicate with each other in or through a mobile network and / or wireless access network according to one or more standards and / or specifications. Typically, standards and / or specifications can define rules or procedures under which communication nodes can wirelessly communicate. These rules or procedures, in various embodiments, can include those for communication in the millimeter (mm) band, and / or those with multiple antenna schemes and beamforming capabilities. Additionally or alternatively, the standards and / or specifications are those that define wireless access technologies and / or cellular technologies (such as, as a non-limiting example, Fourth Generation (4G) Long Term Evolution (LTE), Fifth Generation (5G) New Radio (NR), or New Radio Unlicensed (NR-U)).

[0024] Furthermore, in the wireless system 100, communication nodes are configured to wirelessly communicate with each other. Typically, communication between two communication nodes in the wireless system 100 can be or includes transmitting or receiving, and is usually simultaneous, depending on the perspective of the specific node in the communication. For example, for a given communication between a first node and a second node, where the first node transmits a signal to the second node and the second node receives a signal from the first node, the first node can be referred to as a source or transmitting node or device, and the second node can be referred to as a destination or receiving node or device, and the communication can be considered as the transmission of the first node and the reception of the second node. Of course, since each communication node in the wireless system 100 can both transmit and receive signals, a single communication node can be both a transmitting / source node and a receiving / destination node simultaneously, or switch between source / transmitting node and destination / receiving node.

[0025] Furthermore, specific signals can be characterized or defined as uplink (UL) signals, downlink (DL) signals, or sidelink (SL) signals. An uplink signal is a signal transmitted from user equipment 102 to radio access node 104. A downlink signal is a signal transmitted from radio access node 104 to user equipment 102. A sidelink signal is a signal transmitted from one user equipment 102 to another user equipment 102, or from one radio access node 104 to another radio access node 104. Moreover, for sidelink transmission, the first / source user equipment 102 transmits the sidelink signal directly to the second / destination user equipment 102 without forwarding it to radio access node 104.

[0026] Furthermore, the signals transmitted between communication nodes in system 100 can be characterized or defined as data signals or control signals. Typically, data signals are signals that include or carry data (such as multimedia data, e.g., voice and / or image data), while control signals are signals that carry control information that configures the communication nodes in a specific way to facilitate communication with each other, or otherwise controls how the communication nodes transmit data signals to each other. Additionally, specific signals can be defined or characterized by combinations of data / control and uplink / downlink / sidelink signals, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, sidelink control signals, and sidelink data signals.

[0027] For at least some specifications (such as 5G NR), data signals and control signals are transmitted and / or carried on physical channels. Typically, a physical channel corresponds to a set of time-frequency resources used for signal transmission. Different types of physical channels can be used to transmit different types of signals. For example, physical data channels (or simply data channels) are used to transmit data signals, and physical control channels (or simply control channels) are used to transmit control signals. Example types of physical data channels include, but are not limited to, physical downlink shared channels (PDSCH) for transmitting downlink data signals, physical uplink shared channels (PUSCH) for transmitting uplink data signals, and physical sidelink shared channels (PSSCH) for transmitting sidelink data signals. Furthermore, example types of physical control channels include, but are not limited to, physical downlink control channels (PDCCH) for transmitting downlink control signals, physical uplink control channels (PUCCH) for transmitting uplink control signals, and physical sidelink control channels (PSCCH) for transmitting sidelink control signals. As used herein, for simplicity, unless otherwise stated, a specific type of physical channel is also used to refer to the signals transmitted on that specific type of physical channel, and / or the transmission on that specific type of transmission. By way of example, PDSCH refers to the physical downlink shared channel itself, downlink data signals transmitted on the PDSCH, or downlink data transmission. Therefore, a communication node sending or receiving a PDSCH means that the communication node is sending or receiving signals on the PDSCH.

[0028] Additionally, for at least some specifications such as 5G NR and / or for at least some types of control signals, the control signals transmitted by the communication nodes may include control information necessary to enable the transmission of one or more data signals between the communication nodes and / or the scheduling of one or more data channels (or one or more transmissions on data channels). For example, such control information may include: information necessary to correctly receive, decode, and demodulate data signals received on a physical data channel during data transmission; and / or information necessary to grant uplink scheduling authorization, which informs the user equipment of the resources and transmission formats used for uplink data transmission. In some embodiments, the control information includes downlink control information (DCI) transmitted from the radio access node 104 to the user equipment 102 in the downlink direction. In other embodiments, the control information includes uplink control information (UCI) or sidelink control information (SCI), the uplink control information being sent from user equipment 102 to radio access node 104 in the uplink direction, and the sidelink control information being sent from one user equipment 102 (1) to another user equipment 102 (2) in the sidelink direction.

[0029] Furthermore, in some implementations, SL-PRS transmission is enabled to support sidelink positioning. For sidelink data transmission, the Media Access Control (MAC) layer of the transmitting user equipment 102 can perform authorization determination, Logical Channel Priority (LCP), and / or Hybrid Automatic Repeat Request (HARQ) processes.

[0030] In some implementations, even if SL positioning may introduce two resource pools (e.g., a shared resource pool and a dedicated resource pool), user equipment 102 can still determine the authorization within only one transport resource pool. This specification describes how to determine SL-PRS transport authorization for different schemes within the shared resource pool and the dedicated resource pool.

[0031] Furthermore, in some implementations, the LCP process can be utilized when the MAC layer generates a MAC protocol data unit (PDU) to transmit SL data. However, for SL-PRS, since SL-PRS is a reference signal and it is not combined at the receiving node, a MAC PDU may not be generated. This specification describes how the characteristics of the SL-PRS transmission to be sent are determined for a single grant.

[0032] Additionally, in some implementations, retransmission of sidelink data and HARQ feedback can be used to ensure reliability. Furthermore, time interval constraints can be specified between the PSSCH, PSCCH, and / or the physical sidelink feedback channel (PSFCH). However, some implementations for SL-PRS do not have a HARQ feedback mechanism or a PSFCH. This specification describes methods for determining time interval constraints between two consecutive transmissions.

[0033] Additionally, in some implementations, the MAC layer can have up to sixteen SL processes working in parallel to send sidelink data. When the number of SL-PRS transmission requests is relatively large, a single process dedicated to SL-PRS transmission may not meet the sidelink location quality of service (QoS) requirements. This specification describes ways to increase the maximum number of SL-PRS processes (particularly for dedicated pools).

[0034] Additionally, in some implementations, the MAC layer may perform a transmit (Tx) resource selection check when determining the selected grant for sidelink data transmission. This specification describes how user equipment 102 determines when to perform Tx resource selection and / or reselection for SL-PRS transmissions.

[0035] Additionally, in some implementations, the MAC layer can transmit both the sidelink shared channel (SL-SCH) and the SL-PRS in a single timeslot. However, sometimes the SL-SCH may not actually contain any sidelink data to be transmitted. This specification describes how to indicate to the receiving (Rx) user equipment 102 whether a given SL-SCH contains sidelink data to be transmitted.

[0036] Furthermore, for at least some implementations of sidelink positioning, there can be two types of transmission resource pools. The first type of transmission resource pool is called a shared resource pool (also simply referred to as a shared pool herein). The second type of transmission resource pool is called a dedicated resource pool (also simply referred to as a dedicated pool herein). Additionally, for at least some implementations, the transmitting user equipment 102 may be allowed to transmit only PSCCH and PSSCH in the shared pool, or only PSCCH, SL-PRS, and PSSCH in the shared pool. Alternatively, for at least some implementations, the transmitting user equipment 102 may be allowed to transmit only PSCCH and SL-PRS in the dedicated pool. Figure 3 A schematic diagram of a dedicated pool time slot structure is shown.

[0037] For at least some implementations, the shared resource pool may not be configured for SL data according to Scheme 2 (described in further detail below), nor may it be configured for SL-PRS according to Scheme 1 (described in further detail below). Furthermore, for at least some implementations, the shared resource pool may not be configured for SL data according to Scheme 1, nor may it be configured for SL-PRS according to Scheme 2. Similarly, for at least some implementations, user equipment 102 can be configured with both a shared resource pool and a dedicated resource pool, and user equipment 102 can transmit SL-PRS on both types of resource pools simultaneously. For other reference signals (RS), a shared resource pool means that RS and SL data can be transmitted in the same resource pool, while a dedicated resource pool means that the resource pool may only be used to transmit RS and the corresponding PSCCH and / or feedback signaling.

[0038] Furthermore, in some implementations of sidelink positioning, SL-PRS transmission can have at least two schemes. For the first scheme, referred to herein as "Scheme 1" or "Scheme 1 for SL-PRS resource allocation," the sending user equipment 102 can receive SL-PRS resource allocation signaling from the network device 104. In sidelink positioning, for a user equipment 102 configured to perform SL-PRS according to Scheme 1 (referred to herein as Scheme 1 user equipment), there may be two ways to perform resource allocation. The first method includes dynamic resource allocation and / or dynamic granting. In the first method, user equipment 102 can receive radio resource control (RRC) configuration for the resource pool, and user equipment 102 can receive DCI format 3-0 scrambled by a sidelink (SL) - radio network temporary identifier (RNTI) to obtain sidelink resources for dynamically granting sidelink information and / or SL-PRS transmission. For at least some implementations, the first method can be used to allocate dynamic sidelink resources for emergency services. The second approach includes configured grant (CG) resource allocation and / or configuration grant. This second approach can include two types of CGs. In the first type (Type 1 CG), user equipment 102 can receive CG configurations including resource pool identifier (ID), CG configuration ID, CG period, and / or CG resource allocation, and can send sidelink information and / or SL-PRS according to the instructions in the RRC signaling. In the second type (Type 2 CG), user equipment 102 can receive CG configurations including CG index and CG period, and can receive DCI 3-0 scrambled by SL-configuredscheduling (CS)-RNTI to obtain time-domain resources and / or information related to CG activation and / or deactivation. Accordingly, user equipment 102 can send and / or stop sending sidelink information and / or SL-PRS according to the instructions in the RRC signaling and / or DCI.

[0039] For the second scheme, referred to herein as "Scheme 2," the transmitting user equipment 102 can use awareness-based resource selection to determine SL-PRS resource allocation. In sidelink localization, for a user equipment 102 configured to perform SL-PRS according to Scheme 2 (referred to herein as Scheme 2 user equipment 102), the SL grant is called a selection grant, and is selected by the transmitting (Tx) user equipment 102 itself through awareness or random selection. For example, when the transmitting user equipment 102 detects which resources are empty and not occupied by other user equipment 102, then the transmitting user equipment 102 can use and reserve those resources.

[0040] For other reference signals (RS), there may be schemes different from those used for SL-PRS, such as a scheme for enabling network device 104 to control the resources for transmitting RS, or a scheme for enabling user equipment 102 to self-select resources.

[0041] Furthermore, in some implementations, SL-PRS transmissions with and without periodic reservation can be performed according to or using Scheme 1 and / or Scheme 2. For SL-PRS transmissions performed with periodic reservation, the SL-PRS transmission can be reserved using a mechanism similar to the periodic resource reservation for another transport block (TB). For SL-PRS transmissions performed without periodic reservation, the mechanism used is similar to that for SL resource transmissions without periodic reservation, and at least one SL-PRS transmission without periodic reservation is performed. Figure 4 A schematic diagram illustrating the use and non-use of periodically retained SL-PRS resources is shown.

[0042] Furthermore, a license is a set of time and frequency resources that can be used to transmit data or reference signals. A license may include multiple transmission opportunities, thus a single license corresponds to a single transmission opportunity. Furthermore, a single transmission opportunity may correspond to an RS transmission timing or an RS duration. Further, a transmission opportunity may include at least one of the following: an initial transmission opportunity and a retransmission opportunity. Multiple transmission opportunities may be at least one of the following: one or more non-periodic reserved resources and one or more periodic reserved resources. Additionally, a license may have one of several license types, including: configured license, dynamic license, and selected license.

[0043] In addition, a single grant and / or transmission opportunity may also be referred to as at least one of the following terms: PSCCH duration, PSCCH timing, RS duration, RS timing, PSSCH timing, PSSCH duration, PSFCH timing, or PSFCH duration.

[0044] In some implementations, a transmission opportunity may describe all the permitted resources on which RS can be transmitted. However, in some cases, user equipment 102 may not transmit RS in every transmission opportunity. In other words, some resources in some transmission opportunities may be used, while resources in other transmission opportunities may not be used. Furthermore, as used herein, RS duration and / or RS timing signify that RS will be transmitted on that transmission opportunity, and accordingly, the resources of that transmission opportunity are being used.

[0045] Furthermore, in some embodiments involving SL positioning for transmitting SL-PRS, the transmitting user equipment 102 may perform one or more of the following actions: The transmitting user equipment 102 may determine a scheme. Additionally or alternatively, the transmitting user equipment 102 may determine one or more grants and corresponding one or more transmission resource pools. Each grant is a set of time-domain and frequency-domain resources for transmitting the SL-PRS. Furthermore, each grant may have one of the following grant types: In a first grant type, the grant is a configuration grant for scheme 1, having CG type 1 and / or CG type 2, and for at least some embodiments, the grant may be associated with a period and / or retransmission opportunity. In a second grant type, the grant is a dynamic grant for scheme 1, and for at least some embodiments, the grant may be associated with a retransmission opportunity. In a third grant type, the grant is a selection grant for scheme 2, and for at least some embodiments, the grant is associated with a period and / or retransmission opportunity.

[0046] Table 1: Characteristics of Dedicated Pools and Shared Pools for Schemes 1 and 2

[0047] Table 1 provides certain characteristics or parameters related to dedicated pools and shared pools for Scheme 1 and Scheme 2.

[0048] For each individual grant (e.g., a PSCCH duration), User Equipment 102 can determine which SL-PRS request to prioritize, and the associated SL-PRS to be prioritized will be transmitted on that individual grant. Furthermore, User Equipment 102 can determine the content of the sidelink control information (SCI) used to schedule the SL-PRS, and transmit the SCI and the SL-PRS (with or without SL data). In any of the various embodiments, these actions can be performed by the transmitting User Equipment's Radio Resource Control (RRC) layer, Media Access Control (MAC) layer, and / or Physical (PHY) layer. Similarly, in any other embodiment of the various embodiments, similar or identical processes can be performed for other reference signals.

[0049] Furthermore, as used herein, the phrase “SL-PRS transmission request” may be used interchangeably with any or all of the following terms: 'SL-PRS', 'SL-PRS transmission', or 'SL-PRS transmission to be sent'. At least in the following contexts, “SL-PRS transmission request” can be used to describe an SL-PRS to be sent, and that the SL-PRS has associated characteristics, and that the SL-PRS request is for sending the corresponding SL-PRS resource at the physical layer SL-PRS transmission timing. Furthermore, different SL-PRS transmission requests for SL-PRS transmission may resemble or correspond to different logical channels used for sidelink data.

[0050] Furthermore, the actions performed in this specification can be applied to any or all types of reference signals (e.g., SL-PRS, sensing RS transmitted in PC5, or other RS) used for transmission on the PC5 interface using a side link. Therefore, SL-PRS is used in this specification as a non-limiting example of an RS, and the actions described herein can be performed for that example. That is, the reference to SL-PRS is intended as a non-limiting example of a reference signal (RS), and other types of reference signals can be used similarly.

[0051] Figure 5This is a flowchart of an example method 500 for wireless communication, which involves a reference signal (RS) transmission opportunity. At block 502, user equipment 102 determines an award in one or more awards allocated for reference signal (RS) resources. At block 504, user equipment 102 determines one or more RS characteristics for each of the one or more RS transmission opportunities in the awards. At block 506, user equipment 102 transmits an RS for each RS transmission duration corresponding to a specific transmission opportunity in the one or more transmission opportunities.

[0052] In some embodiments of method 500, one or more RS characteristics include at least one of the following: RS transmission session, RS transmission priority, RS transmission broadcast type, RS transmission destination information, RS transmission sequence identification (ID), or RS transmission delay budget.

[0053] In some embodiments of method 500, user equipment 102 determines the maximum number of parallel processes that user equipment 102 can determine for more than one authorization to send the RS in a dedicated pool. In some of these embodiments, user equipment 102 determines the maximum number of parallel processes based on resource selection to determine the RS resource allocation.

[0054] In some implementations of method 500, user equipment 102 reports at least one of the following: whether user equipment 102 supports the ability to use parallel processes for a dedicated pool, or the maximum number of parallel processes for a dedicated pool supported by user equipment 102.

[0055] In some embodiments of method 500, user equipment 102 transmits more than one RS resource in a time slot for a dedicated pool.

[0056] In some embodiments of method 500, the one or more RS transmission opportunities include: initial RS transmission opportunities and RS retransmission opportunities, and when the number of unused transmission opportunities in the license in the dedicated pool reaches the configuration parameter, the user equipment 102 reselects the license, wherein the unused transmission opportunities include: initial RS transmission opportunities or RS retransmission opportunities when the corresponding resources are not used for RS.

[0057] In some embodiments of method 500, the one or more RS transmission opportunities include: initial RS transmission opportunities and RS retransmission opportunities, and when the number of unused transmission opportunities in the license in the shared pool reaches the configuration parameter, the user equipment 102 reselects the license, wherein the unused transmission opportunities include: initial RS transmission opportunities or RS retransmission opportunities when the corresponding resources are not used for RS and sidelink data.

[0058] In some embodiments of method 500, the user equipment 102 determines that one or more RS characteristics in each RS transmission opportunity are the same as one or more RS characteristics for the RS transmission with the highest priority among all RS transmissions to be sent.

[0059] In some embodiments of method 500, the user equipment 102 determines that one or more RS characteristics for an RS in each RS transmission opportunity are the same as one or more RS characteristics for an RS transmission with the minimum remaining delay budget (DB) among all RS transmissions to be transmitted.

[0060] In some embodiments of method 500, the one or more RS transmission opportunities include RS retransmission opportunities, and wherein the user equipment 102 determines that one or more RS characteristics for RS in the RS retransmission opportunity are the same as one or more RS characteristics for RS in the corresponding initial RS transmission opportunity.

[0061] In some embodiments of method 500, the one or more RS characteristics include the following characteristic: whether the Media Access Control (MAC) Protocol Data Unit (PDU) transmitted in the same time slot as the RS consists only of padding bits.

[0062] In some implementations of method 500, this feature is indicated in the side-link shared channel (SL-SCH) subheader of the MAC PDU.

[0063] In some embodiments of method 500, this feature is indicated in side link control information (SCI), which includes SCI format 2-D using a source identifier (ID) with 0 bits or 24 bits and a destination identifier (ID) with 0 bits or 24 bits.

[0064] In some embodiments of method 500, the one or more RS characteristics include the characteristic of whether the RS will be transmitted on an RS transmission opportunity.

[0065] In some embodiments of method 500, the user equipment determines the characteristic based on a first number of continuous transmissions and a second number of stopped transmissions. In some of these embodiments, at least one of the following occurs: when a first RS with a priority continuously transmits to a destination in a first number, transmissions by a second RS with the same priority and destined for that destination in a second number are stopped; when a first RS with a priority continuously transmits in a first number within a session, transmissions by a second RS with the same priority in that session in a second number are stopped; the first number of continuous transmissions and the second number of stopped transmissions each include at least one of the following: initial transmission, initial transmission and retransmission, initial transmission to the destination, initial transmission to the destination and retransmission, initial transmission of the session, or initial transmission and retransmission of the session. In some of these embodiments, the initial transmission occurs on an initial transmission opportunity, and the retransmission occurs on a retransmission opportunity.

[0066] In some embodiments of method 500, user equipment 102 determines the one or more RS characteristics based on a first period of continuous transmission and a second period of stopped transmission. In some of these embodiments, at least one of the following conditions exists: when a first RS with a priority continuously transmits to a destination during the first period, transmission by a second RS with that priority and destined for that destination is suspended during the second period; when a first RS with a priority continuously transmits within a session during the first period, transmission by a second RS with that priority within that session is suspended during the second period.

[0067] In some embodiments of method 500, user equipment 102 determines the characteristic based on one of one or more user equipment variables, each of the one or more user equipment variables being associated with a second RS characteristic. In some of these embodiments, the second RS characteristic includes at least one of the destination of the RS transmission or the session of the RS transmission. Additionally or alternatively, at least one of the following occurs: the initial value of the user equipment variable is set to the priority value of the current RS transmission; the user equipment variable value is incremented by one when an RS with the second characteristic is successfully transmitted on an RS transmission opportunity; the user equipment variable value is decremented by one when an RS with the second characteristic is pending transmission but has not been transmitted on that RS transmission opportunity; and the user equipment variable is decremented by one when an RS with the second characteristic is pending transmission but has not been transmitted within a predetermined time period. Additionally or alternatively, user equipment 102 determines that one or more RS characteristics for an RS in each RS transmission opportunity are the same as one or more RS characteristics for an RS transmission with the lowest user equipment variable value among all pending RS transmissions.

[0068] In some embodiments of method 500, one or more RS features include a time interval between two consecutive transmissions, wherein the two consecutive transmissions include at least one of the following: two RSs, a Physical Side Link Control Channel (PSCCH) and an RS, or a Physical Side Link Shared Channel (PSSCH) and an RS. For at least some of these embodiments, there exists at least one of the following: the time interval or maximum time interval between the two consecutive transmissions is configured by a communication node other than the user equipment, wherein the communication node includes a gNB 206 that configures the time interval via Radio Resource Control (RRC) signaling, a Location Management Function (LMF) 202 that configures the time period via Side Link Positioning Protocol (SLPP) signaling or LTE Positioning Protocol (LPP) signaling, or a second user equipment 102 that configures the time period via SLPP signaling or PC5-RRC signaling; or the user equipment reports the minimum time interval between the two consecutive transmissions that the user equipment can use.

[0069] Further details of various actions performed by communication nodes in wireless communication system 100 are now described, any or all of which may be incorporated into any various implementation of method 500 or other methods.

[0070] In some implementations, in time slot n, the MAC layer of a communication node (e.g., user equipment 102 or network device 104) can trigger the physical (PHY) layer to perform resource selection for a dedicated pool for transmitting SL-PRS. Since the time slot pattern for the dedicated pool has already been configured or pre-configured by the network device (e.g., gNB 206), the PHY layer can select one or more SL-PRS resources in the time slot and generate a set of resources selected by the PHY layer. Furthermore, in some implementations, the MAC layer can randomly select a resource from the SA. Accordingly, to select an authorization, the MAC layer can select SL-PRS resources with more than one in a time slot, and / or only one SL-PRS resource in a time slot. Such features may be advantageous (but are not limited to) multi-beam scenarios.

[0071] In addition, in some implementations, the sending user equipment 102 may receive configuration authorization or dynamic authorization from network device 104 (e.g., gNB 206) indicating that more than one SL-PRS resource can be used in a dedicated pool.

[0072] Furthermore, in some implementations, more than one SL-PRS resource may be associated with a single PSCCH within a time slot, or not associated with any PSCCH within a time slot, or each SL-PRS resource may be associated with a corresponding PSCCH within a time slot. Additionally, the PSCCH within a time slot may be frequency division multiplexed (FDM'ed) or time division multiplexed (TDM'ed), and / or the SL-PRS resources within a time slot may be FDM'ed or TDM'ed. Alternatively, the SL-PRS and PSCCH within a time slot may be TDM'ed. Figure 6 This is a timing diagram illustrating an example of the MAC layer selecting more than one SL-PRS within a single time slot.

[0073] In some implementations, the transmitting user equipment 102 may transmit SL-PRS in a time slot within a shared transport resource pool, or transmit SL-PRS and PSSCH together in a time slot.

[0074] In some implementations, when transmitting user equipment 102 transmits SL-PRS and PSSCH within a time slot of a shared transport resource pool, the transmitting user equipment 102 may transmit Level 1 Side Link Control Information (SCI) format 1-A. This SCI format 1-A indicates SCI format 2-D. Accordingly, the transmitting user equipment 102 may transmit Level 2 SCI format 2-D. This SCI format 2-D indicates the SL-PRS resource ID and indicates one or more fields that are identical to those in SCI format 2-A or SCI format 2-B.

[0075] Furthermore, in some embodiments, when the transmitting user equipment 102 transmits only PSSCH in a time slot of a shared transport resource pool, the transmitting user equipment 102 may transmit SCI format 1-A, wherein the SCI format 1-A indicates a second SCI format 2-A, 2-B or 2-C.

[0076] Furthermore, for at least some implementations, the fields in SCI format 1-A are: –Priority–3 bits Frequency resource allocation –Time resource allocation–5 or 9 bits –Resource Retention Period– Bit, –DMRS (Demodulation Reference Signal) pattern– Bit, –Second-level SCI format–2 bits –Beta_offset (Beta offset) indicator – 2 bits, – Number of DMRS ports – 1 bit –Modulation and coding scheme–5 bits, –Additional MCS table indicator – 0, 1, or 2 bits –PSFCH overhead indicator – 1 bit, –Conflict information receiver flag – 0 or 1 bit.

[0077] Furthermore, for at least some implementations, the fields in SCI formats 2-A and 2-B are: –HARQ process ID– 4 bits – New data indicator – 1 bit, – Redundant version – 2 bits, –Source ID–8 bits –Destination ID– 16 bits –HARQ feedback enable / de-enable indicator – 1 bit – Broadcast type indicator – 2 bits –CSI Request– 1 bit, –Field identifier–12 bits, –Communication range requirement–4 bits.

[0078] Additionally, in some implementations, when the transmitting user equipment 102 transmits SL-PRS and PSSCH within a time slot of a shared transport resource pool, it is possible that the PSSCH contains SCI and SL-SCH, but the SL-SCH does not contain actual sidelink data to be transmitted. This means that the Media Access Control (MAC) Protocol Data Unit (PDU) (excluding the SL-SCH subheader) may only include padding bits. Here, sidelink data or actual data refers to the MAC Service Data Unit (SDU) and / or MAC Control Element (CE) containing SL data.

[0079] Furthermore, in some implementations, the transmitting user equipment 102 may know whether the MAC PDU, TB, or PSSCH (which is transmitted in the same time slot as the SL-PRS) contains actual data to be transmitted. However, the receiving user equipment 102 may not know this. In this case, to indicate to the receiving user equipment 102 whether the PSSCH includes actual sidelink data or only includes padding bits, the following actions can be performed.

[0080] Figure 7A schematic diagram of an example structure of a MAC PDU is shown. Figure 8 A schematic diagram of an example structure of the SL-SCH subheader is shown. For at least some implementations, each MAC PDU may have an SL-SCH subheader to indicate the source ID and destination ID information of the MAC PDU. Furthermore, each MAC PDU may include one or more MAC SDUs or MAC CEs. Each MAC SDU or MAC CE has a MAC subheader to indicate the LCID (logical channel identification) and length of the MAC SDU or MAC CE. The transmitting user equipment 102 may use one of the reserved bits (R bits) in the SL-SCH subheader of the MAC PDU to indicate that the MAC PDU includes data, or that all MAC SDUs or MAC CEs in the MAC PDU include only padding bits.

[0081] In this manner, when receiving user equipment 102 receives the SCI 2-D and subsequent MAC PDU, the MAC layer of receiving user equipment 102 can decode the SL-SCH sub-header and locate the field indicating that the MAC PDU includes data. Furthermore, receiving user equipment 102 can continue decoding the MAC PDU and deliver the decoded MAC PDU to the de-assembly and demultiplexing entity of receiving user equipment 102. If the MAC layer of receiving user equipment decodes the SL-SCH sub-header and locates the field indicating that the MAC PDU does not include data, the MAC layer of receiving user equipment 102 can directly ignore or discard the MAC PDU.

[0082] Furthermore, in some implementations, SCI Format 2-D may include two fields. The first field may indicate the source ID of the SL-PRS. The second field may indicate the destination ID of the SL-PRS. The source ID and destination ID can be 0 bits or 24 bits, depending on different conditions. To save SCI overhead, user equipment 102 may not carry a total of 48 bits in every SCI 2-D transmission.

[0083] In an event where the transmitting user equipment 102 confirms that the PSSCH, transmitted in the same time slot as the SL-PRS, contains actual data to be sent, the transmitting user equipment 102 may set the source ID field of the SL-PRS to 0 bits and the destination ID field of the SL-PRS to 0 bits. Furthermore, when the receiving user equipment 102 receives an SCI 2-D with both fields set to 0 bits, the receiving user equipment 102 can know or determine that the PSSCH actually includes the data to be transmitted, and that the data receiving user equipment 102 intends to receive and process. In some embodiments, the SL-PRS and PSSCH in a time slot have the same destination ID and source ID. In such embodiments, the receiving user equipment 102 may simultaneously receive and decode the PSSCH containing SCI 2-D information and the SL-SCH subheader, and receive and process the SL-PRS.

[0084] Furthermore, in the event that the transmitting user equipment 102 confirms that there is no actual data to be transmitted in the PSSCH sent together with the SL-PRS in the same time slot, the transmitting user equipment 102 can configure the SCI 2-D to include a 24-bit source ID and a 24-bit destination ID for the SL-PRS. When the receiving user equipment 102 receives the SCI 2-D, both fields being 24 bits, the receiving user equipment 102 can know that this PSSCH only contains padding bits. Therefore, the receiving user equipment 102 can skip the reception and decoding process of this PSSCH. Additionally, the receiving user equipment 102 can use the 24-bit source ID and destination ID in the SCI 2-D to confirm whether the SL-PRS in this time slot will be received by the receiving user equipment 102.

[0085] The following describes how user equipment 102 can determine one or more characteristics of SL-PRS transmission at each transmission opportunity. Such methods can be applied to shared pools and dedicated pools, and / or to schemes 1 and 2.

[0086] Furthermore, in some embodiments, user equipment 102 may determine one or more grants for transmitting SL-PRS. A grant may include non-periodic reserved resources and / or periodic reserved resources. Each non-periodic reserved resource and / or periodic reserved resource may be mapped to and / or associated with a PSCCH duration or SL-PRS transmission timing / SL-PRS transmission opportunity. Each non-periodic reserved resource and / or periodic reserved resource in a grant may also be referred to as a single grant within that grant. Furthermore, each first transmission opportunity for each periodic reservation is referred to as an initial transmission opportunity, while other single grants within this grant may be referred to as retransmission opportunities.

[0087] Furthermore, in some implementations, authorization is at least one of configured authorization, dynamic authorization, or selective authorization. When the transmitting user equipment 102 has received an SL-PRS transmission request from an upper layer (e.g., a layer higher than the MAC layer) or from another user equipment 102, or when the transmitting user equipment 102 generates an SL-PRS transmission request at its own MAC layer, since multiple SL-PRS transmission requests may arrive at once, the transmitting user equipment 102 can determine which SL-PRS transmission requests(s) to satisfy, and the corresponding SL-PRS will be transmitted on each individual authorization. In other words, the MAC layer of the transmitting user equipment 102 may be triggered by one or more SL-PRS transmissions to be transmitted.

[0088] In addition, each SL-PRS transmission request may be associated with at least one of the following: an SL-PRS transmission request ID, which is an identifier of the SL-PRS transmission to be sent; a different session, such as an SL positioning session or another session of other services (a session may have an SL positioning session ID, an LPP session ID, or another session ID); a priority value associated with the SL-PRS, the SL positioning session, or the SL-PRS transmission request; a broadcast type (e.g., broadcast, multicast, unicast); a delay budget (DB), such as the remaining DB associated with the SL-PRS, the SL positioning session, or the SL-PRS transmission request; destination information associated with the SL-PRS, the SL positioning session, the SL-PRS transmission request, or the destination ID; the number of retransmissions; the period of the SL-PRS transmission; or a sequence ID used to send the corresponding SL-PRS.

[0089] In addition, each SL-PRS transmission may have one or more of the characteristics described above associated with the SL-PRS transmission request. Other or additional characteristics of SL-PRS may include at least one of the following: whether the SL-PRS transmission is performed on a transmission opportunity; whether the MAC PDU transmitted in the same time slot as the SL-PRS consists only of padding bits; or the time interval between two consecutive transmissions.

[0090] Furthermore, in some implementations, each individual grant may correspond to one SL-PRS resource and one corresponding PSCCH in a time slot, or each individual grant may correspond to one SL-PRS resource in a time slot. A time slot may have one or more individual grants. In the first case, if a user equipment 102 is only permitted to transmit one PSCCH and one corresponding SL-PRS resource in one time slot, then each individual grant may include one PSCCH and one corresponding SL-PRS resource in one time slot. Accordingly, user equipment 102 may transmit only one SL-PRS corresponding to a single SL-PRS transmission request in one time slot. The SL-PRS and the corresponding PSCCH are time-division multiplexed within the time slot. In the second case, if a user equipment 102 is permitted to transmit more than one SL-PRS resource in one time slot, then a time slot may have multiple individual grants. Accordingly, user equipment 102 may transmit multiple SL-PRS corresponding to multiple SL-PRS transmission requests in one time slot.

[0091] In both of the above scenarios, if multiple SL-PRS transmission requests arrive in each single grant (i.e., the corresponding SL-PRS is to be sent), the transmitting user equipment 102 can determine or select which SL-PRS transmission request to satisfy and the corresponding SL-PRS to be sent on each single grant according to at least one of the following configurations (i.e., the transmitting user equipment 102 determines the characteristics of the SL-PRS transmission on a single grant according to at least one of the following configurations).

[0092] In the first configuration, user equipment 102 can select the SL-PRS transmission request with the highest priority. That is, the sending user equipment 102 can determine that the SL-PRS transmission characteristics on each transmission opportunity are the same as those of the SL-PRS transmission with the highest priority at that time. A transmission opportunity can be at least one of an initial transmission opportunity or a retransmission opportunity. The SL-PRS transmission with the highest priority at that time can include: the SL-PRS transmission with the highest priority among all pending transmissions and which are currently included in priority ordering or LCP, or the SL-PRS transmission with the highest priority among all pending transmissions at that time. As used herein, a transmission included in priority ordering or LCP means that the transmission can be selected for, or is permitted to be selected for, transmission within a transmission opportunity, or can be multiplexed in, or is permitted to be multiplexed in a MAC PDU for transmission within a transmission opportunity. For at least some implementations, communication nodes in wireless communication system 100 may operate according to certain specifications or rules, and these specifications or rules prohibit one or more of the transmissions from being sent in one or more of the transmission opportunities, wherein the transmissions can or are permitted to be selected or multiplexed in a MAC PDU for transmission in the transmission opportunity.

[0093] In the second configuration, user equipment 102 can select an SL-PRS transmission request with the minimum remaining DB. That is, the sending user equipment 102 determines that the SL-PRS transmission characteristics on each transmission opportunity are the same as those of the SL-PRS transmission with the minimum remaining DB at that time. A transmission opportunity can be at least one of an initial transmission opportunity or a retransmission opportunity. The SL-PRS transmission with the minimum remaining DB at that time can include: the SL-PRS transmission with the minimum remaining DB among all pending transmissions and those currently included in priority ordering or LCP, or the SL-PRS transmission with the minimum remaining DB among all pending transmissions at that time.

[0094] In the third configuration, if the same SL-PRS transmission request in the corresponding initial transmission opportunity time is still available, user equipment 102 can select the SL-PRS transmission request in the retransmission opportunity as the same SL-PRS transmission request in the corresponding initial transmission opportunity time, wherein the SL-PRS transmission request in the initial transmission opportunity is the same as the SL-PRS transmission request in the retransmission opportunity, and at least one of their respective characteristics is the same. On the other hand, if the SL-PRS transmission request corresponding to the initial transmission opportunity is not available at this time, user equipment 101 can select any SL-PRS transmission request. For the initial transmission opportunity, user equipment 102 can select any SL-PRS transmission request. That is, the sending user equipment 102 can determine that the SL-PRS transmission characteristics in the retransmission opportunity are the same as the SL-PRS transmission characteristics in the corresponding initial transmission opportunity. Accordingly, user equipment 102 can determine the characteristics of the new transmission in the new transmission opportunity based on the characteristics of one or more of the SL-PRS transmissions to be sent, which have the highest priority or the smallest remaining DB.

[0095] In cases where user equipment 102 is allowed to send more than one SL-PRS resource in a time slot or in other implementations, user equipment 102 may determine or select which SL-PRS transmission request to satisfy and the corresponding SL-PRS to be transmitted in each time slot according to at least one of the following processes (i.e., user equipment 102 may determine one or more characteristics of more than one SL-PRS transmission in a time slot according to at least one of the following processes).

[0096] In the first process, User Equipment 102 can determine the destination and broadcast type of the SL-PRS transmission request with the highest priority and select that SL-PRS transmission request. In the second process, User Equipment 102 can determine one or more SL-PRS transmission requests with the same destination and broadcast type as the selected SL-PRS transmission request, based on the remaining DB and the number of single grants in a time slot. In the third process, User Equipment 102 can send one or more SL-PRS transmissions in a time slot based on the selected SL-PRS transmission request.

[0097] Figure 9 A schematic timing diagram is shown for an example of user equipment 102 selecting SL-PRS for transmission. Furthermore, the UL MAC CE used to request DG (dynamic grant) resources may include a preference for resource pools (e.g., a shared pool or a dedicated pool). Additionally, the UL RRC message used to request CG resources may include a preference for resource pools (e.g., a shared pool or a dedicated pool).

[0098] In some implementations, including those applicable to dedicated pools and / or shared pools, and / or those applicable to Scheme 1 and / or Scheme 2, the authorization may include at least one of the following: configuration authorization, dynamic authorization, and / or selection authorization. The authorization may be an authorization with non-periodic reserved resources, or an authorization with both non-periodic and periodic reserved resources.

[0099] In events where user equipment 102 has determined an authorization to send an SL-PRS, and where user equipment 102 selects to send the SL-PRS with the highest priority in each individual authorization, the SL-PRS request with the highest priority may be continuously sent. In such cases, SL-PRS with lower priority may not have a chance to be sent, and SL positioning may fail frequently. To prevent failures, a priority rule for sending SL-PRS is implemented. For at least some implementations, this priority rule can be applied to both new transmission opportunities and retransmission opportunities. Alternatively, the priority rule can be applied only whenever a new transmission is performed.

[0100] For an SL-PRS transmission request or at least one of broadcast, multicast, and / or unicast of an SL-PRS, the transmitting user equipment 102 may use the authorization to send the SL-PRS to multiple destinations. If for a destination there are more than one SL positioning session and each SL-PRS transmission request is associated with a priority, then to ensure that lower-priority SL-PRS also have a chance to be sent to that destination, at least one of the following configurations may be implemented (or in other words, user equipment 102 may have multiple SL positioning sessions simultaneously, and for each SL positioning session there may be multiple SL-PRS transmission requests associated with one SL positioning session). If for a sidelink positioning session each SL-PRS transmission request is associated with a priority, then to ensure that lower-priority SL-PRS also have a chance to be sent for that sidelink positioning session, then at least one of the following configurations may be implemented.

[0101] In the first configuration, each SL-PRS priority can be associated with a first number X consecutive transmissions. Furthermore, each SL-PRS priority can be associated with a second number Y of stopped transmissions. User equipment 102 can count according to the following rule: if an SL-PRS transmission request with a priority for a certain destination ID has been satisfied, and the corresponding SL-PRS with that priority has been continuously sent to that specific destination ID X times or X single grants, then that priority should be suspended Y times or Y single grants. That is, for a specific destination ID, user equipment 102 may not select SL-PRS requests with that priority, and will not send SL-PRS with that priority for Y times. Other implementations may employ the same first configuration, but use or be applicable to specific sidelink location session IDs instead of specific destination IDs. Similarly, suspending or stopping Y times may include: SL-PRS transmissions with a certain priority that are to be sent to a certain destination or session will not be included in the priority ordering of these Y times, even if these SL-PRS transmissions are still waiting to be sent in the next few transmission opportunities.

[0102] In the second configuration, the counted X consecutive transmissions include only the initial transmission, or both the initial transmission and retransmissions. Similarly, the counted Y stopped transmissions include either the initial transmissions that were not sent, or both the initial transmissions that were not sent and retransmissions. For some implementations of the second configuration, the counted X consecutive transmissions include only the initial transmissions for a specific destination or a specific SL positioning session, or only the initial transmissions and retransmissions for a specific destination or a specific SL positioning session. Similarly, the Y stopped transmissions counted as not sent include either Y initial transmissions for a specific destination or a specific SL positioning session, or both Y initial transmissions and retransmissions for a specific destination or a specific SL positioning session.

[0103] In the third configuration, each SL-PRS priority can be associated with a first time period A, and each SL-PRS priority can be associated with a second time period B. User equipment 102 can count if an SL-PRS transmission request with a priority for a certain destination ID has been satisfied, and corresponding SL-PRS with that priority are continuously sent to that destination ID, and the transmission time reaches the first time period A (calculated from the first time an SL-PRS with that priority is sent to that destination ID), then user equipment 102 can stop sending SL-PRS with that priority to that destination ID during the second time period B. In other embodiments, similar actions can be performed according to the third configuration, but for a specific sidelink location ID rather than a specific destination ID. Furthermore, pausing or stopping during time period B includes: the SL-PRS transmission to be sent is not part of the priority sorting process within time period B.

[0104] In the fourth configuration, each SL-PRS priority can be associated with a first number X consecutive transmissions. Furthermore, each SL-PRS priority can be associated with a second time period B. If an SL-PRS transmission request with a priority for a specific destination ID has been satisfied, and the corresponding SL-PRS with that priority has been continuously sent to that destination ID X times or X single grants, then the user equipment 102 can stop sending SL-PRS with that priority to that destination ID during the second time period B. In other implementations, similar actions can be performed according to the fourth configuration, but targeting a session ID on a particular side link instead of a specific destination ID.

[0105] Furthermore, in any of the various implementations, the aforementioned associations between priorities and counts X, Y, time period A, and / or time period B can be configured by Radio Resource Control (RRC) signaling from network device 104 (e.g., gNB 206) to transmitting user equipment 102. Alternatively, the associations can be configured per resource pool or per user equipment 102. Alternatively, the aforementioned associations between priorities and counts X, Y, time period A, and / or time period B can also be configured by SLPP signaling from LMF 202 to transmitting user equipment 102, or from another user equipment 102 (e.g., server user equipment 102) to transmitting user equipment 102. Alternatively, the associations between priorities and counts X, Y, time period A, and / or time period B can be pre-configured or fixed in the specification. Alternatively or additionally, the association between priority and count X, count Y, time period A, and / or time period B may be included in the UE capability report of LMF 202, gNB 206, or another user equipment 102. Alternatively or additionally, count X and / or count Y may each be an integer greater than 0. Alternatively or additionally, the unit for each of time period A and / or time period B may be at least one of a symbol, time slot, sub-time slot, subframe, radio frame, millisecond, or second. Figure 10 A schematic diagram illustrating the priority of transmission control is shown.

[0106] Furthermore, in some implementations, for a shared pool, when user equipment 102 has data from the sidelink control channel (SCCH), data from the sidelink traffic channel (STCH), or sidelink MAC CEs to be transmitted, their priorities are in the following constrained order: Logical channels are prioritized in the following order (highest priority listed first): -Data from SCCH; - Side link CSI report MAC CE; - Sidelink UE-to-UE Coordination Request (MAC CE) and Sidelink UE-to-UE Coordination Information (MAC CE); - Side-link DRX (Discontinuous Reception) command MAC CE; - Data from any STCH.

[0107] Furthermore, in some implementations, when SL-PRS is included in the priority ordering, SL-PRS may not be prioritized higher than data from STCH and SL MAC CE. Accordingly, when in a shared pool, the MAC layer / entity of user equipment 102 can choose to transmit to the same destination as the pending transmission with the highest priority, or the MAC layer / entity of user equipment 102 can determine whether to transmit SL-PRS on a transmission opportunity based on the priority order. The priority order from highest to lowest should be: data from SCCH, SL MAC CE, data from STCH, and SL-PRS (depending on the configured priority). In this way, the priority of data from STCH is compared together with the priority of SL-PRS. If the priorities configured for data from STCH and SL-PRS have the same configured priority value, the destination can be determined based on the specific implementation.

[0108] In other implementations, the priority order from highest to lowest may be: data from SCCH, SL MACCE, data from STCH, and SL-PRS.

[0109] Furthermore, in some implementations, the logical channels including data from the SCCH and the sidelink MAC CE generated by the MAC layer can have fixed priority values. Similarly, data from the STCH and the SL-PRS can each have their own configurable priority values.

[0110] Additionally, some implementations may utilize a user equipment variable (also known as a UE variable) Z to control the selection of the SL-PRS. For at least some of these implementations, each SL-PRS transmission request may maintain or include a UE variable Z. Different SL-PRS transmission requests may maintain or include a corresponding UE variable Z independently and / or in parallel. The UE variable Z may have the same value range (e.g., eight levels) as the priority value of the SL-PRS (e.g., 0-7 or 1-8). In particular, in these implementations, unless explicitly stated otherwise, as used herein, the lowest priority value represents the highest priority, and vice versa. For the priority value range of 0-7, if Z decreases to 0, Z cannot decrease further. Similarly, if Z increases to 7, Z cannot increase further. Likewise, for the priority value range of 1-8, Z cannot decrease to a value less than 1, nor can it increase to a value greater than 8. Furthermore, for at least some implementations, user equipment 102 may set an initial Z value as the priority value of the current SL-PRS transmission request. In particular, in these embodiments, user equipment 102 can select (e.g., always select) the SL-PRS transmission request with the lowest Z value in each individual grant. If different SL-PRS transmission requests have the same Z value at a given time, user equipment 102 can select the SL-PRS transmission request, which may depend on the specific implementation of any of the various embodiments.

[0111] Similarly, in some implementations, at least one of the following methods can be used to determine whether two or more SL-PRS transmission requests can be identified as the same SL-PRS transmission requests with the same UE variable Z. In a first method, if the two or more SL-PRS transmission requests arrive at different times, then the two or more SL-PRS transmission requests are not identified as the same SL-PRS transmission requests. Accordingly, the user equipment 102 determines to apply independent or individual UE variables Z to the two or more SL-PRS transmission requests. In a second method, if the two or more SL-PRS transmission requests arrive at different times but have the same associated destination information, the user equipment 102 can determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission requests. Accordingly, the user equipment 102 can determine to apply the same UE variable Z to the two or more SL-PRS transmission requests. In the third approach, if two or more SL-PRS transmission requests arrive at different times and have the same associated sidelink location session information, then user equipment 102 can determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission requests. Accordingly, user equipment 102 can apply the same UE variable Z to the two or more SL-PRS transmission requests. In the fourth approach, if two or more SL-PRS transmission requests arrive at different times and have the same associated SL-PRS transmission request ID, then user equipment 102 can determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission requests. Accordingly, user equipment 102 can apply the same UE variable Z to the two or more SL-PRS transmission requests. In the fifth approach, if the two or more SL-PRS transmission requests arrive at different times but have the same associated broadcast type, user equipment 102 can determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission requests. Accordingly, user equipment 102 can apply the same UE variable Z to these two or more SL-PRS transmission requests. In the sixth approach, if the two or more SL-PRS transmission requests arrive at different times but have the same associated retransmission count, user equipment 102 can determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission request. Accordingly, user equipment 102 can apply the same UE variable Z to these two or more SL-PRS transmission requests.In the seventh approach, if two or more SL-PRS transmissions arrive at different times and have the same associated SL-PRS transmission priority, then user equipment 102 can determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission request. Accordingly, user equipment 102 can apply the same UE variable Z to the two or more SL-PRS transmission requests. In the eighth approach, if two or more SL-PRS transmission requests arrive at different times but have the same associated sequence ID for sending the corresponding SL-PRS, then user equipment 102 can determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission request. Accordingly, user equipment 102 can apply the same UE variable Z to the two or more SL-PRS transmission requests. In the ninth approach, if two or more SL-PRS transmission requests arrive at different times but have the same associated delay budget (DB) or remaining DB, then user equipment 102 can determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission request. Accordingly, user equipment 102 may apply the same UE variable Z to these two or more SL-PRS transmission requests. In the tenth mode, if the two or more SL-PRS transmission requests arrive at different times but have the same associated priority, user equipment 102 may determine that the two or more SL-PRS transmission requests are the same SL-PRS transmission request. Accordingly, user equipment 102 may apply the same UE variable Z to these two or more SL-PRS transmission requests.

[0112] Furthermore, in some implementations, for each SL-PRS transmission request with the same UE variable Z, the user equipment 102 may execute one or more of the following processes. In a first process, if an SL-PRS transmission request has been selected and the corresponding SL-PRS has been sent for a single grant, the corresponding UE variable Z is incremented by 1. Accordingly, when the next SL-PRS transmission request with the same UE variable Z arrives, the UE variable Z is incremented by 1, i.e., Znew = Zold + 1. In a second process, if an SL-PRS transmission request is waiting to be sent but has not been sent within a specific time, the corresponding UE variable Z is decremented by 1. Accordingly, when the next SL-PRS transmission request with the same UE variable Z waits for that specific time, the UE variable Z is decremented by 1, i.e., Znew = Zold - 1. Furthermore, in some implementations, this specific time may be a specific time period in units of at least one of symbols, time slots, milliseconds, subframes, radio frames, or seconds. Alternatively, this specific time may be a specific number of single grants that have not been sent for that SL-PRS transmission request. Alternatively, this specific time may be configured by another communication node, or it may be determined by the sending user equipment 102 itself, or it may be predefined in the specification.

[0113] Furthermore, in some implementations that include sidelink positioning, a user equipment 102 may be simultaneously in different sidelink positioning sessions. For example, the user equipment 102 may act as different UE roles in different sidelink positioning sessions. Each sidelink positioning session may be associated with at least one sidelink positioning quality of service (QoS) requirement. Accordingly, the user equipment 102 may need to send multiple SL-PRS to satisfy multiple SL-PRS transmission requests corresponding to multiple QoS requirements of multiple SL positioning services.

[0114] Furthermore, in some implementations, a dedicated resource pool may be used solely for transmitting SL-PRS and the corresponding PSCCH. If User Equipment 102 is scheduled and / or configured to transmit in a dedicated pool, and if User Equipment 102 can only use one grant, it may be impossible or inefficient to satisfy multiple SL-PRS transmission requests corresponding to multiple SL-PRS to be transmitted using only one grant with multiple retransmissions and a single cycle. On the other hand, in other implementations, it may be more efficient for User Equipment 102 to use parallel processes to determine grants and transmit SL-PRS in a dedicated resource pool. For at least some of these other implementations, each process in the parallel process is associated with one grant. Such parallel processes may not include SL processes that process SL data. Additionally or alternatively, such parallel processes may be performed by the MAC layer / entity of the transmitting User Equipment 102.

[0115] Additionally, in some implementations, one or more of the following configurations can be implemented. In a first configuration, user equipment 102 can determine the maximum number of parallel processes X that user equipment 102 can use to perform SL-PRS transmission on a dedicated pool. In a second configuration, user equipment 102 can determine the maximum number of parallel processes Y that user equipment 102 can use to perform SL-PRS transmission on a dedicated pool using scheme 2. In a third configuration, for scheme 1 and the dedicated resource pool, user equipment 102 can be configured with one or more CG configurations for SL-PRS transmission. In at least some implementations of the third process, the mapping between one or more CG configurations (e.g., provided by network device 104) and X parallel processes (e.g., maintained by the MAC layer / entity of the sending user equipment 102) can be configured by network 104 or can be calculated by the sending user equipment 102 itself. In a fourth configuration, for scheme 2 and the dedicated resource pool, user equipment 102 can select an authorization for each of the Y parallel processes. In a fifth configuration, user equipment 102 can determine the maximum number of parallel processes Y1 that user equipment 102 can use to perform SL-PRS transmission using scheme 2. At least some implementations of the fifth configuration can be applied to at least one of the following: a dedicated pool and a shared pool; or only a shared pool. In the sixth configuration, user equipment 102 can determine the maximum number of parallel processes Z that user equipment 102 can use to perform SL-PRS transmissions together with sidelink data. In the seventh configuration, user equipment 102 can determine the maximum number of parallel processes Z1 that user equipment 102 can use to perform SL-PRS transmissions together with sidelink data using scheme 2.

[0116] Additionally, in some implementations, User Equipment 102 may report whether it supports the UE capability to use parallel processes in a shared pool or a dedicated pool. Alternatively, User Equipment 102 may report whether it supports the UE capability to use parallel processes for Scheme 2 in a shared pool or a dedicated pool. Alternatively, User Equipment 102 may report whether it supports the UE capability to transmit SL-PRS simultaneously in both the dedicated pool and the shared pool. Alternatively, User Equipment 102 may report whether it supports the UE capability to transmit SL-PRS simultaneously for Scheme 2 in both the dedicated pool and the shared pool. The UE may report whether it supports the UE capability to use parallel processes for Scheme 2 in both the dedicated pool and the shared pool. Alternatively, User Equipment 102 may report whether it supports and / or supports X parallel processes, Y parallel processes, Y1 parallel processes, Z parallel processes, and / or Z1 parallel processes. Alternatively or additionally, one or more of the values ​​X, Y, Y1, Z, and Z1 may be configured by a communication node other than the transmitting user equipment 102, or may be predefined or fixed in the specification. Alternatively or additionally, each of the values ​​X, Y, Y1, Z, and Z1 for the number of parallel processes may be an integer greater than 0. Alternatively or additionally, Z may be up to 16, and Z1 may be up to 4.

[0117] Furthermore, in some implementations of user equipment 102 configured according to scheme 2, for sending SL-PRS using both a shared pool and a dedicated pool, user equipment 102 may perform a transmit (Tx) resource (re)selection check at one or more times or instances to determine whether to ignore or discard the old grant and select a new grant. If the MAC layer of the user equipment determines that SL-PRS is not to be sent in the dedicated pool, the grant may be ignored, discarded, or cleared by the MAC layer of user equipment 102.

[0118] For a dedicated pool, the Tx resource selection check can be performed on a per-selected authorized process. In some cases, user equipment 102 can employ one or more parallel processes for dedicated pool resource selection. For a shared pool, the Tx resource (re)selection check process can be per SL process.

[0119] Furthermore, in some implementations, for at least one of the dedicated pool and the shared pool, a parameter can be used to indicate the number of times a transmission opportunity has not been used, after which the selected grant can be discarded by the MAC layer. A transmission opportunity can include at least one of an initial transmission opportunity or a retransmission opportunity. For example, user equipment 102 can count the number of unused transmission opportunities, including unused initial transmission opportunities and unused retransmission opportunities. In other words, the number of unused transmission opportunities on the resource indicated in the selected sidelink grant increments by 1 when each individual grant in the resource reservation interval is not used. Initial transmission opportunities and retransmission opportunities can be sent periodically or aperiodically in any of the various implementations.

[0120] Furthermore, in some implementations for dedicated pools, a transmission opportunity not being used includes the SL-PRS not being sent on that transmission opportunity. Additionally, in some implementations for shared pools, a transmission opportunity not being used includes neither SL data nor SL-PRS being sent on that transmission opportunity. This is because for shared pools, if data is sent on the initial transmission opportunity, the data in the retransmission should be the same as the data on the initial transmission opportunity. However, SL-PRS can be sent on either the initial transmission opportunity or the retransmission opportunity. Conversely, if data is not sent multiple times, and the number reaches an indicated parameter value, SL-PRS can still be sent using the license. Therefore, the license may not be released in this case.

[0121] Alternatively, this parameter can be configured individually by other communication nodes, such as gNB 206 (e.g., via RRC signaling), LMF 202 (e.g., via SLPP or LPP signaling), or another user equipment 102 (e.g., via SLPP or PC5-RRC signaling). Alternatively, when using DL RRC signaling, this parameter is an integer, while in some implementations, it may use a specific M code and / or be configured in the Mode 2 / Scheme 2 configuration of each user equipment 102. Alternatively, this parameter can reuse SL-ReselectAfterIE (SL Reselect After IE (information element)) according to various wireless communication protocols or standards. Alternatively, in some shared pool implementations, the number of unused transmission opportunities on the resources indicated in the selected sidelink grant can be increased by 1 when each individual grant in the resource reservation interval is unused. Each individual grant is used to transmit data and SL-PRS. When SL-PRS is included, User Equipment 102 may not be able to achieve the sl-ReselectAfter value in some implementations because, at least in some cases, SL-PRS and data rarely remain silent for multiple consecutive resource reservation intervals. Conversely, if no single grant is used for a resource reservation interval (or multiple intervals), and the number of unused transmission opportunities on the resources indicated in the selected sidelink grant increases by 1, User Equipment 102 may require a relatively long time to switch grants.

[0122] Furthermore, in some implementations of at least one of the dedicated pool or shared pool, if multiple SL-PRS transmission requests lasting for a specific period exist, user equipment 102 can release the old license and select a new license. A new license can be selected to maintain a shorter period to accommodate multiple SL-PRS transmission requests.

[0123] Furthermore, in some shared pool implementations, if the selected resource pool is configured with HARQ feedback, the transmitting user equipment 102 can monitor and / or receive HARQ feedback from the receiving user equipment after transmitting SL data. However, in some cases, SL-PRS transmitted in this shared pool may not have HARQ feedback. Additionally or alternatively, in some cases, no SL data may be available, which in turn may cause the MAC layer / entity to generate a MAC PDU with empty data. In this case, HARQ feedback may not be required. To reduce or conserve feedback resources, a shared pool with HARQ feedback may not be used, and the user equipment 102 may trigger an authorization selection process in this SL process and change the resource pool.

[0124] Furthermore, in some implementations, when User Equipment 102 selects authorization in a shared pool with HARQ feedback and selects the number of retransmissions only when considering SL data, or when User Equipment 102 is configured with a maximum number of retransmissions in configured authorization or dynamic authorization, if User Equipment 102 receives positive HARQ feedback, User Equipment 102 may stop the remaining retransmissions of SL data, thus wasting remaining retransmission opportunities because SL-PRS may not be sent on these retransmission opportunities. To avoid wasting retransmission opportunities, one or more of the following processes can be performed.

[0125] In the first process, if User Equipment 102 needs to select the number of retransmissions, its MAC layer / entity can select the number of retransmissions by considering the sidelink data waiting to be sent. Furthermore, to avoid wasting retransmission opportunities, even if User Equipment 102 receives a positive acknowledgment feedback from the MAC PDU and stops retransmitting sidelink data, User Equipment 102 may still send SL-PRS within the retransmission opportunities associated with this SL process and shared pool in this authorization. That is, regardless of whether User Equipment 102 receives a positive or negative acknowledgment feedback from the MAC PDU, or receives no feedback at all, User Equipment 102 may still send SL-PRS within the retransmission opportunities associated with this SL process and shared pool in this authorization. User Equipment 102 may also send SL-SCH without data along with SL-PRS in the remaining retransmission opportunities.

[0126] Alternatively, when selecting the number of retransmissions during the authorization selection process, the MAC layer / entity of user equipment 102 can select two retransmission counts. The first retransmission count can be used for SL data in the logical channel. The second retransmission count can be used for SL-PRS. Alternatively, in any embodiment of the various embodiments, the maximum set of retransmission counts for SL-PRS can be configured separately or individually by communication nodes other than the transmitting user equipment 102.

[0127] Furthermore, in some implementations, there is no HARQ feedback for SL-PRS reception in a dedicated pool. Accordingly, when transmitting user equipment 102 selects an SL-PRS resource for non-periodic reservation, transmitting user equipment 102 is not required to ensure that the minimum time between any two selected SL-PRS resources is equal to the time required to receive and process the PSFCH. However, transmitting user equipment 102 may need to ensure that the SL-PRS resource selected for non-periodic reservation is indicated by a prior SCI.

[0128] Furthermore, in some implementations, in a shared pool or dedicated pool, there may be situations where user equipment 102 cannot continuously transmit two transmissions without time interval, for example, when different transmissions correspond to multiple transmission beams. Alternatively, in some implementations, one or more configurations can be implemented regarding the time interval between two transmissions. In a first configuration, the time interval between two consecutive transmissions can be configured individually by other communication nodes, such as gNB 206 (e.g., via RRC signaling), LMF 202 (e.g., via SLPP or LPP signaling), or another user equipment 102 (e.g., via SLPP or PC5-RRC signaling). In a second configuration, the maximum time interval between two consecutive transmissions can be fixed, or predefined according to the wireless communication specifications or standards followed by the communication nodes in the wireless communication system 100. In a third configuration, the minimum time interval between two consecutive transmissions can be fixed, or predefined according to the wireless communication specifications or standards followed by the communication nodes in the wireless communication system 100. In a fourth configuration, user equipment 102 can report the UE capability of the minimum time interval between two consecutive transmissions. Similarly, for at least some of these embodiments, two consecutive transmissions may include at least one of the following: two consecutive SL-PRS transmissions, two consecutive PSCCH and SL-PRS transmissions, two consecutive PSSCH and SL-PRS transmissions, or two consecutive PSFCH and SL-PRS transmissions. Additionally or alternatively, in various embodiments, the SL-PRS may also be any reference signal transmitted in PC5. Additionally or alternatively, for two consecutive transmissions including PSCCH and SL-PRS transmissions, the associated SL-PRS resource may be the SL-PRS resource scheduled by the SCI in the PSCCH, or the SL-PRS resource may be any SL-PRS resource closest to the SCI in the PSCCH.

[0129] Furthermore, in some implementations, each SLPP session ID can be associated with a specific sidelink location session with specific QoS requirements. An SLPP message can indicate or convey an SLPP session ID. When SLPP messages are delivered between UE 102 and LMF 202, similar to LPP messages, the SLPP message can also be embedded in a NAS message. In this way, LMF 202, the access and mobility management function (AMF), and the target UE 102 can still use the location service (LCS) association ID and routing ID to distinguish different SL location sessions. That is, the SLPP session ID is transparent to LMF 202 and AMF. Therefore, when SLPP messages are transmitted between UE 102 and LMF 202, there is no need to expose or indicate the SLPP session ID to LMF 202.

[0130] Furthermore, in some implementations, when target user equipment 102 receives a service request with a route ID, since different route IDs represent different location sessions with different QoS, target user equipment 102 can assign an SLPP session ID with a one-to-one mapping relationship to the received route ID. That is, if target user equipment 102 receives two route IDs simultaneously, the assigned SLPP session ID may also include two different IDs instead of one. However, a mechanism to restrict which route ID is associated with which SLPP session ID may not be necessary. Instead, for at least some implementations, target user equipment 102 can ensure that there are no overlapping session IDs during each sidelink location session.

[0131] Furthermore, in some embodiments, for a location request initiated by at least one sidelink mobile terminal (SL-MT-LR), a location request initiated by a sidelink mobile station (SL-MO-LR), LMF-based location, or UE-based location, LMF 202 may request gNB 206 to configure at least one of the following information to user equipment 102, or LMF 202 may recommend at least one of the following resource allocation configurations to gNB 206: preference for using a shared pool or a dedicated pool; dedicated pool configuration, including the frequency domain configuration and / or time domain configuration of the dedicated pool; number of SL-PRS symbols; SL-PRS comb size; SL-PRS comb offset; SL-PRS bandwidth; number of SL-PRS repetitions; number of SL-PRS retransmissions; SL-PRS period; or SL-PRS priority. Additionally, for at least some implementations, gNB 206 may determine one or more final resource allocation configurations and provide them to LMF 206. In other implementations, the above actions can be transmitted in NR Positioning Protocol A (NRPPa) messages or Next Generation Application Protocol (NGAP) messages.

[0132] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter can be implemented in a variety of different forms, and therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the example embodiments set forth herein. A reasonably broad scope is intended for the claimed or covered subject matter. In particular, for example, the subject matter can be implemented as a method, apparatus, component, system, or non-transitory computer-readable medium for storing computer code. Thus, embodiments can take the form of, for example, hardware, software, firmware, storage medium, or any combination thereof. For example, the above-described method embodiments can be implemented by a component, apparatus, or system including a memory and a processor by executing computer code stored in the memory.

[0133] Throughout the specification and claims, terms may have nuanced meanings beyond those explicitly stated, implied or suggested in the context. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include, in whole or in part, combinations of exemplary embodiments.

[0134] Generally, terms can be understood at least in part based on their use in context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings that can depend at least in part on the context in which they are used. Typically, “or,” when used to associate a list such as A, B, or C, is intended to mean A, B, and C (inclusive meaning) and A, B, or C (exclusive meaning). Furthermore, depending at least in part on the context, the term “one or more,” as used herein, can be used to describe any feature, structure, or characteristic in a singular sense, or a combination of features, structures, or characteristics in a plural sense. Similarly, depending at least in part on the context, terms such as “a,” “an,” or “the” can be understood to convey either a singular or a plural usage. Moreover, the term “based on” can be understood to not necessarily convey an exclusive set of factors, and conversely, again depending at least in part on the context, may allow for additional factors that are not necessarily explicitly described.

[0135] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable using this solution should be included or are all included in any single implementation thereof. Rather, the language referring to features and advantages is to be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, the discussion of features and advantages, and similar language throughout this specification, may, but do not necessarily, refer to the same embodiments.

[0136] Furthermore, the features, advantages, and characteristics described herein can be combined in any suitable manner in one or more embodiments. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in specific embodiments that may not exist in all embodiments of this solution.

[0137] The subject matter of this disclosure may also include, in particular, the following aspects: The first aspect includes a method for wireless communication, comprising: determining, by a user equipment, one or more licenses allocated for reference signal (RS) resources; determining, by the user equipment, one or more RS characteristics in each of the one or more RS transmission opportunities in the licenses; and transmitting RS by the user equipment for each RS transmission duration corresponding to a corresponding transmission opportunity in the one or more transmission opportunities.

[0138] The second aspect includes the first aspect, and further includes, wherein one or more RS characteristics include at least one of the following: RS transmission session, RS transmission priority, RS transmission broadcast type, RS transmission destination information, RS transmission source information, RS transmission delay budget, or RS transmission sequence identifier (ID).

[0139] The third aspect includes either the first or the second aspect, and further includes: the user equipment determining the maximum number of parallel processes that the user equipment can determine for more than one authorization to send RS in the dedicated pool.

[0140] The fourth aspect includes any one of the first to third aspects, and further includes, wherein the user equipment determines the maximum number of parallel processes based on resource selection in order to determine the RS resource allocation.

[0141] The fifth aspect includes either the third or fourth aspect, and further includes: the user equipment reporting at least one of the following: whether the user equipment supports the ability to use parallel processes for a dedicated pool, or the maximum number of parallel processes for a dedicated pool supported by the user equipment.

[0142] The sixth aspect includes any one of the first to fifth aspects, and further includes: the user equipment sending more than one RS resource in a time slot for a dedicated pool.

[0143] The seventh aspect includes any one of the first to sixth aspects, and further includes, wherein one or more RS transmission opportunities include: initial RS transmission opportunities and RS retransmission opportunities, and the method further includes: when the number of unused transmission opportunities in the authorization in the dedicated pool reaches the configuration parameter, the user equipment re-selects authorization, wherein the unused transmission opportunities include: initial RS transmission opportunities or RS retransmission opportunities whose corresponding resources are not used for RS.

[0144] The eighth aspect includes any one of the first to seventh aspects, and further includes, wherein one or more RS transmission opportunities include: an initial RS transmission opportunity and an RS retransmission opportunity, and the method further includes: when the number of unused transmission opportunities in the licenses in the shared pool reaches the configuration parameter, the user equipment reselects the license, wherein the unused transmission opportunities include: initial RS transmission opportunities or RS retransmission opportunities for which the corresponding resources have not been used for RS and sidelink data.

[0145] The ninth aspect includes any one of the first to eighth aspects, and further includes, wherein the user equipment determines that one or more RS characteristics in each RS transmission opportunity are the same as one or more RS characteristics for the RS transmission with the highest priority among all RS transmissions to be transmitted.

[0146] The tenth aspect includes any one of the first to ninth aspects, and further includes, wherein the user equipment determines that one or more RS characteristics in each RS transmission opportunity are the same as one or more RS characteristics of the RS transmission with the highest priority among all RS transmissions to be transmitted and allowed to be selected for transmission.

[0147] The eleventh aspect includes any one of the first to tenth aspects, and further includes, wherein the user equipment determines that one or more RS characteristics for an RS in each RS transmission opportunity are the same as one or more RS characteristics for an RS transmission having the minimum remaining delay budget (DB) among all RS transmissions to be transmitted.

[0148] The twelfth aspect includes any one of the first to eleventh aspects, and further includes, wherein one or more RS transmission opportunities include RS retransmission opportunities, and wherein the user equipment determines that one or more RS characteristics for RS in the RS retransmission opportunity are the same as one or more RS characteristics for RS in the corresponding initial RS transmission opportunity.

[0149] The thirteenth aspect includes any one of the first to twelfth aspects, and further includes, wherein one or more RS characteristics include the characteristic of whether a Media Access Control (MAC) Protocol Data Unit (PDU) transmitted in the same time slot as the RS consists only of padding bits.

[0150] The fourteenth aspect includes the thirteenth aspect, and further includes, wherein the feature is indicated in the sidelink shared channel (SL-SCH) subheader of the MAC PDU.

[0151] The fifteenth aspect includes either the thirteenth or fourteenth aspect, and further includes the characteristic being indicated in a side link control information (SCI), the SCI including SCI format 2-D using a source identifier (ID) with 0 bits or 24 bits and a destination identifier (ID) with 0 bits or 24 bits.

[0152] The sixteenth aspect includes any one of the first to fifteenth aspects, and further includes, wherein the user equipment determines the characteristics based on a first number of continuous transmissions and a second number of stopped transmissions.

[0153] The seventeenth aspect includes the sixteenth aspect, and further includes, wherein at least one of the following conditions exists: when a first RS with a priority continuously transmits to a destination in a first quantity, a second quantity of transmissions of a second RS with that priority and to the destination are not permitted; when a first RS with a priority and associated with a session continuously transmits in a first quantity, a second quantity of transmissions of a second RS with that priority and associated with the session are not permitted; the first quantity of continuous transmissions and the second quantity of stopped transmissions each include at least one of the following: initial transmission, initial transmission and retransmission, initial transmission to the destination, initial transmission and retransmission to the destination, initial transmission of the session, or initial transmission and retransmission of the session.

[0154] The eighteenth aspect includes any one of the fifteenth to seventeenth aspects, and further includes, wherein the user equipment determines one or more RS characteristics based on a first period of continuous transmission and a second period of stopped transmission.

[0155] The nineteenth aspect includes the eighteenth aspect, and further includes, wherein at least one of the following conditions exists: when a first RS with a priority continuously transmits to a destination within a first time period, transmission of a second RS with that priority and destined for that destination is not permitted to be transmitted within a second time period; or when a first RS with a priority and a session continuously transmits within a first time period, transmission of a second RS with that priority and a session is not permitted to be transmitted within a second time period.

[0156] The twentieth aspect includes any one of the first to nineteenth aspects, and further includes, wherein the user equipment determines the RS characteristics based on one of one or more user equipment variables, and wherein the user equipment determines that one or more RS characteristics in each RS transmission opportunity are the same as one or more RS characteristics for the RS transmission with the lowest user equipment variable value among all RS transmissions to be transmitted and allowed to be selected for transmission.

[0157] The twenty-first aspect includes the twentieth aspect, and further includes, wherein each of the one or more user equipment variables is associated with at least one of the destinations of the RS transmission or the session of the RS transmission.

[0158] The twenty-second aspect includes the twenty-first aspect, and further includes, wherein at least one of the following conditions exists: the initial value of the user equipment variable is set to the priority value of the current RS transmission; when the corresponding RS is successfully transmitted in an RS transmission opportunity, the value of the user equipment variable is increased by one; when the corresponding RS is to be transmitted and is not transmitted in a second RS transmission opportunity, the value of the user equipment variable is decreased by one; when the corresponding RS with the second characteristic is to be transmitted and is not transmitted within a predetermined time period, the user equipment variable is decreased by one.

[0159] The twenty-third aspect includes any one of the first to twenty-second aspects, and further includes, wherein one or more RS characteristics include a time interval between two consecutive transmissions, and wherein the two consecutive transmissions include at least one of the following: two RSs, a physical side link control channel (PSCCH) and an RS, or a physical side link shared channel (PSSCH) and an RS.

[0160] The twenty-fourth aspect includes the twenty-third aspect, and further includes, wherein at least one of the following conditions exists: the time interval or maximum time interval between two consecutive transmissions is configured by a communication node other than the user equipment, wherein the communication node includes a gNB that configures the time interval via Radio Resource Control (RRC) signaling, a Location Management Function (LMF) that configures the time period via Side Link Positioning Protocol (SLPP) signaling or LTE Positioning Protocol (LPP) signaling, or a second user equipment that configures the time period via SLPP signaling or PC5-RRC signaling; or the user equipment reports the minimum time interval between two consecutive transmissions that the user equipment can use.

[0161] The twenty-fifth aspect includes a wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory to implement any one of the first to the twenty-fourth methods.

[0162] The twenty-sixth aspect includes a computer program product comprising a computer-readable program medium having code stored thereon, which, when executed by a processor, causes the processor to implement any one of the first to the twenty-fourth methods.

[0163] In addition to the features mentioned in each of the individual aspects listed above, some examples may be shown individually or in combination as optional features mentioned in the subordinate aspects and / or disclosed in the description above and shown in the figures.

Claims

1. A method for wireless communication, the method comprising: The user equipment determines one or more licenses for the allocation of reference signal (RS) resources; The user equipment determines one or more RS characteristics in each of the one or more RS transmission opportunities in the authorization; as well as The user equipment transmits RS during each RS transmission duration corresponding to one of the one or more transmission opportunities.

2. The method according to claim 1, wherein, The one or more RS characteristics include at least one of the following: RS transmission session, RS transmission priority, RS transmission broadcast type, RS transmission destination information, RS transmission source information, RS transmission delay budget, or RS transmission sequence identifier (ID).

3. The method according to claim 1, further comprising: The user equipment determines the maximum number of parallel processes that it can determine for more than one authorization to send the RS in the dedicated pool.

4. The method according to claim 1, wherein, The user equipment determines the maximum number of parallel processes based on resource selection, thereby determining the RS resource allocation.

5. The method according to claim 3, further comprising: The user equipment reports at least one of the following: whether the user equipment supports the ability to use parallel processes for a dedicated pool, or the maximum number of parallel processes for a dedicated pool supported by the user equipment.

6. The method according to claim 1, further comprising: The user equipment sends more than one RS resource in a time slot for the dedicated pool.

7. The method according to claim 1, wherein, The one or more RS transmission opportunities include: initial RS transmission opportunities and RS retransmission opportunities. The method further includes: when the number of unused transmission opportunities in the license in the dedicated pool reaches the configuration parameter, the user equipment reselects the license, wherein the unused transmission opportunities include: the corresponding resources that have not been used for the initial RS transmission opportunity or RS retransmission opportunity of the RS.

8. The method according to claim 1, wherein, The one or more RS transmission opportunities include: initial RS transmission opportunities and RS retransmission opportunities. The method further includes: when the number of unused transmission opportunities in the license in the shared pool reaches the configuration parameter, the user equipment reselects the license, wherein the unused transmission opportunities include: initial RS transmission opportunities or RS retransmission opportunities whose corresponding resources have not been used for the RS and sidelink data.

9. The method according to claim 1, wherein, The user equipment determines one or more RS characteristics in each RS transmission opportunity that are the same as one or more RS characteristics for the RS transmission with the highest priority among all RS transmissions to be sent.

10. The method according to claim 1, wherein, The user equipment determines one or more RS characteristics in each RS transmission opportunity that are the same as one or more RS characteristics of the RS transmission with the highest priority among all RS transmissions to be transmitted and allowed to be selected for transmission.

11. The method according to claim 1, wherein, The user equipment determines that one or more RS characteristics for each RS transmission opportunity are the same as one or more RS characteristics for the RS transmission with the minimum remaining delay budget (DB) among all RS transmissions to be transmitted.

12. The method according to claim 1, wherein, The one or more RS transmission opportunities include RS retransmission opportunities, and wherein the user equipment determines that one or more RS characteristics for RS in the RS retransmission opportunity are the same as one or more RS characteristics for RS in the corresponding initial RS transmission opportunity.

13. The method according to claim 1, wherein, The one or more RS characteristics include the following: whether the Media Access Control (MAC) Protocol Data Unit (PDU) transmitted in the same time slot as the RS consists only of padding bits.

14. The method of claim 13, wherein, The characteristics are indicated in the Side Link Shared Channel (SL-SCH) subheader of the MAC PDU.

15. The method according to claim 13, wherein, The characteristics are indicated in the sidelink control information (SCI), which includes SCI format 2-D using a source identifier (ID) with 0 bits or 24 bits and a destination identifier (ID) with 0 bits or 24 bits.

16. The method according to claim 1, wherein, The user equipment determines the characteristic based on a first number of continuous transmissions and a second number of stopped transmissions.

17. The method according to claim 16, wherein, At least one of the following situations exists: When a first RS with a priority continuously transmits to a destination in the first quantity, a second quantity of transmissions of a second RS with the same priority to the destination are not allowed to be selected. When a first RS with a priority and associated with a session transmits continuously in the first quantity, it is not allowed to select a second RS with the same priority and associated with the session for a second quantity of transmissions. The first number of continuous transmissions and the second number of stopped transmissions each include at least one of the following: initial transmission, initial transmission and retransmission, initial transmission to the destination, initial transmission and retransmission to the destination, initial transmission of the session, or initial transmission and retransmission of the session.

18. The method according to claim 15, wherein, The user equipment determines one or more RS characteristics based on a first period of continuous transmission and a second period of stopped transmission.

19. The method of claim 18, wherein, At least one of the following situations exists: When a first RS with a priority continuously sends to a destination within the first time period, the transmission of a second RS with the same priority to the destination is not allowed to be transmitted within the second time period. or When a first RS with a priority and a session transmits continuously during the first time period, the transmission of a second RS with the same priority and the same session is not allowed to be transmitted during the second time period.

20. The method according to claim 1, wherein, The user equipment determines RS characteristics based on one of one or more user equipment variables, wherein the user equipment determines one or more RS characteristics in each RS transmission opportunity to be the same as one or more RS characteristics for the RS transmission with the lowest user equipment variable value among all RS transmissions to be sent and allowed to be selected for transmission.

21. The method of claim 20, wherein each of the one or more user equipment variables is associated with at least one of the destination of the RS transmission or the session of the RS transmission.

22. The method according to claim 21, wherein, At least one of the following situations exists: The initial value of the user equipment variable is set to the priority value of the current RS transmission; When the corresponding RS is successfully transmitted in the RS transmission opportunity, the user equipment variable value increases by one; When the corresponding RS is to be sent but is not sent in the second RS transmission opportunity, the value of the user equipment variable is reduced by one; When the corresponding RS with the second characteristic is to be sent and is not sent within a predetermined time period, the user equipment variable is reduced by one.

23. The method according to claim 1, wherein, The one or more RS characteristics include a time interval between two consecutive transmissions, wherein the two consecutive transmissions include at least one of the following: two RSs, a Physical Side Link Control Channel (PSCCH) and the RS, or a Physical Side Link Shared Channel (PSSCH) and the RS.

24. The method of claim 23, wherein, At least one of the following situations exists: The time interval or maximum time interval between the two consecutive transmissions is configured by a communication node other than the user equipment, wherein the communication node includes a gNB that configures the time interval via Radio Resource Control (RRC) signaling, a Location Management Function (LMF) that configures the time interval via Side Link Positioning Protocol (SLPP) signaling or LTE Positioning Protocol (LPP) signaling, or a second user equipment that configures the time interval via SLPP signaling or PC5-RRC signaling; or The user equipment reports the minimum time interval between the two consecutive transmissions that the user equipment can use.

25. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory to implement the method according to any one of claims 1 to 24.

26. A computer program product comprising a computer-readable program medium on which code is stored, the code, when executed by a processor, causing the processor to perform the method according to any one of claims 1 to 24.

Images