Method and equipment for handling scheduling request triggered by positioning reference signal resource request

Abstract

The invention discloses a method and equipment for handling a scheduling request triggered by a sidelink positioning reference signal resource request. A first user equipment determines a first priority value associated with a first sidelink transmission to a second user equipment. The first user equipment determines a second priority value associated with a scheduling request transmission to the network node based on one or more priority values associated with one or more second sidelink transmissions associated with a sidelink resource request on which the scheduling request transmission is triggered. The first user equipment selects one of a first sidelink transmission or a scheduling request transmission from among a plurality of transmissions including the first sidelink transmission and the scheduling request transmission based on the first priority value and the second priority value. The first user equipment performs the selected transmission.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 680,782, filed August 8, 2024, the entire disclosure of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present disclosure relates generally to wireless communication networks, and more particularly to methods and apparatus for handling of scheduling requests triggered by sidelink positioning reference signal (SL-PRS) resource requests in a wireless communication system. BACKGROUND

[0004] As the demand for mobile communication devices increases and as the capacity of these devices increases, the use of these devices for communication has dramatically increased. These devices are now routinely used for communication while the user is on the move. As a result, the use of mobile communication devices for voice communication while the user is on the move has dramatically increased. These devices are now routinely used for voice communication while the user is on the move.

[0005] An example network structure is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). An E-UTRAN system can provide high data throughput to enable IP bearer voice and multimedia services. Currently, the 3GPP standards organization is discussing new air interface technologies for the next generation (e.g., 5G). Therefore, changes to the current body of 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. SUMMARY

[0006] According to the present disclosure, one or more apparatuses and / or methods are provided. In an example from the perspective of a first user equipment (UE), the first UE determines a first priority value associated with a sidelink (SL) transmission to a second UE. The first UE determines a second priority value associated with a scheduling request (SR) transmission to a network node based on one or more priority values associated with one or more sidelink positioning reference signal (SL-PRS) transmissions, the one or more SL-PRS transmissions being associated with a SL-PRS resource request based on which the SR transmission is triggered. The first UE selects one of the SL transmission or the SR transmission from among a plurality of transmissions including the SL transmission and the SR transmission based on the first priority value and the second priority value. The first user equipment performs the selected transmission.

[0007] In an instance from the perspective of a first UE, the first UE determines a first priority value associated with a first SL transmission to a second UE. The first UE determines a second priority value associated with a second SR transmission to a network node based on one or more priority values ​​associated with one or more second SL transmissions, which are related to the SL resource request on which the SR transmission was triggered. The first UE selects one of a plurality of transmissions, including the first SL transmission and the SR transmission, based on the first and second priority values. The first user equipment executes the selected transmission.

[0008] In an instance from the perspective of a first UE that cannot simultaneously execute an SR transmission triggered by an SL-PRS resource request and an SL transmission associated with a first priority value, the first UE determines a second priority value associated with the SR transmission based on the lowest priority value among the priority values ​​indicated by the SL-PRS resource request MAC CE for one or more pending SL-PRS transmissions. The first UE executes an SL transmission to a second UE based on the first priority value being lower than the second priority value, or executes an SR transmission to a network node based on the second priority value being lower than the first priority value. Attached Figure Description

[0009] Figure 1 A diagram of a wireless communication system according to an exemplary embodiment is shown.

[0010] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an exemplary embodiment.

[0011] Figure 3 This is a functional block diagram of a communication system according to an exemplary embodiment.

[0012] Figure 4 This is based on an exemplary embodiment. Figure 3 Functional block diagram of the program code.

[0013] Figure 5 A sidelink (SL) channel state information (CSI) media access control (MAC) control element (CE) according to an exemplary embodiment is shown.

[0014] Figure 6 A Side Link Positioning Reference Signal (SL-PRS) Resource Request (MACCE) is illustrated according to an exemplary embodiment.

[0015] Figure 7This illustrates a scenario, according to an exemplary embodiment, associated with performing a conflict prioritization operation for a conflict between a scheduling request (SR) transmission and a side link (SL) transmission.

[0016] Figure 8 This is a flowchart based on an exemplary embodiment.

[0017] Figure 9 This is a flowchart based on an exemplary embodiment.

[0018] Figure 10 This is a flowchart based on an exemplary embodiment. Detailed Implementation

[0019] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), 3GPP Long Term Evolution (LTE) Radio Access, 3GPP Long Term Evolution Advanced (LTE-A), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR) Radio Access for 5G, or some other modulation techniques.

[0020] Specifically, the exemplary wireless communication system apparatus described below can be designed to support one or more standards, such as those provided by the consortium referred to herein as 3GPP, which is named the "3rd Generation Partnership Project," including: 3GPP TS 38.321V18.2.0 (2024-06), "3GPP TSG RAN; Media Access Control (MAC) Protocol Specification (Version 18)." The standards and documents listed above are hereby expressly incorporated by reference in their entirety.

[0021] Figure 1 A multiple access wireless communication system according to one or more embodiments of the present disclosure is presented. Access network 100 (AN) includes multiple antenna groups, one comprising 104 and 106, another comprising 108 and 110, and yet another comprising 112 and 114. Figure 1In the diagram, only two antennas are shown for each antenna group; however, more or fewer antennas can be used for each antenna group. Access terminal 116 (AT) communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from access terminal 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In a frequency-division duplex (FDD) system, communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, forward link 120 can use a frequency different from that used by reverse link 118.

[0022] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group may be designed to communicate with an access terminal in a sector of the area covered by the access network 100.

[0023] In communications on forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Furthermore, compared to an access network that transmits to all its access terminals via a single antenna, an access network that uses beamforming to transmit to access terminals randomly distributed throughout its coverage area typically causes less interference to access terminals in neighboring cells.

[0024] An access network (AN) can be a fixed station or base station used for communication with terminals, and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB (eNB), next-generation NodeB (gNB), or other terms. An access terminal (AT) may also be referred to as user equipment (UE), wireless communication device, terminal, access terminal, or other terms.

[0025] Figure 2 An embodiment of a multiple-input multiple-output (MIMO) system 200 is presented, comprising a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)). At the transmitter system 210, service data from multiple data streams can be provided from a data source 212 to a transmit (TX) data processor 214.

[0026] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, encodes, and interleaves the service data of the data streams based on a specific encoding scheme selected for each data stream to provide encoded data.

[0027] Orthogonal frequency-division multiplexing (OFDM) technology can be used to multiplex the coded data and pilot data of each data stream. The pilot data can typically be a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilots and coded data of the data streams can then be modulated (i.e., symbol mapped) based on a specific modulation scheme selected for each data stream (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PSK), or M-ary quadrature amplitude modulation (M-QAM), etc.) to provide modulated symbols. Instructions executed by processor 230 can determine the data rate, coding, and / or modulation for each data stream.

[0028] The modulation symbols of the data stream are then provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 may apply beamforming weights to symbols in the data stream and to the antennas transmitting said symbols therefrom.

[0029] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and / or up-converts) the analog signals to provide modulated signals suitable for transmission via a MIMO channel. Then, signals can be transmitted from N... T Antennas 224a to 224t transmit N from transmitters 222a to 222t. T A modulated signal.

[0030] At receiver system 250, by N RAntennas 252a to 252r receive the transmitted modulated signal and can provide the signal received from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 can adjust (e.g., filter, amplify, and downconvert) the corresponding received signal, digitize the adjusted signal to provide a sample, and / or further process the sample to provide a corresponding "received" symbol stream.

[0031] Next, the RX data processor 260 from N R Each receiver 254 receives and / or processes N based on specific receiver processing technology. R The received symbol stream provides N T Each detected symbol stream. The RX data processor 260 can then demodulate, deinterleave, and / or decode each detected symbol stream to recover the service data used for the data stream. The processing performed by the RX processor 260 can complement the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.

[0032] Processor 270 can periodically determine which precoding matrix to use (discussed below). Processor 270 formulates a reverse link message including the matrix index part and the rank part.

[0033] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message may then be processed by the TX data processor 238 (which may also receive service data from several data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and / or transmitted back to the transmitter system 210.

[0034] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Next, processor 230 can determine which precoding matrix to use to determine beamforming weights, and then process the extracted message.

[0035] Figure 3 An alternative simplified functional block diagram of a communication device according to one embodiment of the disclosed subject matter is presented. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to achieve... Figure 1 UE (or AT) 116 and 122 or Figure 1The communication device 300 includes a base station (or AN) 100, and the wireless communication system can be an LTE system or an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, transmit received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306. Alternatively, the communication device 300 in a wireless communication system can also be used. Figure 1 AN 100 in the middle.

[0036] Figure 4 This is an embodiment based on the disclosed subject matter. Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 can perform radio resource control. Layer 2 portion 404 can perform link control. Layer 1 portion 406 can perform and / or implement physical connections.

[0037] The aspect of scheduling requests (SRs) is discussed in 3GPP TS 38.321V18.2.0 (2024-06). It should be noted that section 6.1.3.35 of 3GPP TS 38.321V18.2.0 (2024-06) is titled "Sidelink CSI Report MAC CE". Figure 6 .1.3.35-1 is reproduced in this paper as Figure 5 The section 6.1.3.74 of 3GPP TS 38.321V18.2.0 (2024-06) is titled "SL-PRS Resource Request MAC Control Element". Figure 6 .1.3.74-1 is reproduced in this paper as Figure 6 The following quotes one or more parts of 3GPP TS 38.321V18.2.0 (2024-06).

[0038] 5.4.4 Scheduling Request

[0039] A scheduling request (SR) is used to request UL-SCH resources for a new transfer.

[0040] A MAC entity may be configured with zero, one, or more SR configurations. An SR configuration consists of a set of PUCCH resources for SR spanning different BWPs and cells. For logical channels, or for SCell beam fault recovery (see Clause 5.17) and for consistency LBT fault recovery (see Clause 5.21), at most one PUCCH resource is configured per BWP for SR. For logical channels serving radio bearers configured with SDTs, no PUCCH resources for SR are configured for the SDTs. For beam fault recovery of the BFD-RS set serving a cell, at most two PUCCH resources are configured per BWP for SR. A dedicated SR configuration is configured for positioning measurement gap activation / deactivation requests.

[0041] Each SR configuration corresponds to one or more logical channels and / or SCell beam fault recovery and / or consistent LBT fault recovery and / or BFD-RS set beam fault recovery and / or positioning measurement gap activation / deactivation requests. Each logical channel, SCell beam fault recovery, BFD-RS set beam fault recovery, and consistent LBT fault recovery may be mapped to zero or one SR configuration configured by RRC. The SR configuration of the logical channel that triggers a BSR (clause 5.4.5) or DSR (clause 5.4.9) or SCell beam fault recovery or BFD-RS set beam fault recovery or consistent LBT fault recovery (clause 5.21) (if this configuration exists) or positioning measurement gap activation / deactivation request (clause 5.25) is considered the corresponding SR configuration used for the triggered SR. Any SR configuration may be used for an SR triggered by a preemptive BSR (clause 5.4.7) or timing advance reporting (clause 5.4.8).

[0042] RRC configures the following parameters for the scheduling request program:

[0043] -sr-ProhibitTimer (based on SR configuration);

[0044] -sr-TransMax (based on SR configuration).

[0045] The following UE variables are used in the scheduling request procedure:

[0046] -SR_COUNTER (based on SR configuration).

[0047] If an SR is triggered and there are no other pending SRs corresponding to the same SR configuration, the MAC entity sets the SR_COUNTER of the corresponding SR configuration to 0.

[0048] When an SR is triggered, it will be considered pending until it is canceled.

[0049] All pending SRs triggered by the BSR procedure (clause 5.4.5) prior to MAC PDU assembly will be cancelled, and when a MAC PDU is transmitted and this PDU contains a long, finely detailed long, or short BSR MAC CE, each corresponding sr-ProhibitTimer will be stopped. This BSR MAC CE contains a buffer state up to (and including) the last event that triggered the BSR (see clause 5.4.5) prior to MAC PDU assembly. When the UL grants all pending data suitable for transmission, all pending SRs triggered by the BSR procedure (clause 5.4.5) will be cancelled, and each corresponding sr-ProhibitTimer will be stopped.

[0050] For each pending SR not triggered for the serving cell in accordance with the BSR procedure (clause 5.4.5), the MAC entity will:

[0051] 1> If this SR is triggered before the MAC PDU assembly via a preemptive BSR procedure (see Clause 5.4.7), and a MAC PDU containing the relevant preemptive BSR MAC CE is transmitted; or

[0052] 1> If this SR is triggered by beam fault recovery of the SCell (see Clause 5.17) and transmits a MAC PDU, and this PDU contains a MAC CE for the BFR containing beam fault recovery information for this SCell; or

[0053] 1> If this SR is triggered by beam fault recovery for the BFD-RS set for the serving cell (see Clause 5.17) and a MAC PDU is transmitted, and this PDU contains an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE containing beam fault recovery information for this BFD-RS set for the serving cell; or

[0054] 1> If this SR is triggered by beam failure recovery of the SCell (see Clause 5.17) and the SCell is deactivated (see Clause 5.9); or

[0055] 1> If this SR is triggered by beam fault recovery of the BFD-RS set used for the SCell (see Clause 5.17) and this SCell is deactivated (see Clause 5.9); or

[0056] 1> If the SR is triggered by a positioning measurement gap activation / deactivation request (see Clause 5.25), and the positioning measurement gap activation / deactivation request MAC CE that triggered the SR has been cancelled; or

[0057] 1> If this SR is triggered by a consistent LBT fault recovery of the SCell (see Clause 5.21) and a MAC PDU is transmitted, and the MAC PDU contains an LBT fault MAC CE indicating a consistent LBT fault of this SCell; or

[0058] 1> If this SR is triggered by a consistent LBT failure recovery of the SCell (see Clause 5.21), and all triggered consistent LBT failures of this SCell are cancelled; or

[0059] 1> If this SR is triggered by an advance timing report (see Clause 5.4.8) and all triggered advance timing reports are cancelled; or

[0060] 1> If this SR was triggered by a DSR procedure (see Clause 5.4.9) and the DSR that triggered the SR has been cancelled:

[0061] 2> Cancel the pending SR and stop the corresponding sr-ProhibitTimer (if it is running).

[0062] Only PUCCH resources that are active during the SR delivery time on the BWP are considered valid.

[0063] As long as at least one SR is pending, for each pending SR, the MAC entity will:

[0064] 1> If the MAC entity is not configured with a valid PUCCH resource for pending SRs; and

[0065] 1> If there is no ongoing RACH-free LTM cell handover; and

[0066] 1> If rach-LessHO is not configured:

[0067] 2> Initiate a random access procedure on SpCell (see Clause 5.1) and cancel the pending SR.

[0068] 1> Otherwise, for the SR configuration corresponding to the pending SR:

[0069] 2> When the MAC entity has an SR transmission opportunity on a valid PUCCH resource for the configured SR; and

[0070] 2> If sr-ProhibitTimer is not running during the SR transmission timing; and

[0071] 2> If the PUCCH resource used for SR transmission timing does not overlap with the measurement gap:

[0072] 3> If the PUCCH resource used for SR transmission timing does not overlap with UL-SCH and SL-SCH resources, the simultaneous transmission of the UL-SCH resource and SR is not permitted by the configuration of simultaneousPUCCH-PUSCH, simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup, simultaneousSR-PUSCH-diffPUCCH-Groups, simultaneousPUCCH-PUSCH-SamePriority, or simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup; or

[0073] 3> If the MAC entity can perform this SR transfer simultaneously with the transfer of SL-SCH resources; or

[0074] 3> If the MAC entity is configured with lch-based Prioritization, and the PUCCH resource used for the SR transmission timing does not overlap with the uplink grant PUSCH duration received in the random access response, or with the uplink grant PUSCH duration addressed to the temporary C-RNTI, or with the PUSCH duration of the MSGA payload, and the PUCCH resource used for the SR transmission timing of the pending SR triggered as specified in Clause 5.4.5 overlaps with any other UL-SCH resource, and the physical layer may transmit the SR on a valid PUCCH resource used for the SR, and the logical channel triggering the SR has a higher priority than the uplink grant for any UL-SCH resource, then the SR can be transmitted on a valid PUCCH resource used for the SR. The priority of uplink permission, wherein uplink permission has not been de-prioritized and its simultaneous transmission with SR is not permitted by the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCHgroups or simultaneousPUCCH-PUSCH-SamePriority or simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup, and the priority of uplink permission is determined as specified in Clause 5.4.1; or

[0075] 3> If both sl-PrioritizationThres and ul-PrioritizationThres are configured, and the PUCCH resource for the timing of the SR transmission of the triggered pending SR as specified in Clause 5.22.1.5 overlaps with any UL-SCH resource carrying the MAC PDU, and the priority value of the triggering SR determined as specified in Clause 5.22.1.5 is lower than sl-PrioritizationThres, and the highest priority value of the logical channel in the MAC PDU is higher than or equal to ul-PrioritizationThres, and any MAC CE that is prioritized as described in Clause 5.4.3.1.3 according to TS23.287

[19] is not included in the MAC PDU, and the MAC PDU is not prioritized by the upper layer; or

[0076] 3> If the SL-SCH resource overlaps with the PUCCH resource used for the timing of a pending SR transmission (as specified in Clause 5.4.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and no transmission on the SL-SCH resource has been prioritized as described in Clause 5.22.1.3.1a, or the priority value of the logical channel triggering the SR is lower than ul-PrioritizationThres (if configured); or

[0077] 3> If the SL-SCH resource overlaps with the PUCCH resource used for the timing of a pending SR transmission (as specified in Clause 5.22.1.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and the priority of the triggering SR determined as specified in Clause 5.22.1.5 is higher than the priority of the MAC PDU determined for the SL-SCH resource as specified in Clause 5.22.1.3.1a; or

[0078] 3> If the SL-PRS resource overlaps with the PUCCH resource used for the timing of a pending SR transmission (as specified in Clause 5.4.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission on the SL-PRS resource, and no transmission on the SL-PRS resource has been prioritized as described in Clause 5.22.1.3.1a, or the priority value of the logical channel triggering the SR is lower than ul-PrioritizationThres (if configured); or

[0079] 3> If the SL-PRS resource overlaps with the PUCCH resource for the timing of an SR transmission for a pending SR that is triggered (as specified in Clause 5.22.1.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggering SR determined as specified in Clause 5.22.1.5 for the SL-PRS resource is higher than the priority of the MAC PDU and the SL-PRS (if available) determined as specified in Clause 5.22.1.3.1a:

[0080] 4> Treat SR transfers as priority SR transfers.

[0081] 4> Treat other overlapping uplink grants (if they exist) as de-prioritized uplink grants, except for overlapping uplink grants that are allowed to be transmitted simultaneously by the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups or simultaneousPUCCH-PUSCH-SamePriority or simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup;

[0082] 4> If de-prioritizing uplink granting is a configured uplink granting that has started its PUSCH and is configured with autonomousTx:

[0083] 5> Stop the configuredGrantTimer used by the corresponding HARQ process for de-prioritizing uplink grants;

[0084] 5> Stop the cg-RetransmissionTimer used for the corresponding HARQ process that is used to de-prioritize uplink grants.

[0085] 4> If SR_COUNTER <sr-TransMax:

[0086] 5> Instruct the physical layer to send the SR on a valid PUCCH resource used for the SR;

[0087] 5> If no LBT fault indication is received from the lower layer:

[0088] 6> Increment SR_COUNTER by 1;

[0089] 6> Start sr-ProhibitTimer.

[0090] 5> Otherwise, if lbt-FailureRecoveryConfig is not configured:

[0091] 6> Increment SR_COUNTER by 1.

[0092] 4> Otherwise:

[0093] 5> Notify RRC to release PUCCHs used for all serving cells;

[0094] 5> Notify RRC to release SRS for all serving cells;

[0095] 5> Clear any configured downlink assignments and uplink permissions;

[0096] 5> Remove any PUSCH resources used for semi-persistent CSI reporting;

[0097] 5> If rach-LessHO is not configured and if there is no ongoing RACH-less LTM cell handover:

[0098] 6> Start the random access procedure on SpCell (see Clause 5.1) and cancel all pending SRs.

[0099] 3> Otherwise:

[0100] 4> Treat SR transfer as a de-prioritized SR transfer.

[0101] Note 1: Apart from the SR used for SCell beam fault recovery, when the MAC entity has more than one overlapping valid PUCCH resource for SR transmission timing, the UE implementation decides which valid PUCCH resource to select for SR to send the SR signal.

[0102] Note 2: If more than one individual SR triggers instructions from the MAC entity to the PHY layer to signal the SR on the same valid PUCCH resource, then the SR_COUNTER used for the relevant SR configuration is incremented only once.

[0103] Note 3: When a MAC entity has a pending SR for SCell beam fault recovery and the MAC entity has one or more PUCCH resources that overlap with the PUCCH resources for SCell beam fault recovery for SR transmission timing (excluding PUCCH resources for pending SRs for beam fault recovery of BFD-RS sets), the MAC entity will only consider the PUCCH resources for SCell beam fault recovery as valid. When a MAC entity has a pending SR for beam fault recovery of the BFD-RS set for the serving cell and the MAC entity has one or more PUCCH resources that overlap with the PUCCH resources for beam fault recovery of the BFD-RS set for SR transmission timing (excluding PUCCH resources for pending SRs for beam fault recovery), the MAC entity will only consider the PUCCH resources for beam fault recovery of the BFD-RS set as valid.

[0104] Note 4: For a UE operating in the semi-static channel access mode as described in TS 37.213

[18] , PUCCH resources that overlap with a set of consecutive symbols that the UE does not transmit before the start of the next channel occupancy time are considered invalid.

[0105] Note 5: If the MAC entity is configured with lch-based Prioritization, then when it is determined whether the valid PUCCH resource for SR transmission can be transmitted by the physical layer and whether the timing of the SR transmission overlaps with the uplink PUSCH duration allowed for the MSGA payload, the MAC entity does not perform UCI multiplexing according to the procedure specified in TS 38.213[6].

[0106] Note 6: When a MAC entity has PUCCH resources for a pending SR for beam fault recovery that overlap with the PUCCH resources for beam fault recovery of the BFD-RS set used for SR transmission timing, the UE implementation scheme shall select either the PUCCH resources for SCell beam fault recovery or the PUCCH resources for beam fault recovery of the BFD-RS set.

[0107] Since a pending SR for BSR initiated by the MAC entity before the MAC PDU combination does not have a configured valid PUCCH resource, the MAC entity may stop the ongoing random access procedure (if one exists) if:

[0108] - The MAC PDU is transmitted using a UL grant other than that provided by the random access response or a UL grant determined for the transmission of the MSGA payload as specified in Clause 5.1.2a, and this PDU contains a BSR MAC CE containing a buffer state up to (and including) the previous event that triggered the BSR (see Clause 5.4.5) prior to the MAC PDU assembly; or

[0109] - The UL allows for the inclusion of all pending data that can be used for transmission.

[0110] Since there is no pending SR for SL-BSR with a valid configured PUCCH resource, the MAC entity may stop the ongoing random access procedure (if one exists) if:

[0111] - The MAC PDU is transmitted using a UL grant other than that provided by the random access response or a UL grant determined as specified in Clause 5.1.2a for the transmission of the MSGA payload, and the ongoing random access procedure is initiated by the MAC entity before the MAC PDU assembly, and the PDU contains an SL-BSR MAC CE containing a buffer state up to (and including) the last event that triggered the SL-BSR (see Clause 5.22.1.6) before the MAC PDU assembly; or

[0112] -SL allows for the inclusion of all pending data that can be transmitted, and the ongoing random access procedure is initiated by the MAC entity before the sidelink MAC PDU combination.

[0113] Because there is no pending SR for SL-CSI reporting with a valid configured PUCCH resource, the MAC entity may stop (if any) the ongoing random access procedure, provided that:

[0114] -SL allows for the inclusion of SL-CSI reports MAC CE for transmission.

[0115] Since there is no pending SR for SL-DRX command indication with a valid configured PUCCH resource, the MAC entity may halt the ongoing random access procedure (if one exists) if:

[0116] -SL allows the inclusion of SL-DRX command indications for transmission.

[0117] Since there is no pending SR for the BFR for SCell with a valid configured PUCCH resource, the MAC entity may stop the ongoing random access procedure (if one exists) if:

[0118] - The MAC PDU is transmitted using a UL grant other than that provided by the random access response or a UL grant determined for the transmission of the MSGA payload as specified in Clause 5.1.2a, and this PDU contains a MAC CE of the BFR containing beam fault recovery information for the SCell; or

[0119] -SCell is deactivated (as specified in Clause 5.9), and all triggering BFRs used for SCell are cancelled.

[0120] If a pending SR exists in the BFR of the serving cell's BFD-RS set for a serving cell that does not have a configured valid PUCCH resource, the MAC entity may halt the ongoing random access procedure, if such a SR exists, provided that:

[0121] - A MAC PDU is transmitted using a UL grant other than that provided by the random access response or a UL grant determined for the transmission of the MSGA payload as specified in Clause 5.1.2a, and this PDU contains an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE, which contains beam fault recovery information for the BFD-RS set of the serving cell.

[0122] Since there is no pending SR for consistent LBT fault recovery with a valid configured PUCCH resource, the MAC entity may stop the ongoing random access procedure (if one exists) if:

[0123] - The MAC PDU is transmitted using a UL grant other than that provided by the random access response or a UL grant determined for transmitting the MSGA payload as specified in section 5.1.2a, and this PDU contains an LBT fault MAC CE indicating a consistent LBT fault for all SCells that have triggered a consistent LBT fault; or

[0124] - All SCells that triggered consistent LBT fault recovery were deactivated (see Clause 5.9).

[0125] If a pending SR for sidelink consistent LBT failure recovery is not configured with valid PUCCH resources, the MAC entity may halt the ongoing random access procedure (if one exists), provided one of the following conditions is met:

[0126] - The MAC PDU is transmitted using a UL grant other than that provided by the random access response, or a UL grant as specified in Clause 5.1.2a for the transmission of the MSGA payload, and this PDU contains an SL LBT Failure MAC CE indicating a side-link consistent LBT failure; or

[0127] - All triggered sidelink consistent LBT fault recovery is cancelled (see Clause 5.31.2).

[0128] Since there is no pending SR for a location measurement gap activation / deactivation request with a valid configured PUCCH resource, the MAC entity may stop the ongoing random access procedure (if one exists) if:

[0129] - The activation / deactivation request MAC CE for the positioning measurement gap corresponding to the random access procedure SR has been cancelled.

[0130] Since there is no pending SR for time advance reporting with a valid configured PUCCH resource, the MAC entity may stop the ongoing random access procedure (if one exists) if:

[0131] - The MAC PDU is transmitted using a UL grant other than that provided by the random access response or a UL grant determined as specified in Clause 5.1.2a for the transmission of the MSGA payload, and the PDU includes an advance notification of the MAC CE (see Clause 5.4.8).

[0132] If there is no pending SR for DSR with a valid configured PUCCH resource, the MAC entity may stop the ongoing random access procedure (if one exists) if:

[0133] - Use a UL grant other than the UL grant provided by the random access response, or a UL grant determined as specified in Clause 5.1.2a for the transmission of the MSGA payload, and this PDU contains DSR MAC CE or

[0134] - All PDCP SDUs associated with DSR (see Clause 5.4.9); or

[0135] - All PDCP SDUs associated with the DSR have been discarded (see Clause 5.4.9).

[0136] Since there is no pending SR for an SL-PRS resource request with a valid configured PUCCH resource, the MAC entity may stop the ongoing random access procedure (if one exists) if:

[0137] - The MAC PDU is transmitted using a UL grant other than the UL grant provided by the random access response or a UL grant determined as specified in Clause 5.1.2a for the transmission of the MSGA payload, and the PDU contains an SL-PRS resource request MAC CE (see Clause 5.22.1.12).

[0138] [...]

[0139] 5.4.5 Buffer Status Report

[0140] The Buffer Status Report (BSR) program is used to provide the service gNB with information about the amount of UL data in the MAC entity.

[0141] [...]

[0142] Each logical channel can be assigned to an LCG using a logicalChannelGroup. The maximum number of LCGs is eight, except for IAB-MTs configured with logicalChannelGroupIAB-Ext, which have a maximum of 256 LCGs.

[0143] The MAC entity determines the amount of UL data available for the logical channel based on the data volume calculation procedures in TS 38.322[3] and 38.323[4].

[0144] A BSR should be triggered if any of the following events occur for an active cell group:

[0145] - For logical channels belonging to the LCG, UL data becomes available for MAC entities; and

[0146] - This UL data belongs to a logical channel with a higher priority than any logical channel containing available UL data belonging to any LCG; or

[0147] - None of the logical channels belonging to the LCG contain any usable UL data.

[0148] In this context, the BSR will be referred to as the 'regular BSR' below;

[0149] - When allocating UL resources and the number of padding bits is equal to or greater than the size of the Buffer Status Report (MAC) CE plus its subheadings, the BSR will be referred to as the 'Padding BSR' below.

[0150] If the -retxBSR-Timer expires and at least one of the logical channels belonging to the LCG contains UL data, the BSR will be referred to as a 'regular BSR' below.

[0151] -periodicBSR-Timer expires, in which case the BSR will be referred to as 'periodic BSR' below.

[0152] Note 1: When a regular BSR trigger event occurs simultaneously for multiple logical channels, a separate regular BSR is triggered for each logical channel.

[0153] For a standard BSR, the MAC entity should:

[0154] 1> If a BSR is triggered for a logical channel configured with a true logicalChannelSR-DelayTimerApplied by the upper layer, and the SDT procedure is not in progress according to clause 5.27, then:

[0155] 2> Start or restart logicalChannelSR-DelayTimer.

[0156] 1> Otherwise, if a BSR is triggered for a logical channel configured with a true logicalChannelSR-DelayTimerApplied by the upper layer, and the SDT procedure is in progress according to clause 5.27, then:

[0157] 2> Start or restart logicalChannelSR-DelayTimer with the value configured by sdt-LogicalChannelSR-DelayTimer (if configured).

[0158] 1> Otherwise:

[0159] 2> If it is running, then stop logicalChannelSR-DelayTimer.

[0160] [...]

[0161] MAC entities will:

[0162] 1> If the buffer status reporting procedure determines that at least one BSR has been triggered and not canceled:

[0163] 2> If the UL-SCH resource is available for a new transmission, and the UL-SCH resource can accommodate a BFR MAC CE plus its sub-header due to logical channel prioritization:

[0164] 3> Instruct the multiplexing and combining procedures to produce a BSR MAC CE, as defined in Clause 6.1.3.1;

[0165] 3> Start or restart periodicBSR-Timer, except when all generated BSRs are long or short truncated or extended long or short truncated BSRs;

[0166] 3> Start or restart retxBSR-Timer.

[0167] 2> If a regular BSR has been triggered and the logicalChannelSR-DelayTimer is not running:

[0168] 3> If no UL-SCH resource is available for the new transfer; or

[0169] 3> If the MAC entity is configured with a logical channel triggering rule (BSR) that is configured for uplink permission and is set to false for logicalChannelSR-Mask; or

[0170] 3> If the UL-SCH resources available for new transmission do not meet the LCP mapping constraints of the logical channel configured to trigger BSR (see Clause 5.4.3.1), then:

[0171] 4> Trigger a scheduling request.

[0172] [...]

[0173] 5.22.1.3.1a Sidelink processes not associated with a dedicated SL-PRS resource pool

[0174] The sidelink process is associated with the HARQ buffer.

[0175] New transmissions and retransmissions are performed on the resources indicated in the sidelink grant specified in Clause 5.22.1.1, using the MCS selected as specified in Clause 8.1.3.1 and Clause 5.22.1.1 of TS38.214[7].

[0176] If the sidelink procedure is configured to perform the transmission of multiple MAC PDUs using sidelink resource allocation mode 2, then the procedure maintenance counter SL_RESOURCE_RESELECTION_COUNTER is used. This counter is not available for other sidelink procedure configurations.

[0177] The priority of the MAC PDU and SL-PRS (if available) is determined by the highest priority of the logical channel in the MAC PDU or SL-PRS, or the MAC CE.

[0178] If the sidelink HARQ entity requests a new transmission, then the sidelink process should:

[0179] 1> Store the MAC PDU in the associated HARQ buffer;

[0180] 1> Store the sidelink grant received from the sidelink HARQ entity;

[0181] 1> Generate and transmit as described below.

[0182] If the sidelink HARQ entity requests a retransmission, then the sidelink process should:

[0183] 1> Store the sidelink grant received from the sidelink HARQ entity;

[0184] 1> Generate and transmit as described below.

[0185] In order to generate a transmission, the sidelink process should:

[0186] 1> If there is no uplink transmission; or

[0187] 1> If the MAC entity can perform uplink and sidelink transmissions simultaneously during transmission; or

[0188] 1> If another MAC entity and the MAC entity are respectively capable of simultaneously performing uplink transmission and sidelink transmission during transmission; or

[0189] 1> If a MAC PDU exists in the uplink for this duration, except for MAC PDUs obtained from the Msg3 buffer, MSGA buffer, or those prioritized as specified in Clause 5.4.2.2, and sidelink transmissions take precedence over uplink transmissions:

[0190] 2> Instruct the physical layer to allow the transmission of SCI along with the associated sidelink transmission information, based on the stored sidelink information;

[0191] 2> Instruct the physical layer to generate a transmission based on the stored side link;

[0192] 2> If HARQ feedback has been enabled for the MAC PDU according to clause 5.22.1.4.2:

[0193] 3> Instruct the physical layer to monitor the PSFCH used for transmission and perform PSFCH reception as specified in Clause 5.22.1.3.2.

[0194] 2> If sl-PUCCH-Config is configured by RRC for stored sidelink permissions:

[0195] 3> Ensure the transmission of acknowledgments on the PUCCH, as specified in Clause 5.22.1.3.2.

[0196] 1> If this transfer corresponds to the last transfer of the MAC PDU and SL-PRS (if available):

[0197] 2> Decrement SL_RESOURCE_RESELECTION_COUNTER by 1 (if available).

[0198] Note 1: If the number of HARQ retransmissions selected by the MAC entity has been reached, or if a positive acknowledgment has been received for the transmission of the MAC PDU, or if negative acknowledgment only is enabled in the SCI and no negative acknowledgment has been received for the transmission of the MAC PDU, then the MAC entity determines that this transmission corresponds to the previous transmission of the MAC PDU used for sidelink resource allocation mode 2. How the previous transmission is determined in other cases depends on the UE implementation scheme.

[0199] 1> If the highest priority sl-MaxTransNum corresponding to the logical channel in the MAC PDU has been configured by RRC in the sl-CG-MaxTransNumList for sidelink granting and the number of MAC PDU transmissions has reached sl-MaxTransNum; or

[0200] 1> If a positive acknowledgment is received for this transmission of the MAC PDU pursuant to Clause 5.22.1.3.2, except for a positive acknowledgment for a multi-slot transmission of the MAC PDU (i.e., in the case of multiple TB), and there are remaining slots available for this MAC PDU; or

[0201] 1> If negative acknowledgment only is enabled in SCI and no negative acknowledgment is received for this transmission of the MAC PDU according to clause 5.22.1.3.2:

[0202] 2> Refresh the HARQ buffer of the associated sidelink process.

[0203] The transmission of a MAC PDU or SL-PRS takes precedence over the uplink transmission of the MAC entity or other MAC entities if the following conditions are met:

[0204] 1> If the MAC entity cannot simultaneously perform this-side link transmission and all uplink transmissions during transmission, and

[0205] 1> If, according to TS23.287

[19] , no uplink transmission is prioritized by the upper layer, and

[0206] 1> If none of the NR uplink MAC PDUs contains any MAC CE that is prioritized as described in Clause 5.4.3.1.3, and

[0207] 1> If ul-PrioritizationThres is configured, and if the highest priority value of all logical channels transmitted on the NR uplink is not lower than ul-PrioritizationThres, and

[0208] 1> If sl-PrioritizationThres is configured, and if the highest priority value of MAC CE in the logical channel or MAC PDU is lower than sl-PrioritizationThres.

[0209] Note 2: If the MAC entity is unable to perform this sidelink transmission at the same time as all uplink transmissions as specified in Clause 5.4.2.2 of TS 36.321

[22] , and priority ordering information is unavailable before the time of this sidelink transmission due to processing time constraints, then whether to perform this sidelink transmission depends on the UE implementation scheme.

[0210] [...]

[0211] 5.22.1.3.5 Sidelink processes associated with the dedicated SL-PRS resource pool

[0212] If the sidelink process is configured to perform multiple SL-PRS transmissions using sidelink resource allocation scheme 2, then the process maintains the counter SL_RESOURCE_RESELECTION_COUNTER. This counter is unavailable for other sidelink process configurations. For each new or retransmitted SL-PRS, the MAC entity should:

[0213] 1> If there is no uplink transmission; or

[0214] 1> If uplink transmission exists, and sidelink transmission takes precedence over uplink transmission:

[0215] 2> Instruct the physical layer to transmit SL-approved SCIs with associated SL-PRS transmission information on a dedicated SL-PRS resource pool;

[0216] 2> Instruct the physical layer to generate SL-PRS on a dedicated SL-PRS resource pool.

[0217] 1> If this transfer corresponds to the last transfer in the SL-PRS transfer:

[0218] 2> Decrement SL_RESOURCE_RESELECTION_COUNTER by 1 (if available).

[0219] The transmission of SL-PRS takes precedence over the uplink transmission of the MAC entity or another MAC entity if the following conditions are met:

[0220] 1> If the MAC entity cannot simultaneously perform this-side link transmission and all uplink transmissions during transmission, and

[0221] 1> If ul-PrioritizationThres is configured, and if the highest priority value of all logical channels transmitted on the NR uplink is not lower than ul-PrioritizationThres, and

[0222] 1> If sl-PrioritizationThres is configured, and if the value of SL-PRS priority is lower than sl-PrioritizationThres.

[0223] [...]

[0224] 5.22.1.5 Scheduling Request

[0225] In addition to Clause 5.4.4, a Scheduling Request (SR) is also used to request SL-SCH resources for a new transmission when triggered by a sidelink BSR (Clause 5.22.1.6), an SL-CSI report (Clause 5.22.1.7), or an SL-DRX command indication. A Scheduling Request (SR) is also used to request SL-PRS resources for a new transmission when triggered by an SL-PRS resource request (Clause 6.1.3.74). If configured, the MAC entity performs the SR procedure as specified in this clause, unless otherwise specified in Clause 5.4.4. For each sidelink logical channel, or for an SL-CSI report, or for an SL-DRX command indication, or for a sidelink consistent LBT fault recovery, or for an SL-PRS resource request, at most one PUCCH resource is configured for SR per UL BWP.

[0226] The SR configuration (clause 5.22.1.6) of the logical channel that triggers the sidelink BSR is also considered to be the corresponding SR configuration (clause 5.4.4) for the triggered SR. The priority value of the triggered SR corresponds to the priority value of the logical channel that triggered the SR.

[0227] Each sidelink logical channel and sidelink consistent LBT fault recovery can be mapped to zero or one SR configuration configured by RRC. If the SL-CSI reporting procedure is enabled by RRC, then the SL-CSI report is mapped to one SR configuration for all PC5-RRC connections. The SR configuration of an SL-CSI report triggered according to 5.22.1.7 is considered the corresponding SR configuration for the triggered SR (clause 5.4.4). The priority value of the triggered SR triggered by the SL-CSI report corresponds to the priority value of the sidelink CSI report MAC CE. The SR configuration of the SL-CSI report is considered the corresponding SR configuration for the triggered SR indicated by the SL-DRX command triggered according to 5.28.3. The priority value of the triggered SR indicated by the SL-DRX command corresponds to the priority value of the sidelink DRX command MAC CE. The SR configuration of a sidelink consistent LBT fault recovery triggered according to 5.31.2 is considered the corresponding SR configuration for the triggered SR (clause 5.4.4). The priority value of the triggering SR triggered by a sidelink consistent LBT fault recovery corresponds to the priority value of the SL LBT fault MAC CE. SL-PRS resource requests can be mapped to zero or one SR configuration configured by RRC. The priority value of the triggering SR triggered by an SL-PRS resource request corresponds to the priority value of the SL-PRS that triggered the SL-PRS resource request MAC CE.

[0228] All pending SRs triggered prior to MAC PDU assembly according to the sidelink BSR procedure (clause 5.22.1.6) will be cancelled, and when a MAC PDU is transmitted and this PDU contains an SL-BSR MAC CE, each corresponding sr-ProhibitTimer containing a buffer state until (and including) the last event that triggered the sidelink BSR (see clause 5.22.1.4) prior to MAC PDU assembly.

[0229] When a MAC PDU is transmitted and this PDU contains an SL LBT Fault MAC CE indicating a sidelink consistent LBT fault, or when all triggers for the SL BWP for a sidelink consistent LBT fault are cancelled, all pending SRs triggered under the sidelink consistent LBT fault recovery (clause 5.31.2) shall be cancelled and each corresponding sr-ProhibitTimer shall be stopped.

[0230] When the SL grants permission for all pending data available for transmission in the adaptable side link, all pending SRs triggered according to the side link BSR procedure (clause 5.22.1.6) will be cancelled and each corresponding sr-ProhibitTimer will be stopped.

[0231] If there is a pending SR triggered by a sidelink consistent LBT failure recovery that does not have a corresponding SR configuration, the MAC entity initiates a random access procedure on the serving cell (see Clause 5.1) and cancels the pending SR.

[0232] When the SL grants an adaptive sidelink CSI report MAC CE, when an SL-CSI report has been triggered but not canceled, or when a triggered SL-CSI report is canceled due to the delay not being fulfilled as specified in 5.22.1.7, pending SRs triggered for the destination based on the SL-CSI report will be canceled and each corresponding sr-ProhibitTimer will be stopped. When the SL grants an adaptive sidelink DRX command MAC CE, when an SL-DRX command indication has been triggered but not canceled, pending SRs triggered for the destination based on the SL-DRX command will be canceled and each corresponding sr-ProhibitTimer will be stopped. When the RRC is configured with sidelink resource allocation mode 2, all pending SRs triggered by sidelink BSRs, sidelink CSI reports, or sidelink DRX command indications will be canceled.

[0233] When a MAC PDU is transmitted and this PDU contains an SL-PRS resource request MAC CE, all pending SRs triggered prior to the MAC PDU assembly according to the SL-PRS resource request procedure (clause 5.22.1.12) shall be cancelled and each corresponding sr-ProhibitTimer shall be stopped, the SL-PRS resource request MAC CE containing the status of pending SL-PRS transmissions up to (and including) the last event that triggered the SL-PRS resource request prior to the MAC PDU assembly (see clause 5.22.1.12).

[0234] When an SL is permitted to accommodate all pending SL-PRS transmissions, all pending SRs triggered under the SL-PRS resource request procedure (clause 5.22.1.12) shall be cancelled, and each corresponding sr-ProhibitTimer shall be stopped.

[0235] […]

[0236] 5.22.1.12SL-PRS Resource Request

[0237] SL-PRS transmissions can be triggered by lower-layer signaling from a peer UE or an upper-layer signaling source within the UE itself. The SL-PRS resource request procedure is used to provide the gNB with information about the triggered SL-PRS transmission.

[0238] If sidelink resource allocation scheme 1 for SL-PRS transmission is configured, the MAC entity should:

[0239] 1> If a non-periodic SL-PRS is triggered:

[0240] 2> Trigger SL-PRS resource request.

[0241] 1> Otherwise, if periodic SL-PRS is triggered:

[0242] 2> Notify RRC to send an SL-PRS resource request.

[0243] MAC entities will:

[0244] 1> If an SL-PRS resource request is triggered and not cancelled:

[0245] 2> If UL-SCH resources are available for new transmissions, and these UL-SCH resources can accommodate SL-PRS resource request MAC CE plus its sub-header due to logical channel prioritization:

[0246] 3> Instruct the multiplexing and combining entity to generate SL-PRS resource request MAC CE.

[0247] 2> Otherwise:

[0248] 3> Trigger a scheduling request for SL-PRS resource request MAC CE, as specified in Clause 5.4.4.

[0249] When an SL is permitted to accommodate all pending SL-PRS transmissions, an SL-PRS resource request MAC CE can be cancelled. When a MAC PDU is transmitted and this PDU contains an SL-PRS resource request MAC CE, the SL-PRS resource request MAC CE, indicating a request for all pending SL-PRS transmissions since the last event that triggered the MAC CE, should be cancelled.

[0250] [...]

[0251] 6.1.3.35 Sidelink CSI Report MAC CE

[0252] The sidelink CSI report MAC CE is identified by a MAC subheader with the LCID specified in Table 6.2.4-1. The priority of the sidelink CSI report MAC CE is fixed at '1'. The sidelink CSI report MAC CE is defined as follows ( Figure 6 .1.3.35-1):

[0253] -RI: This field indicates the derived value of the rank indicator for sidelink CSI reporting as specified in Clause 8.5 of TS 38.214[7]. The field is 1 bit long and the value of the rank indicator field is mapped to the allowed rank indicator values ​​in ascending order, where '0' is mapped to the minimum allowed rank indicator value;

[0254] -CQI: This field indicates the derived value of the channel quality indicator used for sidelink CSI reporting as specified in Clause 8.5 of TS 38.214[7]. The field is 4 bits long;

[0255] -R: Reserved bit, set to 0.

[0256] Figure 6 1.3.35-1: Sidelink CSI Report MAC CE

[0257] [...]

[0258] • 6.1.3.74SL-PRS Resource Request MAC CE

[0259] The SL-PRS resource request MAC CE is identified by a MAC subheader with the eLCID specified in Table 6.2.1-1b. It has the following fields:

[0260] - Destination Index: The destination index field identifies the destination. This field is 5 bits long. The value is set to an index corresponding to the SL destination identifier associated with the same destination reported in the sl-PosTxResourceReqList (if it exists). The value is indexed sequentially from 0 in the same ascending order as the SL destination identifiers in the sl-PosTxResourceReqList as specified in TS 38.331[5]. When multiple lists are reported, the value is indexed sequentially across all lists in the same order as presented in the SidelinkUEInformationNR message;

[0261] -SL-PRS Priority: The priority of pending SL-PRS transmissions. This field is 3 bits long.

[0262] -SL-PRS Bandwidth: The minimum bandwidth of the requested pending SL-PRS transmission. This field is 5 bits long. This field is encoded the same as sl-PRS-Bandwidth in IE SL-PRS-QoS-Info as specified in TS 38.331[5], i.e., code point value 0 corresponds to the value "mhz5" of field sl-PRS-Bandwidth, code point value 1 corresponds to the value "mhz10" of field sl-PRS-Bandwidth, and so on;

[0263] -R: Reserved bit, set to 0.

[0264] Figure 6 1.3.74-1: SL-PRS Resource Request MAC Control Element

[0265] In some instances, a scheduling request (SR) transmission may be triggered based on a sidelink positioning reference signal (SL-PRS) resource request, which may be triggered based on one or more SL-PRS transmissions (e.g., pending SL-PRS transmissions). For example, a user equipment (UE) may trigger an SL-PRS resource request and / or generate an SL-PRS resource request media access control (MAC) element (CE) indicating the SL-PRS resource request in response to determining that one or more SL-PRS transmissions are pending. An SR transmission may be triggered to request one or more uplink resources for transmitting the SL-PRS resource request MAC CE. In some systems, a priority value indicating the priority of triggering an SR transmission triggered by an SL-PRS resource request corresponds to a priority value indicating the priority associated with the one or more SL-PRS transmissions (e.g., triggering an SL-PRS resource request and / or an SL-PRS resource request MAC CE). In such systems, if SL-PRS resources (associated with, for example, a shared or dedicated SL-PRS resource pool) or sidelink shared channel (SL-SCH) resources overlap (e.g., at least partially in the time and / or frequency domains) with uplink resources (e.g., physical uplink control channel (PUCCH) resources) for the timing of SR transmissions triggered by (pending) SR transmissions triggered by SL-PRS resource requests, a scenario may occur where SR transmissions triggered by SL-PRS resource requests for the one or more pending SL-PRS transmissions may not be prioritized even if the highest priority of the one or more pending SL-PRS transmissions is higher than the priority of the SL-PRS resources (and / or SL-PRS transmissions) or SL-SCH resources (and / or SL-SCH transmissions). This could result in (e.g., more important and / or urgent) pending SL-PRS transmissions being incorrectly de-prioritized and / or causing the UE to fail to fulfill service requests (e.g., for relevant ongoing location services). In some instances, the UE is not configured to perform SR transmissions to the network via the Uu interface while performing one or more SL transmissions (e.g., SL-PRS or SL-SCH) to one or more peer UEs via the side link (SL) or PC5 interface.

[0266] Figure 7 An exemplary scenario 700 is illustrated, relating to the execution of conflict prioritization operations for conflicts between SR and SL transmissions. First UE ( Figure 7 The "UE 1" in the table can identify the first pending SL-PRS 704 with a priority value of X. The first pending SL-PRS 704 can be triggered by the first UE (e.g., by a higher layer and / or upper layer of the first UE). It can be based on the data from the peer UE (UE 1). Figure 7The first pending SL-PRS 704 is triggered by the sidelink control information (SCI) of “UE 2” (and / or in response to receiving the SCI). An SR transmission 712 for an SL-PRS resource request MAC CE can be triggered at time T1 (e.g., by the first UE). The SR transmission 712 can be triggered based on an SL-PRS resource request, which can be triggered based on the first pending SL-PRS 704. For example, the first UE can trigger an SL-PRS resource request in response to determining that the first pending SL-PRS 704 is pending. The first UE can (in response to, for example, triggering the SL-PRS resource request) generate an SL-PRS resource request MAC CE indicating the SL-PRS resource request. The SR transmission 712 can be triggered at 702 to request one or more uplink resources for transmitting the SL-PRS resource request MAC CE (e.g., to the network).

[0267] After time T1, a second pending SL-PRS 706 with priority value = Y can be triggered at time T2. The second pending SL-PRS 706 can be triggered by a first UE (e.g., by a higher layer and / or upper layer of the first UE) and / or by an SCI from a peer UE or one or more other peer UEs. In some instances, one or more SR transmission opportunities 710 for the triggered SR (e.g., one or more PUCCH transmission opportunities for, for example, SR transmission 712 triggered at time T1 702) may or may not occur between time T1 and time T2. In some instances, the first UE can identify a potential conflict 714 between the SR transmission 712 (e.g., an SR transmission on an SR transmission opportunity) for the triggered SR (triggered at time T1 702) and an SL transmission 708 with priority value = Z at time T3. SL transmission 708 may include the transmission of SL data (e.g., on SL-SCH and / or PSSCH). SL transmission 708 may include SL-PRS transmissions (possibly associated with, for example, a shared or dedicated SL-PRS resource pool). SL transmission 708 may include SL-CSI transmissions. Conflict 714 may correspond to a time period where the SL resources of SL transmission 708 (e.g., SL-SCH resources, PSSCH resources, SL-PRS resources of a shared or dedicated SL-PRS resource pool, etc.) overlap with the uplink resources of SR transmission 712 (e.g., PUCCH resources that may correspond to the timing of SR transmissions configured and / or scheduled by the UE) (e.g., overlap in the time and / or frequency domains).

[0268] Based on the priority value of the first pending SL-PRS 704 that triggers the SL-PRS resource request (e.g., triggers the transmission 712 of 702 SR), the priority value indicating the priority of the SR transmission 712 can be determined as X. In some systems, in the exemplary scenario 700 where Y < Z < X, even though it is more advantageous to prioritize the SR transmission 712, the SR transmission 712 can be deprioritized because the priority of the second pending SL-PRS 706 (identified by the priority value Y) is higher than the priority of the SL transmission 708 (identified by the priority value Z). For example, the first UE can transmit the SL transmission 708 to the peer UE at time T3 and / or may not transmit the SR transmission 712 to the network at time T3. In some instances, a lower priority value can correspond to a higher priority, such that Y (indicating the priority of the second pending SL-PRS 706) being less than Z (indicating the priority of the SL transmission 708) indicates that the priority of the second pending SL-PRS 706 is higher than the priority of the SL transmission 708. In some instances, the UE can be configured with a set of eight priority values from 1 to 8, where the priority value '1' corresponds to the highest priority and / or the priority value '8' corresponds to the lowest priority.

[0269] According to some embodiments of the present disclosure, the first UE can perform an (enhanced) conflict prioritization operation 716 to handle conflicts 714 with improved prioritization. The conflict prioritization operation 716 can include determining the SR priority value of the SR transmission 712, which takes into account the priorities of the set of (pending) SL-PRSs (e.g., a set of one or more SL-PRSs) associated with the SL-PRS resource request (e.g., triggering the transmission 712 of 702 SR). For example, the set of SL-PRSs can include all pending SL-PRSs associated with the SL-PRS resource request.

[0270] In some instances, the first UE may determine a set of priority values ​​that includes one or more priority values ​​of the SL-PRS set (e.g., priority values ​​of all SL-PRS in the SL-PRS set), and / or may determine an SR priority value based on the set of priority values ​​(e.g., all priority values ​​in the priority value set). In some instances, the SL-PRS set may include SL-PRS that trigger an SL-PRS resource request and / or an SL-PRS resource request MAC CE (e.g., pending SL-PRS). For example, the SL-PRS set may include all SL-PRS that trigger an SL-PRS resource request (and / or all pending SL-PRS). In some instances, the SL-PRS set may include SL-PRS indicated by an SL-PRS resource request MAC CE (e.g., pending SL-PRS). For example, the SL-PRS set may include all SL-PRS indicated by an SL-PRS resource request MAC CE (and / or all pending SL-PRS).

[0271] In some instances, the first UE may generate and / or maintain a pending SL-PRS data structure indicating a set of pending SL-PRS (e.g., an SL-PRS set) and / or priority values ​​(e.g., a set of priority values) associated with the set of pending SL-PRS (e.g., the current pending SL-PRS). The first UE may generate and / or update the pending SL-PRS data structure to include first information associated with the first pending SL-PRS 704 in response to triggering and / or identifying the first pending SL-PRS 704. The first information may include the priority value of the first pending SL-PRS 704 = X. In some instances, the first information may include the first pending SL-PRS 704 (e.g., it may be generated by the first UE). The first UE may store the pending SL-PRS data structure in memory. The first UE may update the pending SL-PRS data structure to include second information associated with the second pending SL-PRS 706 (e.g., by accessing memory and / or storing the second information in memory) in response to triggering and / or identifying the second pending SL-PRS 706. In some instances, the second information may include the priority value = Y of the second pending SL-PRS 706. In some instances, the second information may include the second pending SL-PRS 706 (e.g., it may be generated by the first UE). In some instances, in response to triggering and / or identifying one or more other pending SL-PRS (e.g., associated with one or more peer UEs), the first UE may update the pending SL-PRS data structure to include information associated with said one or more other pending SL-PRS (e.g., priority values ​​and / or other information). In some instances, the conflict prioritization operation 716 may include accessing memory and / or referencing a pending SL-PRS data structure to determine a set of SL-PRS and / or a set of priority values ​​(and / or subsequently using, for example, the determined set of SL-PRS and / or the determined set of priority values ​​to determine an SR priority value). In some instances, the SL-PRS set may include pending SL-PRS (e.g., all pending SL-PRS) indicated by the pending SL-PRS data structure. In some instances, the priority value set may include pending SL-PRS (e.g., all pending SL-PRS) indicated by the pending SL-PRS data structure. In some instances, the priority value set may include priority values ​​(e.g., all priority values) indicated by the pending SL-PRS data structure. In some instances, the pending SL-PRS data structure includes an SL-PRS resource request MAC CE. In some instances, the SL-PRS resource request MAC CE is generated based on the pending SL-PRS data structure.

[0272] In some instances, the conflict prioritization operation 716 may include performing one or more operations (e.g., one or more mathematical and / or logical operations) on a set of priority values to determine the SR priority value. In some instances, the conflict prioritization operation 716 may include analyzing the set of priority values to identify a target priority value (among the set of priority values) that indicates the highest priority among the priorities indicated by the set of priority values, and determining the SR priority value based on the target priority value. In a scenario where a lower priority value corresponds to a higher priority, the target priority value may be the lowest (e.g., smallest) priority value among the set of priority values. Embodiments are contemplated where a higher priority value may correspond to a higher priority, where the target priority value may be the highest (e.g., largest) priority value among the set of priority values. In some instances, the SR priority value may be set to be equal to the target priority value (e.g., the lowest priority value among the set of priority values in a scenario where a lower priority value corresponds to a higher priority).

[0273] The conflict prioritization operation 716 may include using the SR priority value associated with the SR transmission 712 and the priority value of the SL transmission 708 (e.g., Z) to select one of the SR transmission 712 or the SL transmission 708 for transmission. For example, a first UE may select the SR transmission 712 for transmission based on the SR priority value of the SR transmission 712 indicating a higher priority than the priority value of the SL transmission 708 (e.g., Z). For example, in a scenario where a lower priority value corresponds to a higher priority, the first UE may select the SR transmission 712 for transmission based on the SR priority value of the SR transmission 712 being less than the priority value of the SL transmission 708 (e.g., Z). Thus, in a scenario where Y < Z < X, the SR priority value may be set to Y (e.g., based on Y being the lowest priority value among the set of priority values) via the conflict prioritization operation 716, and the SR transmission 712 may be selected for transmission based on the SR priority value (e.g., Y) being less than the priority value of the SL transmission 708 (e.g., Z) (e.g., indicating that the priority of the SR transmission 712 is greater than the priority of the SL transmission 708). Thus, according to some embodiments, performing the conflict prioritization operation 716 causes the SR transmission 712 to be (correctly) prioritized over the SL transmission 708, thereby enabling improved operation of the first UE and improved (and / or more efficient) communication with one or more peer UEs and / or the network that meets service requirements (e.g., for an ongoing positioning service).

[0274] In some instances, the first UE may determine the SR priority value (and / or the priority value associated with the SL-PRS Resource Request MAC CE) as a predefined (and / or fixed) value (e.g., the predefined value could be 1 to indicate the highest priority). In some instances, the first UE may determine the SR priority value (and / or the priority value associated with the SL-PRS Resource Request MAC CE) based on configurations from (e.g., the first UE's) higher layer and / or upper layer or Radio Resource Control (RRC). In some instances, the SL-PRS Resource Request MAC CE may include multiple SL-PRS priority values ​​indicating priorities associated with multiple (different) peer and / or (destination) UEs and / or multiple (different) SL-PRS bandwidths.

[0275] In some instances, the first UE can execute a selected transmission (e.g., SR transmission 712 or SL transmission 708) chosen by the conflict prioritization operation 716. For example, if the conflict prioritization operation 716 selects SR transmission 712, the first UE can transmit SR transmission 712 to the network via the uplink resources of SR transmission 712 (e.g., PUCCH resources that may correspond to the timing of the SR transmission configured and / or scheduled by the UE) during a third time T3. If the conflict prioritization operation 716 selects SL transmission 708, the first UE can transmit SL transmission 708 to the network via the SL resources of SL transmission 708 (e.g., SL-SCH resources, PSSCH resources, SL-PRS resources of a shared or dedicated SL-PRS resource pool, etc.) during a third time T3.

[0276] In some instances, (in addition to and / or as a supplement to triggering 702 in response to an SL-PRS resource request and / or an SL-PRS resource request MAC CE) a 702SR transmission 712 may be triggered in response to one or more requests and / or signals (e.g., by the first UE). For example, the one or more requests and / or signals (e.g., triggering 702SR transmission 712) may include an Uplink Buffer State Report (ULBSR), a Sidelink Buffer State Report (SL BSR), and / or one or more MAC CEs. In some instances, when the configuration and / or capabilities of the first UE do not allow the first UE to perform both SL transmission 708 and SR transmission 712 simultaneously (e.g., making it impossible for the first UE to perform both SL transmission 708 and SR transmission 712 simultaneously), the first UE may perform a conflict prioritization operation 716 (using one or more of the techniques provided herein). In some instances, where the SL resources associated with SL transmission 708 include SL-PRS resources in a shared or dedicated SL-PRS resource pool, a first UE may perform a conflict prioritization operation 716 in response to determining (e.g., during a third time T3) that the SL-PRS resources overlap with the uplink resources of SR transmission 712 (e.g., PUCCH resources that may correspond to the timing of the SR transmission configured and / or scheduled by the UE to perform SR transmission 712) (e.g., at least partially in the time and / or frequency domains). The first UE can determine which of SR transmission 712 or SL transmission 708 to use for transmission by performing conflict prioritization operation 716 (using one or more of the techniques provided herein). In some instances, transmissions not selected by conflict prioritization operation 716 (de-prioritized) (e.g., SR transmission 712 or SL transmission 708) may be dropped and / or rescheduled.

[0277] One, some, and / or all of the foregoing examples, concepts, techniques, and / or embodiments can be formed and / or combined to form new embodiments.

[0278] In some instances, the embodiments disclosed herein may be implemented independently and / or separately. Alternatively and / or additionally, combinations of the embodiments described herein may be implemented. Alternatively and / or additionally, combinations of the embodiments described herein may be implemented in parallel and / or simultaneously.

[0279] The various techniques, embodiments, methods, and / or alternatives disclosed herein can be performed independently and / or separately. Alternatively and / or additionally, the various techniques, embodiments, methods, and / or alternatives disclosed herein can be combined and / or implemented using a single system. Alternatively and / or additionally, the various techniques, embodiments, methods, and / or alternatives disclosed herein can be implemented in parallel and / or simultaneously.

[0280] To enhance 3GPP specifications, such as 3GPP TS 38.321V18.2.0 (2024-06), for wireless communications according to some embodiments herein, Enhancement 1 is provided herein. Enhancement 1 reflects implementations according to some embodiments herein and includes modifications to the 3GPP specification. According to some embodiments, at least a portion of Enhancement 1 may be implemented.

[0281] Enhancement 1 can be implemented according to one or more embodiments of this disclosure. In Enhancement 1, Additions 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14 and / or 15 are made to 3GPP TS 38.321V18.2.0 (2024-06). To distinguish Additions X (where X = 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15) from the original content contained in 3GPP TS 38.321V18.2.0 (2024-06), Additions X are in bold and preceded by the term "Addition X begins:" and followed by the term "Addition X ends". In Enhancement 1, deletions 1, 2, and / or 3 are made to remove portions of 3GPP TS 38.321V18.2.0 (2024-06). To identify the portions of 3GPP TS 38.321V18.2.0 (2024-06) that will be removed by deletion X (where X = 1, 2, 3), the portions to be removed by deletion X are in bold and preceded by the term "Deletion X begins:" and followed by the term "Deletion X ends". In some instances, embodiments of this disclosure may be implemented via one, some, or all of additions 1 to 15 and / or one, some, or all of deletions 1 to 3 in Enhancement 1.

[0282] Enhancement 1:

[0283] 5.4.4 Scheduling Request

[0284] A scheduling request (SR) is used to request UL-SCH resources for a new transfer.

[0285] A MAC entity may be configured with zero, one, or more SR configurations. An SR configuration consists of a set of PUCCH resources for SR spanning different BWPs and cells. For logical channels, or for SCell beam fault recovery (see Clause 5.17) and for consistency LBT fault recovery (see Clause 5.21), at most one PUCCH resource is configured per BWP for SR. For logical channels serving radio bearers configured with SDTs, no PUCCH resources for SR are configured for the SDTs. For beam fault recovery of the BFD-RS set serving a cell, at most two PUCCH resources are configured per BWP for SR. A dedicated SR configuration is configured for positioning measurement gap activation / deactivation requests.

[0286] [...]

[0287] As long as at least one SR is pending, for each pending SR, the MAC entity will:

[0288] 1> If the MAC entity is not configured with a valid PUCCH resource for pending SRs; and

[0289] 1> If there is no ongoing RACH-free LTM cell handover; and

[0290] 1> If rach-LessHO is not configured:

[0291] 2> Initiate a random access procedure on SpCell (see Clause 5.1) and cancel the pending SR.

[0292] 1> Otherwise, for the SR configuration corresponding to the pending SR:

[0293] 2> When the MAC entity has an SR transmission opportunity on a valid PUCCH resource for the configured SR; and

[0294] 2> If sr-ProhibitTimer is not running during the SR transmission timing; and

[0295] 2> If the PUCCH resource used for SR transmission timing does not overlap with the measurement gap:

[0296] 3> If the PUCCH resource used for SR transmission timing does not overlap with UL-SCH and SL-SCH resources, the simultaneous transmission of the UL-SCH resource and SR is not permitted by the configuration of simultaneousPUCCH-PUSCH, simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup, simultaneousSR-PUSCH-diffPUCCH-Groups, simultaneousPUCCH-PUSCH-SamePriority, or simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup; or

[0297] 3> If the MAC entity can perform this SR transfer simultaneously with the transfer of SL-SCH resources; or

[0298] 3> If the MAC entity is configured with lch-based Prioritization, and the PUCCH resource used for the SR transmission timing does not overlap with the uplink grant PUSCH duration received in the random access response, or with the uplink grant PUSCH duration addressed to the temporary C-RNTI, or with the PUSCH duration of the MSGA payload, and the PUCCH resource used for the SR transmission timing of the pending SR triggered as specified in Clause 5.4.5 overlaps with any other UL-SCH resource, and the physical layer may transmit the SR on a valid PUCCH resource used for the SR, and the logical channel triggering the SR has a higher priority than the uplink grant for any UL-SCH resource, then the SR can be transmitted on a valid PUCCH resource used for the SR. The priority of uplink permission, wherein uplink permission has not been de-prioritized and its simultaneous transmission with SR is not permitted by the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCHgroups or simultaneousPUCCH-PUSCH-SamePriority or simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup, and the priority of uplink permission is determined as specified in Clause 5.4.1; or

[0299] 3> If both sl-PrioritizationThres and ul-PrioritizationThres are configured, and the PUCCH resource for the timing of the SR transmission of the triggered pending SR as specified in Clause 5.22.1.5 overlaps with any UL-SCH resource carrying the MAC PDU, and the priority value of the triggering SR determined as specified in Clause 5.22.1.5 is lower than sl-PrioritizationThres, and the highest priority value of the logical channel in the MAC PDU is higher than or equal to ul-PrioritizationThres, and any MAC CE that is prioritized as described in Clause 5.4.3.1.3 according to TS 23.287

[19] is not included in the MAC PDU, and the MAC PDU is not prioritized by the upper layer; or

[0300] 3> If the SL-SCH resource "Add 1 Start: or SL-CSI resource Add 1 End" overlaps with the PUCCH resource used for the timing of an SR transmission for a pending SR that is triggered (as specified in Clause 5.4.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and any transmission on the SL-SCH resource has not been prioritized as described in Clause 5.22.1.3.1a, or the priority value of the logical channel triggering the SR is lower than ul-PrioritizationThres (if configured); or

[0301] 3> If the SL-SCH resource "Add 2 Start: or SL-CSI resource Add 2 End" overlaps with the PUCCH resource used for the timing of the SR transmission of a pending SR that is triggered (as specified in Clause 5.22.1.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and the priority of the triggering SR determined as specified in Clause 5.22.1.5 is higher than the priority of the MAC PDU determined for the SL-SCH resource as specified in Clause 5.22.1.3.1a; or

[0302] 3> If the SL-PRS resource overlaps with the PUCCH resource used for the timing of a pending SR transmission (as specified in Clause 5.4.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission on the SL-PRS resource, and any transmission on the SL-PRS resource that has not been prioritized or triggered by the logical channel as described in Clause 5.22.1.3.1a "Add 3 to start: or Clause 5.22.1.3.5 Add 3 to end", has a priority value lower than ul-PrioritizationThres (if configured); or

[0303] 3> If the SL-PRS resource overlaps with the PUCCH resource used for the timing of an SR transmission for a pending SR that is triggered (as specified in Clause 5.22.1.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and for the SL-PRS resource, the priority of the triggering SR determined as specified in Clause 5.22.1.5 is higher than the priority of the SL-PRS (if available) determined as specified in Clause 5.22.1.3.1a: "Delete 1 start: and delete 1 end" "Add 4 start: and / or add 4 end" "Add 5 start: or the priority of the SL-PRS in Clause 5.22.1.3.5 add 5 end":

[0304] Add 6 to start:

[0305] 3> If the SL-PRS resource overlaps with the PUCCH resource for the timing of an SR transmission for a pending SR that is triggered (as specified in Clause 5.22.1.5), and the MAC entity cannot perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggering SR determined as specified in Clause 5.22.1.5 is higher than the priority of the SL-PRS (if available) determined for the SL-PRS resource as specified in Clause 5.22.1.3.5:

[0306] Add 6 to finish

[0307] 4> Treat SR transfers as priority SR transfers.

[0308] 4> Treat other overlapping uplink grants (if they exist) as de-prioritized uplink grants, except for overlapping uplink grants that are allowed to be transmitted simultaneously by the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups or simultaneousPUCCH-PUSCH-SamePriority or simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup;

[0309] 4> If de-prioritizing uplink granting is a configured uplink granting that has started its PUSCH and is configured with autonomousTx:

[0310] 5> Stop the configuredGrantTimer used by the corresponding HARQ process for de-prioritizing uplink grants;

[0311] 5> Stop the cg-RetransmissionTimer used for the corresponding HARQ process that is used to de-prioritize uplink grants.

[0312] [...]

[0313] 5.22.1.5 Scheduling Request

[0314] In addition to Clause 5.4.4, a Scheduling Request (SR) is also used to request SL-SCH resources for a new transmission when triggered by a sidelink BSR (Clause 5.22.1.6), an SL-CSI report (Clause 5.22.1.7), or an SL-DRX command indication. A Scheduling Request (SR) is also used to request SL-PRS resources for a new transmission when triggered by an SL-PRS resource request (Clause 6.1.3.74). If configured, the MAC entity performs the SR procedure as specified in this clause, unless otherwise specified in Clause 5.4.4. For each sidelink logical channel, or for an SL-CSI report, or for an SL-DRX command indication, or for a sidelink consistent LBT fault recovery, or for an SL-PRS resource request, at most one PUCCH resource is configured for SR per UL BWP.

[0315] …

[0316] Each sidelink logical channel and sidelink consistent LBT fault recovery can be mapped to zero or one SR configuration configured by RRC. If the SL-CSI reporting procedure is enabled by RRC, then the SL-CSI report is mapped to one SR configuration for all PC5-RRC connections. The SR configuration of an SL-CSI report triggered according to 5.22.1.7 is considered the corresponding SR configuration for the triggered SR (clause 5.4.4). The priority value of the triggered SR triggered by the SL-CSI report corresponds to the priority value of the sidelink CSI report MAC CE. The SR configuration of the SL-CSI report is considered the corresponding SR configuration for the triggered SR indicated by the SL-DRX command triggered according to 5.28.3. The priority value of the triggered SR indicated by the SL-DRX command corresponds to the priority value of the sidelink DRX command MAC CE. The SR configuration of a sidelink consistent LBT fault recovery triggered according to 5.31.2 is considered the corresponding SR configuration for the triggered SR (clause 5.4.4). The priority value of the triggering SR triggered by side-link consistent LBT fault recovery corresponds to the priority value of the SL LBT fault MAC CE. SL-PRS resource requests can be mapped to zero or one SR configuration configured by RRC.

[0317] The priority value of the trigger SR triggered by the SL-PRS resource request corresponds to the "Add 9 Start: SL-PRS triggers delete 2 end" SL-PRS resource request MAC CE "Add 8 Start: SL-PRS add 8 end" priority value of "Add 7 Start: minimum / minimum add 7 end".

[0318] The priority value of the triggering SR triggered by the SL-PRS resource request corresponds to the "delete 3 start: the deletion 3 ends" "add 11 start: all add 11 ends" "add 12 start: multiple add 12 ends" SL-PRS priority value "add 10 start: minimum / lowest add 10 ends".

[0319] • 6.1.3.74SL-PRS Resource Request MAC CE

[0320] The SL-PRS resource request MAC CE is identified by a MAC subheader with an eLCID as specified in Table 6.2.1-1b. The phrase "Start with 13: The priority of the SL-PRS resource request MAC CE is fixed at '1'. End with 13" has the following fields:

[0321] The SL-PRS resource request MAC CE is identified by a MAC subheader with an eLCID as specified in Table 6.2.1-1b. "Add 14 to begin: The priority of the SL-PRS resource request MAC CE is the highest priority (e.g., minimum / lowest value) of the SL-PRS priority indicated in the MAC CE. Add 14 to end" has the following fields:

[0322] The SL-PRS resource request MAC CE is identified by a MAC subheader with an eLCID as specified in Table 6.2.1-1b. "Add 15 to begin: The priority of the SL-PRS resource request MAC CE is configured by a higher layer, upper layer, or RRC. Add 15 to end." It has the following fields:

[0323] - Destination Index: The destination index field identifies the destination. This field is 5 bits long. The value is set to an index corresponding to the SL destination identifier associated with the same destination reported in the sl-PosTxResourceReqList (if it exists). The value is indexed sequentially from 0 in the same ascending order as the SL destination identifiers in the sl-PosTxResourceReqList as specified in TS 38.331[5]. When multiple lists are reported, the value is indexed sequentially across all lists in the same order as presented in the SidelinkUEInformationNR message;

[0324] -SL-PRS Priority: The priority of pending SL-PRS transmissions. This field is 3 bits long.

[0325] -SL-PRS Bandwidth: The minimum bandwidth of the requested pending SL-PRS transmission. This field is 5 bits long. This field is encoded the same as sl-PRS-Bandwidth in IE SL-PRS-QoS-Info as specified in TS 38.331[5], i.e., code point value 0 corresponds to the value "mhz5" of field sl-PRS-Bandwidth, code point value 1 corresponds to the value "mhz10" of field sl-PRS-Bandwidth, and so on;

[0326] -R: Reserved bit, set to 0.

[0327] Figure 6 1.3.74-1: SL-PRS Resource Request MAC Control Element

[0328] Figure 8 This is a flowchart 800 from the perspective of a first UE according to an exemplary embodiment. In step 805, the first UE determines a first priority value associated with an SL transmission to a second UE (e.g., a peer UE). In step 810, the first UE determines a second priority value associated with an SR transmission to a network node (e.g., a base station, gNB, etc.) based on one or more priority values ​​associated with one or more SL-PRS transmissions, the one or more SL-PRS transmissions being associated with an SL-PRS resource request on which the SR transmission is triggered. In step 815, the first UE selects one of a plurality of transmissions, including SL transmissions and SR transmissions, based on the first priority value and the second priority value. In step 820, the first UE executes the selected transmission. For example, if an SR transmission is selected, the first UE can execute the SR transmission, or if an SL transmission is selected, the first UE can execute the SL transmission.

[0329] In some instances, the first UE may discard and / or reschedule a second transmission among the plurality of transmissions that is different from the selected transmission. For example, if the SR transmission is selected, the first UE may discard and / or reschedule the SL transmission, or if the SL transmission is selected, the first UE may discard and / or reschedule the SR transmission.

[0330] In some instances, the first UE determines a first priority value based on the configuration (e.g., RRC configuration) and / or the type of SL transmission. The type may indicate whether the SL transmission is an SL data transmission (e.g., on SL-SCH and / or PSSCH), an SL-PRS transmission using SL-PRS resources from a shared SL-PRS resource pool, an SL-PRS transmission using SL-PRS resources from a dedicated SL-PRS resource pool, an SL-CSI transmission, or other types of SL transmission.

[0331] In one embodiment, SL transmissions are associated with SL resources that overlap with Physical Uplink Control Channel (PUCCH) resources associated with SR transmissions.

[0332] In one embodiment, performing a selected transmission includes performing an SL transmission to a second UE (and / or one or more other peer UEs) on SL resources in response to selecting an SL transmission from the plurality of transmissions, or performing an SR transmission to a network node on PUCCH resources in response to selecting an SR transmission from the plurality of transmissions.

[0333] In one embodiment, determining a second priority value associated with an SR transmission includes analyzing the one or more priority values ​​to identify a third priority value indicating the highest priority among the one or more priorities indicated by the one or more priority values, and determining the second priority value based on the third priority value. In some instances, a lower priority value corresponds to a higher priority, and therefore the third priority value may correspond to the lowest (e.g., minimum) priority value among the one or more priority values. In some instances, the second priority value may be set equal to the third priority value (e.g., the lowest priority value among the one or more priority values ​​associated with the one or more SL-PRS transmissions).

[0334] In one embodiment, the first UE is configured to perform SL transmission and SR transmission at non-overlapping times. For example, the configuration and / or capabilities of the first UE allow it to perform SL transmission and SR transmission at non-overlapping times.

[0335] In one embodiment, the configuration and / or capabilities of the first UE do not allow the first UE to perform SL transmission and SR transmission simultaneously (e.g., making it impossible for the first UE to perform SL transmission and SR transmission simultaneously).

[0336] In one embodiment, SL transmission includes SL data transmission.

[0337] In one embodiment, an SL transport includes an SL-PRS transport associated with a dedicated SL-PRS resource pool. For example, the SL resource associated with the SL transport may be an SL-PRS resource of a dedicated SL-PRS resource pool.

[0338] In one embodiment, the first UE selects SR transmission based on a second priority value associated with SR transmission indicating a higher priority than a first priority value associated with SL transmission. In some instances, a lower priority value corresponds to a higher priority, and therefore the first UE may select SR transmission based on the second priority value being lower than the first priority value.

[0339] In one embodiment, the first UE selects an SL transmission based on a first priority value associated with the SL transmission indicating a higher priority than a second priority value associated with the SR transmission. In some instances, a lower priority value corresponds to a higher priority, and therefore the first UE may select an SL transmission based on the first priority value being lower than the second priority value.

[0340] In one embodiment, the first UE generates an SL-PRS resource request MAC CE. In some instances, the SL-PRS resource request MAC CE instructs the SL-PRS resource request and / or is used to deliver the SL-PRS resource request to the network node.

[0341] In one embodiment, the one or more SL-PRS transmissions include a plurality of pending SL-PRS transmissions, and the one or more priority values ​​include a plurality of priority values ​​associated with the plurality of pending SL-PRS transmissions. In some instances, the SL-PRS Resource Request MAC CE indicates the plurality of pending SL-PRS transmissions and the plurality of priority values. In some instances, the SL-PRS Resource Request MAC CE includes a plurality of information sets associated with the plurality of pending SL-PRS transmissions. In some instances, each of the plurality of information sets indicates a priority value (and / or other information) for an SL-PRS transmission among the plurality of pending SL-PRS transmissions.

[0342] In one embodiment, the SL-PRS resource request MAC CE indicates one or more priority values.

[0343] In one embodiment, the SL-PRS Resource Request MAC CE indicates information associated with the one or more SL-PRS transmissions. For example, the SL-PRS Resource Request MAC CE can be used to provide a network node with information associated with pending SL-PRS transmissions (associated with one or more peer UEs).

[0344] In some instances, a first UE may identify a first pending SL-PRS transmission among the one or more SL-PRS transmissions. In some instances, the first pending SL-PRS transmission may be triggered by the first UE (e.g., by a higher layer and / or upper layer of the first UE). An SL-PRS resource request may be triggered (e.g., by the first UE) in response to determining that the first pending SL-PRS transmission is pending (e.g., pending for transmission to one or more UEs). In some instances, the first UE may trigger an SR transmission in response to triggering an SL-PRS resource request and / or determining that the first pending SL-PRS transmission is pending. In some instances, after identifying the first pending SL-PRS transmission and / or triggering an SL-PRS resource request, the first UE may identify a second pending SL-PRS transmission among the one or more SL-PRS transmissions. In some instances, the second pending SL-PRS transmission may be triggered by the first UE (e.g., by a higher layer and / or upper layer of the first UE). An SL-PRS resource request can be triggered (e.g., by a first UE) in response to determining that a first pending SL-PRS transmission is pending (e.g., pending for transmission to one or more UEs). The first UE can generate an SL-PRS resource request MAC CE to indicate: information associated with the first pending SL-PRS transmission to be reported to the network node (e.g., the information may include the priority value of the first pending SL-PRS transmission and / or one or more destination UEs of the first pending SL-PRS transmission), information associated with a second pending SL-PRS transmission to be reported to the network node (e.g., the information may include the priority value of the second pending SL-PRS transmission and / or one or more destination UEs of the second pending SL-PRS transmission), and / or information associated with one or more other pending SL-PRS transmissions to be reported to the network node.

[0345] In some instances, the first UE generates the multiple transmissions, including SR transmissions and SL transmissions. The first UE may group the (generated) multiple transmissions together and / or may store the (grouped) multiple transmissions (e.g., as a group) in memory. The first UE may store in memory indications of priority values ​​(e.g., a first priority value and / or a second priority value) and / or other information associated with the (e.g., grouped) multiple transmissions. In some instances, the UE accesses memory to evaluate the priority values ​​and / or other information associated with the (e.g., grouped) multiple transmissions, and determines, based on the evaluation, to select a chosen transmission from the (e.g., grouped) multiple transmissions (e.g., the UE may access memory and / or evaluate priority values ​​to determine the selection of a chosen transmission in response to detecting at least partial overlap between SL resources associated with an SL transmission and PUCCH resources associated with an SR transmission), without selecting one or more other transmissions among the (e.g., grouped) multiple transmissions. In some instances, in response to selecting a chosen transmission, the selected transmission may be retrieved from memory and / or transmitted using available resources (e.g., SL resources if an SL transmission is selected, or SR resources if an SR transmission is selected). Embodiments in which priority values ​​and the plurality of transmissions are stored in a single memory unit or in different memory units are anticipated (e.g., the memory unit can be accessed to evaluate priority values ​​and / or retrieve selected transmissions). In some instances, the priority values ​​and the plurality of transmissions are stored in a single data structure. In some instances, the plurality of transmissions are stored in a transmission data structure, and the priority values ​​are stored in a priority value data structure. The transmission data structure may include an indication of a link between a transmission in the transmission data structure and a corresponding priority value in the priority value data structure. The priority value data structure may include an indication of a link between a priority value in the priority value data structure and a corresponding transmission in the transmission data structure.

[0346] Now for reference Figure 3 and Figure 4In an exemplary embodiment of the first UE, the apparatus 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the first UE to: (i) determine a first priority value associated with an SL transmission to a second UE; (ii) determine a second priority value associated with an SR transmission to a network node based on one or more priority values ​​associated with one or more SL-PRS transmissions, the one or more SL-PRS transmissions being associated with an SL-PRS resource request on which the SR transmission is triggered; (iii) select one of a plurality of transmissions including SL transmissions and SR transmissions based on the first and second priority values; and (iv) execute the selected transmission. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0347] Figure 9 This is a flowchart 900 according to an exemplary embodiment, viewed from the perspective of a first UE. In step 905, the first UE determines a first priority value associated with a first SL transmission to a second UE. In step 910, the first UE determines a second priority value associated with an SR transmission to a network node (e.g., a base station, gNB, etc.) based on one or more priority values ​​associated with one or more second SL transmissions (e.g., one or more SL-PRS transmissions and / or one or more other types of SL transmissions), the one or more second SL transmissions being associated with an SL resource request on which the SR transmission was triggered. In step 915, the first UE selects one of the first SL transmission or the SR transmission from a plurality of transmissions including the first SL transmission and the SR transmission based on the first priority value and the second priority value. In step 920, the first UE executes the selected transmission.

[0348] In some instances, the first UE generates an SL-PRS resource request message (e.g., an SL-PRS resource request MAC CE and / or other types of resource request messages). In some instances, the SL-PRS resource request message indicates an SL-PRS resource request and / or is used to deliver the SL-PRS resource request to the network node.

[0349] In some instances, the one or more second SL transmissions include multiple pending SL transmissions, and the one or more priority values ​​include multiple priority values ​​associated with the multiple pending SL transmissions. In some instances, the SL-PRS Resource Request MAC CE indicates the multiple pending SL transmissions and the multiple priority values. In some instances, the SL-PRS Resource Request MAC CE includes multiple sets of information associated with the multiple pending SL transmissions. In some instances, each of the multiple sets of information indicates the priority value (and / or other information) of the SL-PRS transmission among the multiple pending SL transmissions.

[0350] In one embodiment, determining a second priority value associated with SR transmission includes analyzing the one or more priority values ​​to identify a third priority value that indicates the highest priority among one or more priorities indicated by the one or more priority values, and determining the second priority value based on the third priority value.

[0351] In one embodiment, the first UE is configured to perform a first SL transmission and an SR transmission at non-overlapping times.

[0352] Now for reference Figure 3 and Figure 4 In one exemplary embodiment of the UE, the apparatus 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the first UE to: (i) determine a first priority value associated with a first SL transmission to a second UE; (ii) determine a second priority value associated with a SR transmission to a network node based on one or more priority values ​​associated with one or more second SL transmissions, the one or more second SL transmissions being associated with an SL resource request on which the SR transmission is triggered; (iii) select one of a plurality of transmissions, including the first SL transmission and the SR transmission, based on the first priority value and the second priority value; and (iv) execute the selected transmission. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0353] Figure 10This is a flowchart 1000 according to an exemplary embodiment, viewed from the perspective of a first UE. The first UE cannot simultaneously (and / or simultaneously) execute an SR transmission triggered by an SL-PRS resource request with an SL transmission associated with a first priority value. This is, for example, at least in part, due to the first UE's configuration and / or capabilities not allowing it to simultaneously (and / or simultaneously) execute SL and SR transmissions. In step 1005, the first UE determines a second priority value associated with the SR transmission based on the lowest (e.g., minimum) priority value among the priority values ​​indicated by the SL-PRS resource request MAC CE for one or more pending SL-PRS transmissions. The lowest priority value may correspond to the highest priority among the priorities indicated by the priority values ​​indicated by the SL-PRS resource request MAC CE. Priority values ​​may include all priority values ​​indicated by the SL-PRS resource request MAC CE, and therefore the lowest priority value (on which the second priority value is determined) may correspond to the lowest priority value indicated by the SL-PRS resource request MAC CE. In some instances, the second priority value may be set equal to the lowest priority value. In step 1010, the first UE performs an SL transmission to the second UE (e.g., a peer UE) based on the first priority value being lower than the second priority value, or performs an SR transmission to the network node (e.g., a base station, gNB, etc.) based on the second priority value being lower than the first priority value.

[0354] In some instances, the first UE determines a first priority value based on the configuration (e.g., RRC configuration) and / or the type of SL transmission. The type may indicate whether the SL transmission is an SL data transmission (e.g., on SL-SCH and / or PSSCH), an SL-PRS transmission using SL-PRS resources from a shared SL-PRS resource pool, an SL-PRS transmission using SL-PRS resources from a dedicated SL-PRS resource pool, an SL-CSI transmission, or other types of SL transmission.

[0355] In one embodiment, SL transmissions are associated with SL resources that overlap with Physical Uplink Control Channel (PUCCH) resources associated with SR transmissions. A first UE performs an SL transmission to a second UE on the SL resources (based on a first priority value being lower than a second priority value) or an SR transmission to a network node on the PUCCH resources (based on a second priority value being lower than a first priority value).

[0356] In one embodiment, the first UE is configured to perform SL transmission and SR transmission at non-overlapping times. For example, the configuration and / or capabilities of the first UE allow it to perform SL transmission and SR transmission at non-overlapping times.

[0357] In one embodiment, SL transmission includes SL data transmission.

[0358] In one embodiment, an SL transport includes an SL-PRS transport associated with a dedicated SL-PRS resource pool. For example, the SL resource associated with the SL transport may be an SL-PRS resource of a dedicated SL-PRS resource pool.

[0359] In one embodiment, the one or more pending SL-PRS transmissions include a plurality of pending SL-PRS transmissions, and the one or more priority values ​​include a plurality of priority values ​​associated with the plurality of pending SL-PRS transmissions. In some instances, an SL-PRS Resource Request MAC CE is generated to indicate the plurality of pending SL-PRS transmissions and the plurality of priority values. In some instances, the SL-PRS Resource Request MAC CE includes a plurality of information sets associated with the plurality of pending SL-PRS transmissions. In some instances, each of the plurality of information sets indicates the priority value (and / or other information) of the SL-PRS transmission among the plurality of pending SL-PRS transmissions.

[0360] In one embodiment, the SL-PRS Resource Request MAC CE indicates information associated with the one or more pending SL-PRS transmissions. For example, the SL-PRS Resource Request MAC CE can be used to provide a network node with information associated with the one or more pending SL-PRS transmissions (associated with one or more peer UEs).

[0361] In some instances, a first UE may identify a first pending SL-PRS transmission among the one or more pending SL-PRS transmissions. In some instances, the first pending SL-PRS transmission may be triggered by the first UE (e.g., by a higher layer and / or upper layer of the first UE). An SL-PRS resource request may be triggered (e.g., by the first UE) in response to determining that the first pending SL-PRS transmission is pending (e.g., pending for transmission to one or more UEs). In some instances, the first UE may trigger an SR transmission in response to triggering an SL-PRS resource request and / or determining that the first pending SL-PRS transmission is pending. In some instances, after identifying the first pending SL-PRS transmission and / or triggering an SL-PRS resource request, the first UE may identify a second pending SL-PRS transmission among the one or more SL-PRS transmissions. In some instances, the second pending SL-PRS transmission may be triggered by the first UE (e.g., by a higher layer and / or upper layer of the first UE). An SL-PRS resource request can be triggered (e.g., by a first UE) in response to determining that a first pending SL-PRS transmission is pending (e.g., pending for transmission to one or more UEs). The first UE can generate an SL-PRS resource request MAC CE to indicate: information associated with the first pending SL-PRS transmission to be reported to the network node (e.g., the information may include the priority value of the first pending SL-PRS transmission and / or one or more destination UEs of the first pending SL-PRS transmission), information associated with a second pending SL-PRS transmission to be reported to the network node (e.g., the information may include the priority value of the second pending SL-PRS transmission and / or one or more destination UEs of the second pending SL-PRS transmission), and / or information associated with one or more other pending SL-PRS transmissions to be reported to the network node.

[0362] Now for reference Figure 3 and Figure 4In an exemplary embodiment of the first UE, the apparatus 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 such that the first UE, which cannot simultaneously perform an SR transmission triggered by an SL-PRS resource request associated with an SL transmission of a first priority value, can: (i) determine a second priority value associated with the SR transmission based on the lowest priority value among the priority values ​​indicated by the SL-PRS resource request MAC CE for one or more pending SL-PRS transmissions; and (ii) perform one of the following: performing an SL transmission to a second UE (e.g., a peer UE) based on the first priority value being lower than the second priority value, or performing an SR transmission to a network node (e.g., a base station, gNB, etc.) based on the second priority value being lower than the first priority value. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the aforementioned actions and steps and / or other actions and steps described herein.

[0363] A communication device (e.g., UE, base station, network node, etc.) may be provided, wherein the communication device may include control circuitry, a processor mounted in the control circuitry, and / or a memory mounted in the control circuitry and coupled to the processor. The processor may be configured to execute program code stored in the memory to perform... Figures 8 to 10 The methods and steps described herein. Furthermore, the processor can execute program code to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0364] A computer-readable medium may be provided. The computer-readable medium may be a non-transitory computer-readable medium. The computer-readable medium may include flash memory devices, hard disk drives, disks (e.g., at least one of magnetic disks and / or optical disks, such as digital versatile optical disks (DVDs), compact optical disks (CDs), etc.), and / or memory semiconductors, such as at least one of static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), etc. The computer-readable medium may include processor-executable instructions that, when executed, cause execution... Figures 8 to 10 The steps of one, some and / or all of the methods shown herein, and / or one, some and / or all of the actions and steps described herein and / or other actions and steps.

[0365] It is understood that applying one or more of the techniques proposed herein may yield one or more benefits, including but not limited to: increased communication efficiency between devices, more accurate prioritization of transmissions (e.g., SL-PRS transmissions and / or SR transmissions) to meet location service requirements at increased and / or more uniform rates, more accurate prioritization of SRs associated with and / or triggered by multiple SL-PRSs, improved transmission scheduling decisions in response to potential conflict identifiers, and so on.

[0366] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any particular structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in different ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented by using other structures, functions, or structures and functions other than or different from one or more aspects set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on the pulse repetition frequency. In some aspects, a parallel channel can be established based on the pulse position or offset. In some aspects, a parallel channel can be established based on a time-hopping sequence. In some aspects, a parallel channel can be established based on the pulse repetition frequency, the pulse position or offset, and the time-hopping sequence.

[0367] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0368] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or a combination of both, which may be designed using source coding or some other technique) and have instructions in various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination of both. To clearly illustrate the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as a departure from the scope of this disclosure.

[0369] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0370] It should be understood that any particular order or hierarchy of steps in any disclosed process is an instance of a sample method. Based on design preferences, it should be understood that a particular order or hierarchy of steps in the process may be rearranged while remaining within the scope of this disclosure. The appended method claims present the elements of the individual steps in a sample order and are not intended to be limited to any particular order or hierarchy presented.

[0371] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and associated data) and other data can reside in data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. The sample storage medium can be coupled to a machine such as a computer / processor (for convenience, this machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. The sample storage medium can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside as discrete components in a user equipment. Alternatively and / or additionally, in some aspects, any suitable computer program product may include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some respects, computer program products may include packaging materials.

[0372] Although the disclosed subject matter has been described in conjunction with various aspects, it should be understood that the disclosed subject matter is subject to further modifications. This application is intended to cover any changes, uses, or adaptations of the disclosed subject matter that generally follow the principles of the disclosed subject matter and include deviations from the scope of practice known and customary in the art to which this disclosure pertains.

Claims

1. A method for a first user equipment, wherein the first user equipment cannot simultaneously execute a scheduling request transmission triggered by a sidelink positioning reference signal resource request with a sidelink transmission associated with a first priority value, characterized in that, The method includes: A second priority value associated with the scheduling request transmission is determined based on the lowest priority value among the priority values ​​indicated by the sidelink positioning reference signal resource request media access control control element for one or more pending sidelink positioning reference signal transmissions; and One of the following: The sidelink transmission to the second user equipment is performed based on the fact that the first priority value is lower than the second priority value; or The scheduling request is transmitted to the network node based on the fact that the second priority value is lower than the first priority value.

2. The method according to claim 1, characterized in that: The sidelink transmission is associated with sidelink resources, which overlap with physical uplink control channel resources associated with the scheduling request transmission; and One of the following: The sidelink transmission to the second user equipment includes performing the sidelink transmission on the sidelink resources; or The execution of the scheduling request transmission to the network node includes performing the scheduling request transmission on the physical uplink control channel resources.

3. The method according to claim 1, characterized in that: The sidelink transmission includes sidelink data transmission.

4. The method according to claim 1, characterized in that: The sidelink transmission includes the transmission of sidelink positioning reference signals associated with a dedicated sidelink positioning reference signal resource pool.

5. The method according to claim 1, characterized in that: The transmission of one or more pending sidelink positioning reference signals includes the transmission of multiple pending sidelink positioning reference signals. The priority values ​​include multiple priority values ​​associated with the transmission of the plurality of pending side link positioning reference signals; and The method includes generating a sidelink positioning reference signal resource request media access control element that indicates the transmission of the plurality of pending sidelink positioning reference signals and the plurality of priority values.

6. A non-transitory machine-readable medium for handling scheduling requests triggered by sidelink positioning reference signal resource requests, having stored thereon processor-executable instructions that, when executed by a first user equipment, enable operations to be performed, characterized in that, The operation includes: Determine the first priority value associated with the sidelink transmission to the second user equipment; A second priority value is determined based on one or more priority values ​​associated with one or more sidelink location reference signal transmissions, which are associated with the sidelink location reference signal resource request on which the scheduling request transmission is triggered. Based on the first priority value and the second priority value, select one of the sidelink transmission or the scheduling request transmission from a plurality of transmissions including the sidelink transmission and the scheduling request transmission; and Perform the selected transmission.

7. The non-transitory machine-readable medium according to claim 6, characterized in that: The sidelink transmission is associated with sidelink resources, which overlap with the physical uplink control channel resources associated with the scheduling request transmission.

8. The non-transitory machine-readable medium according to claim 7, characterized in that, Performing the selected transmission includes: In response to selecting the sidelink transmission from the plurality of transmissions, the sidelink transmission is performed on the sidelink resources; or The scheduling request transmission is performed on the physical uplink control channel resources in response to selecting the scheduling request transmission from the plurality of transmissions.

9. The non-transitory machine-readable medium according to claim 6, characterized in that, Determining the second priority value associated with the transmission of the scheduling request includes: Analyze the one or more priority values ​​to identify a third priority value that indicates the highest priority among the one or more priorities indicated by the one or more priority values; and The second priority value is determined based on the third priority value.

10. The non-transitory machine-readable medium according to claim 6, characterized in that: The first user equipment is configured to perform the sidelink transmission and the scheduling request transmission at non-overlapping times.

11. The non-transitory machine-readable medium according to claim 6, characterized in that: At least one of the configurations or capabilities of the first user equipment does not allow the first user equipment to perform the sidelink transmission and the scheduling request transmission simultaneously.

12. The non-transitory machine-readable medium according to claim 6, characterized in that: The sidelink transmission includes sidelink data transmission.

13. The non-transitory machine-readable medium according to claim 6, characterized in that: The sidelink transmission includes the transmission of sidelink positioning reference signals associated with a dedicated sidelink positioning reference signal resource pool.

14. The non-transitory machine-readable medium according to claim 6, characterized in that, Selecting either the sidelink transmission or the scheduling request transmission includes: The scheduling request transmission is selected based on a second priority value associated with the transmission indicating a higher priority than the first priority value associated with the sidelink transmission.

15. The non-transitory machine-readable medium according to claim 6, characterized in that, Selecting either the sidelink transmission or the scheduling request transmission includes: The sidelink transmission is selected based on a first priority value associated with the sidelink transmission indicating a higher priority than a second priority value associated with the scheduling request transmission.

16. The non-transitory machine-readable medium according to claim 6, characterized in that: The transmission of one or more sidelink positioning reference signals includes multiple pending sidelink positioning reference signal transmissions. The one or more priority values ​​include multiple priority values ​​associated with the transmission of the plurality of pending sidelink positioning reference signals; and The operation includes generating a sidelink positioning reference signal resource request media access control control element that indicates the transmission of the plurality of pending sidelink positioning reference signals and the plurality of priority values.

17. The non-transitory machine-readable medium according to claim 6, characterized in that, The operation includes: Generate a sidelink positioning reference signal resource request media access control control element that indicates the one or more priority values.

18. The non-transitory machine-readable medium according to claim 6, characterized in that, The operation includes: Generate a sidelink positioning reference signal resource request media access control control element that indicates information associated with the transmission of the one or more sidelink positioning reference signals.

19. A first user equipment for processing a scheduling request triggered by a sidelink positioning reference signal resource request, characterized in that, The first user equipment includes: Control circuit; The processor, which is installed in the control circuit; and A memory, mounted in the control circuitry and operatively coupled to the processor, wherein the processor is configured to execute program code stored in the memory to perform operations, including: Determine a first priority value associated with the transmission via the first side link to the second user equipment; A second priority value is determined based on one or more priority values ​​associated with one or more second sidelink transmissions, which are associated with the sidelink resource request on which the scheduling request transmission is triggered. Based on the first priority value and the second priority value, select one of the first sidelink transmission or the scheduling request transmission from a plurality of transmissions including the first sidelink transmission and the scheduling request transmission; and Perform the selected transmission.

20. The first user equipment according to claim 19, characterized in that, Determining the second priority value associated with the transmission of the scheduling request includes: Analyze the one or more priority values ​​to identify a third priority value that indicates the highest priority among the one or more priorities indicated by the one or more priority values; and The second priority value is determined based on the third priority value.

Images