Method and apparatus for resource determination of sidelink reference signal

Abstract

The present disclosure provides a method, system and device for resource determination for sidelink reference signals in a wireless communication system, where the method of a first device comprises: receiving from a network a configuration of a first sidelink resource pool for sidelink data transmission and / or sidelink reference signals, determining a first sidelink reference signal resource identifier, the first sidelink reference signal transmission and the first sidelink data transmission are multiplexed in a first time slot, a second sidelink reference signal resource identification is determined, and the second sidelink reference signal transmission and the second sidelink data transmission are multiplexed in a second time slot.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 598,531, filed on November 13, 2023, 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 resource determination for sidelink reference signals in wireless communication systems. Background Art

[0004] With the rapid growth of the demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) packets. Such IP packet communications can provide IP-bearing voice, multimedia, multicast and on-demand communication services to users of mobile communication devices.

[0005] An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the above-mentioned IP-borne voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Therefore, changes to the current body of 3GPP standards are currently being submitted and considered to enable the 3GPP standards to evolve and be completed. Summary of the invention

[0006] A method, system and device for resource determination of a sidelink reference signal in a wireless communication system are provided to avoid unnecessary restrictions and reduce delays regarding sidelink positioning reference signal (SL PRS) multiplexing, SL PRS resource determination and SL PRS request.

[0007] In various embodiments, a method of a first device includes: receiving a configuration of a first side link resource pool for side link data transmission and / or side link reference signal from a network, determining a first side link reference signal resource identity (Identity, ID), multiplexing the first side link reference signal transmission and the first side link data transmission in a first time slot, wherein the first side link reference signal transmission is associated with the first side link reference signal resource ID, determining a second side link reference signal resource ID, and multiplexing the second side link reference signal transmission and the second side link data transmission in a second time slot, wherein the second side link reference signal transmission is associated with the second side link reference signal resource ID, and the first side link data transmission and the second side link data transmission are used to transmit the same side link data packet.

[0008] In various embodiments, a method of a first device includes: receiving a configuration of a first sidelink resource pool for sidelink data transmission and / or a sidelink reference signal from a network, triggering the first sidelink reference signal for transmission based on signaling sent from a second device or based on an upper layer of the first device, setting a first sidelink reference signal resource ID associated with a first transmission of the first sidelink reference signal for an initial transmission of a carrying sidelink data packet, performing an initial transmission multiplexed with the first transmission of the first sidelink reference signal to a second device, wherein the first transmission of the first sidelink reference signal is associated with the first sidelink reference signal resource ID, setting a second sidelink reference signal resource ID associated with a second transmission of the first sidelink reference signal for a retransmission of the carrying sidelink data packet, and performing a retransmission multiplexed with the second transmission of the first sidelink reference signal to the second device, wherein the second transmission of the first sidelink reference signal is associated with the second sidelink reference signal resource ID, and wherein the first sidelink reference signal resource ID and the second sidelink reference signal resource ID are determined by the upper layer of the first device.

[0009] In various embodiments, a method of a first device includes: receiving a configuration of a first sidelink resource pool for sidelink data transmission and / or a sidelink reference signal from a network, triggering a sidelink reference signal transmission based on signaling sent from a second device or based on an upper layer of the first device, allowing the upper layer of the first device to determine two sidelink reference signal resource IDs for a first transmission and a second transmission, respectively, wherein the first transmission and the second transmission carry the same sidelink data packet, setting a first sidelink reference signal resource ID associated with a first sidelink reference signal for the first transmission, performing a first transmission multiplexed with the first sidelink reference signal to a second device, setting a second sidelink reference signal resource ID associated with a second sidelink reference signal for the second transmission, and performing a second transmission multiplexed with the second sidelink reference signal to the second device. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A diagram of a wireless communication system according to an embodiment of the present invention is shown.

[0011] Figure 2 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 embodiment of the present invention.

[0012] Figure 3 is a functional block diagram of a communication system according to an embodiment of the present invention.

[0013] Figure 4 According to an embodiment of the present invention Figure 3 Functional block diagram of the program code.

[0014] Figure 5 is an example diagram showing multiple PSSCH transmissions for the same sidelink data packet according to an embodiment of the present invention: PSSCH 1 is an initial / new PSSCH transmission, and PSSCH 2-6 are PSSCH retransmissions.

[0015] Figure 6 It is an example diagram according to an embodiment of the present invention, showing that in time slot A without PSFCH resources, there can be at most 4 symbols for SL PRS transmission (M≤4); and in time slot B with PSFCH resources, there can be at most 3 symbols for SL PRS transmission (M≤3).

[0016] Figure 7 It is a flowchart of a method of a first device according to an embodiment of the present invention, the method comprising: receiving a configuration of a first side link resource pool for side link data transmission and / or a side link reference signal, performing a new / initial side link data transmission for transmitting a side link data packet, and performing a first side link data retransmission for transmitting the same side link data packet while multiplexing a side link reference signal transmission in a first time slot.

[0017] Figure 8 It is a flowchart of a method of a first device according to an embodiment of the present invention, the method comprising: receiving a configuration of a first side link resource pool for side link data transmission and / or side link reference signal from a network, determining a first side link reference signal resource ID, multiplexing the first side link reference signal transmission and the first side link data transmission in a first time slot, determining a second side link reference signal resource ID, and multiplexing the second side link reference signal transmission and the second side link data transmission in a second time slot.

[0018] Fig. 9It is a flowchart of a method of a first device according to an embodiment of the present invention, the method comprising: receiving a configuration of a first side link resource pool for side link data transmission and / or a side link reference signal from a network, triggering a first side link reference signal for transmission based on signaling sent from a second device or based on an upper layer of the first device, setting a first side link reference signal resource ID associated with a first transmission of the first side link reference signal for an initial transmission of a carrying side link data packet, performing an initial transmission multiplexed with the first transmission of the first side link reference signal to a second device, setting a second side link reference signal resource ID associated with a second transmission of the first side link reference signal for a retransmission of a carrying side link data packet, and performing a retransmission multiplexed with the second transmission of the first side link reference signal to the second device.

[0019] Fig.10 It is a flowchart of a method of a first device according to an embodiment of the present invention, the method comprising: receiving a configuration of a first sidelink resource pool for sidelink data transmission and / or a sidelink reference signal from a network, triggering sidelink reference signal transmission based on signaling sent from a second device or based on an upper layer of the first device, allowing the upper layer of the first device to determine two sidelink reference signal resource IDs for the first transmission and the second transmission, respectively, setting a first sidelink reference signal resource ID associated with the first sidelink reference signal for the first transmission, performing a first transmission multiplexed with the first sidelink reference signal to the second device, setting a second sidelink reference signal resource ID associated with the second sidelink reference signal for the second transmission, and performing a second transmission multiplexed with the second sidelink reference signal to the second device. DETAILED DESCRIPTION

[0020] The present invention described herein may be applied to or implemented in the exemplary wireless communication systems and devices described below. In addition, the present invention is mainly described in the context of the 3GPP architecture reference model. However, it should be understood that, using the disclosed information, those skilled in the art can easily adapt to use and implement various aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

[0021] The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications, 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) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0022] Specifically, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as standards provided by an association named "3rd Generation Partnership Project" referred to herein as 3GPP, including: [1] 3GPP TS 38.213 V18.0.0 (2023-09) 3GPP; TSG RAN; NR; Physical layer procedures for control (Release 18); [2] 3GPP TS 38.214 V18.0.0 (2023-09) 3GPP; TSG RAN; NR; Physical layer procedures for data (Release 18); [3] 3GPP TS 38.212 V18.0.0 (2023-09) 3GPP; TSG RAN; NR; Multiplexing and channel coding (Release 18); [4] 3GPP TS 38.211 V18.0.0 (2023-09) 3GPP; TSG RAN; NR; Physical Channels and Modulation (Release 18); [5] R2-2312264, "Draft running MAC CR for the introduction of Sidelink Positioning", Huawei HiSilicon; [6] RAN1 Chairman's Note of 3GPP TSG RAN WG1#112bis; [7] RAN1 Chairman's Note of 3GPP TSG RAN WG1#113; [8] RAN1 Chairman's Note of 3GPP TSG RAN WG1#114; and [9] RAN1 Chairman's Note of 3GPP TSG RAN WG1#114bis. The standards and documents listed above are hereby expressly and entirely incorporated herein by reference in their entirety.

[0023] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is shown. An access network (AN) 100 includes multiple antenna groups, one antenna group includes 104 and 106, another antenna group includes 108 and 110, and another antenna group includes 112 and 114. Figure 11, each antenna group is shown with only two antennas, however, each antenna group may utilize more or fewer antennas. Access terminal (AT) 116 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 AT 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 an FDD system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than the frequency used by reverse link 118.

[0024] Each antenna group and / or the area in which the antenna group is designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups are each designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0025] In communicating on forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Furthermore, an access network transmitting to access terminals randomly dispersed throughout its coverage area using beamforming generally causes less interference to access terminals in neighboring cells than an access network transmitting to all of its access terminals via a single antenna.

[0026] AN may be a fixed station or base station for communicating with a terminal, and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or some other term. AT may also be referred to as user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other term.

[0027] Figure 2 2 is a simplified block diagram of an embodiment of 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)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0028] In one embodiment, each data stream is transmitted through a corresponding transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0029] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed by processor 230. Memory 232 is coupled to processor 230.

[0030] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). T The modulation symbol streams are provided to N T transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0031] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. T The antennas 224a to 224t transmit N signals from the transmitters 222a to 222t. T a modulated signal.

[0032] At the receiver system 250, N R The transmitted modulated signals are received by each antenna 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to obtain samples, and further processes the samples to obtain a corresponding “received” symbol stream.

[0033] The RX data processor 260 then extracts the N R The receiver 254 receives N R received symbol streams and processing the received symbol streams to provide N TThe RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0034] Processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0035] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238, which also receives traffic data for a number of data streams from the data source 236, modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

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

[0037] Memory 232 may be used to temporarily store some buffer / calculated data from 240 or 242 through processor 230, store some buffer data from 212, or store some specific program codes. Also, memory 272 may be used to temporarily store some buffer / calculated data from 260 through processor 270, store some buffer data from 236, or store some specific program codes.

[0038] Steering Figure 3 , which shows an alternative simplified functional block diagram of a communication device according to one embodiment of the present invention. Figure 3 As shown in FIG. , the communication device 300 in the wireless communication system can be used to implement Figure 1UE (or AT) 116 and 122 in, and the wireless communication system is preferably 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, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive a signal input by a user through an input device 302 such as a keyboard or a keypad, and can output images and sounds through an output device 304 such as a monitor or a speaker. The transceiver 314 is used to receive and transmit wireless signals, deliver the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306.

[0039] Figure 4 According to an embodiment of the present invention Figure 3 4. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connectivity.

[0040] For LTE, LTE-A or NR systems, the layer 2 portion 404 may include a radio link control (RLC) layer and a medium access control (MAC) layer. The layer 3 portion 402 may include a radio resource control (RRC) layer.

[0041] Any two or more of the following paragraphs, (sub) bullet points, key points, actions or technical solutions described in each invention may be logically, reasonably and appropriately combined to form a specific method.

[0042] Any sentence, paragraph, (sub) bullet, key point, action or claim described in each of the following invention paragraphs or sections can be implemented independently and individually to form a specific method or device. The following disclosure of the present invention, such as "based on", "more specifically", "example", etc., is only a possible embodiment that does not limit a specific method or device.

[0043] In TS 38.213 ([1] 3GPP TS 38.213 V18.0.0 (2023-09)), SL-related procedures for control are specified.

[0044] ************************* Quote [1] Start **********************************

[0045] 16 UE procedures for sidelink

[0046] The BWP for SL transmission (SL BWP) is provided to the UE by SL-BWP-Config or SL-BWP-ConfigCommon, which has basic parameters and resource grid determined as described in [4, TS 38.211]. For the resource pool within the SL BWP, a number of subchannels are provided to the UE by sl-NumSubchannel, where each subchannel contains a number of contiguous RBs provided by sl-SubchannelSize. The first RB of the first subchannel in the SL BWP is indicated by sl-StartRB-Subchannel. The available time slots for the resource pool are provided by sl-TimeResource and occur with a periodicity of 10240ms. For available time slots without S-SS / PSBCH blocks, SL transmission may start from the first symbol indicated by sl-StartSymbol and within a number of consecutive symbols indicated by sl-LengthSymbols. For available time slots with S-SS / PSBCH blocks, the first symbol and a number of consecutive symbols are predetermined.

[0047] …

[0048] 16.4 UE Procedure for Transmitting PSCCH

[0049] A number of symbols in the resource pool may be provided to the UE by sl-TimeResourcePSCCH, starting from the second symbol in the slot available for SL transmission, and a number of PRBs in the resource pool may be provided to the UE by sl-FreqResourcePSCCH, starting from the lowest PRB index of the lowest subchannel index in the set of RBs with the lowest index of the associated PSSCH (if applicable), for PSCCH transmission using SCI format 1-A. …

[0050] 16.4A UE Procedure for Transmitting PSCCH in Dedicated Resource Pool for SL PRS

[0051] For the resource pool dedicated to SL PRS transmission, several symbols in the resource pool can be provided to the UE by sl-TimeResourcePSCCH, starting from the second symbol in the time slot that can be used for SL transmission, and several PRBs in the resource pool can be provided to the UE by sl-FreqResourcePSCCH for PSCCH transmission utilizing SCI format 1-B.

[0052] Set so that the UE uses SL PRS resource allocation scheme 2 [6, TS 38.214] to transmit PSCCH using SCI format 1-B

[0053] -…

[0054] Set so that the UE uses SL PRS resource allocation scheme 1 [6, TS 38.214] to transmit PSCCH using SCI format 1-B

[0055] -…

[0056] **************************End of Quote [1]******************************

[0057] In TS 38.214 ([2] 3GPP TS 38.214 V18.0.0 (2023-09)), SL-related procedures for data are specified.

[0058] *************************** Quote [2] starts ******************************

[0059] 8 Physical side link shared channel related procedures

[0060] The UE may be configured by a higher layer to have one or more sidelink resource pools. The sidelink resource pool may be used for transmission of PSSCH as described in clause 8.1 and / or transmission of SL PRS as described in clause 8.2.4, or for reception of PSSCH as described in clause 8.3 and / or reception of SL PRS as described in clause 8.4.4, and may be associated with sidelink resource allocation mode 1 or sidelink resource allocation mode 2.

[0061] The side link resource pool that can be used for transmission of both SL PRS and PSSCH will be referred to as a shared resource pool.

[0062] The side link resource pool that can be used for transmission of SL PRS but not for transmission of PSSCH will be referred to as a dedicated SLPRS resource pool.

[0063] In the frequency domain,

[0064] - If the higher layer parameter transmissionStructureForPSCCHandPSSCH is not provided or is set to 'contiguousRB', the sidelink resource pool consists of sl-NumSubchannel contiguous subchannels. A subchannel consists of sl-SubchannelSize contiguous PRBs, where sl-NumSubchannel and sl-SubchannelSize are higher layer parameters.

[0065] -…

[0066] The set of time slots that can belong to the sidelink resource pool is represented as in

[0067] -

[0068] - the slot index is relative to slot#0 of the radio frame corresponding to SFN 0 or DFN 0 of the serving cell,

[0069] - The set contains all time slots except the following time slots,

[0070] -N S-SSB time slots in which an S-SS / PSBCH block (S-SSB) or an additional transmission opportunity for S-SSB is configured,

[0071] -N nonSL time slots, in each of which, according to the higher layer parameters tdd-UL-DL-ConfigurationCommon (if provided) or sl-TDD-Configuration (if provided) of the serving cell or sl-TDD-Config (if provided) of the received PSBCH, at least one of the Y, (Y+1), ..., (Y+X-1)th OFDM symbols is not semi-statically configured as UL, where Y and X are set by the higher layer parameters sl-StartSymbol and sl-LengthSymbols, respectively.

[0072] - Reserved time slots, which are determined by the following steps.

[0073] 1) Exclude N from the set of all time slots S-SSB time slots and N nonSL The remaining time slots are arranged in increasing order of time slot index. express.

[0074] 2) If Here m=0,1,…,N 预留 -1 and N 预留 =(10240×2μ -N S-SSB -N nonSL )mod L 位图 , where L 位图 represents the length of the bitmap configured by the higher layer, then the time slot l r (0≤r<10240×2 μ -N S-SSB -N nonSL ) belongs to the reserved time slot.

[0075] - The slots in a set are arranged in increasing order of slot index.

[0076] The UE determines the set of logical time slots assigned to the sidelink resource pool as follows:

[0077] -Use the bitmap associated with the resource pool The length of the bitmap is L 位图 Configured by higher layers.

[0078] - If b k′ = 1, where k′ = k mod L 位图 , then the time slot Belongs to the collection.

[0079] - The slots in the set are re-indexed so that the remaining slots The subscript i is continuous {0,1,…,T′ max -1}, where T′ max is the number of time slots remaining in the set.

[0080] The UE determines the set of resource blocks assigned to the sidelink resource pool as follows:

[0081] -The resource block pool consists of N PRB PRBs.

[0082] - If the higher layer parameter transmissionStructureForPSCCHandPSSCH is not provided, or is set to 'contiguousRB', then subchannel m is composed of n subCHsize The number of physical resource blocks is n. PRB =n subCHRBstart +m·n subCHsize +j, where j = 0, 1, ..., n subCHsize -1, where n subCHRBstart 、n subCHsizeand numSubchannel are given by the higher layer parameters sl-StartRB-Subchannel, sl-SubchannelSize and sl-NumSubchannel respectively.

[0083] -…

[0084] 8.1 UE procedures for transmitting the physical sidelink shared channel

[0085] Each PSSCH transmission is associated with a PSCCH transmission.

[0086] The PSCCH transmission carries the level 1 SCI associated with the PSSCH transmission; the level 2 associated SCI is carried within the resources of the PSSCH.

[0087] If the UE transmits SCI format 1-A on the PSCCH according to the PSCCH resource configuration in slot n and PSCCH resource m, then for the associated PSSCH transmission in the same slot

[0088] - One transport block is transmitted using at most two layers;

[0089] -…

[0090] The UE shall set the content of SCI format 2-A as follows:

[0091] - The UE shall set the value of the 'HARQ Process Number' field as instructed by higher layers.

[0092] - The UE shall set the value of the 'NDI' field as instructed by higher layers.

[0093] - The UE shall set the value of the 'Redundancy Version' field as indicated by higher layers.

[0094] - The UE shall set the value of the 'Source ID' field as instructed by higher layers.

[0095] - The UE shall set the value of the 'Destination ID' field as instructed by higher layers.

[0096] - The UE shall set the value of the 'HARQ Feedback Enable / Disable Indicator' field as indicated by higher layers.

[0097] - The UE shall set the value of the 'Broadcast Type Indicator' field as indicated by higher layers.

[0098] - The UE shall set the value of the 'CSI Request' field as instructed by higher layers.

[0099] [- The UE shall set the value of the 'CAPC' field as indicated by higher layers.

[0100] - The UE shall set the value of the 'COT Shared Broadcast Type' field as indicated by higher layers.

[0101] - The UE shall set the value of the 'COT Shared Additional ID' field as instructed by higher layers.

[0102] - The UE shall set the value of the 'Remaining COT Duration' field as indicated by higher layers. ]

[0103] The UE shall set the content of SCI format 2-B as follows:

[0104] - The UE shall set the value of the 'HARQ Process Number' field as instructed by higher layers.

[0105] - The UE shall set the value of the 'NDI' field as instructed by higher layers.

[0106] - The UE shall set the value of the 'Redundancy Version' field as indicated by higher layers.

[0107] - The UE shall set the value of the 'Source ID' field as instructed by higher layers.

[0108] - The UE shall set the value of the 'Destination ID' field as instructed by higher layers.

[0109] - The UE shall set the value of the 'HARQ Feedback Enable / Disable Indicator' field as indicated by higher layers.

[0110] - The UE shall set the value of the 'Zone ID' field as indicated by higher layers.

[0111] - The UE shall set the 'Communication Range Requirement' field as instructed by higher layers.

[0112] [- The UE shall set the value of the 'CAPC' field as indicated by higher layers.

[0113] - The UE shall set the value of the 'COT Shared Broadcast Type' field as indicated by higher layers

[0114] - The UE shall set the value of the 'COT Shared Additional ID' field as instructed by higher layers.

[0115] - The UE shall set the value of the 'Remaining COT Duration' field as indicated by higher layers. ]

[0116] The UE shall set the content of SCI format 2-C as follows:

[0117] - The UE shall set the value of the 'HARQ Process Number' field as instructed by higher layers.

[0118] - The UE shall set the value of the 'NDI' field as instructed by higher layers.

[0119] - The UE shall set the value of the 'Redundancy Version' field as indicated by higher layers.

[0120] - The UE shall set the value of the 'Source ID' field as instructed by higher layers.

[0121] - The UE shall set the value of the 'Destination ID' field as instructed by higher layers.

[0122] - The UE shall set the value of the 'HARQ Feedback Enable / Disable Indicator' field as indicated by higher layers.

[0123] - The UE shall set the value of the 'CSI Request' field as instructed by higher layers.

[0124] - The UE shall set the value of the 'Offer / Request Indicator' field as instructed by higher layers.

[0125] [- The UE shall set the value of the 'CAPC' field as indicated by higher layers.

[0126] - The UE shall set the value of the 'COT Shared Broadcast Type' field as indicated by higher layers

[0127] - The UE shall set the value of the 'COT Shared Additional ID' field as instructed by higher layers.

[0128] - The UE shall set the value of the 'Remaining COT Duration' field as indicated by higher layers. ]

[0129] - If the 'Offer / Request Indicator' indicates that SCI format 2-C is used to deliver an explicit request for inter-UE coordination information:

[0130] - The UE shall set the value of the 'Priority' field as indicated by higher layers.

[0131] - The UE shall set the value of the 'Number of subchannels' field as indicated by higher layers.

[0132] - The UE shall set the value of the 'Resource Reservation Period' field as instructed by higher layers.

[0133] - The UE shall set the value of the 'Resource selection window position' field as instructed by higher layers.

[0134] - If the higher layer parameter sl-DetermineResourceType is configured to 'UE-B's request', the UE shall set the value of the 'Resource Set Type' field as indicated by higher layers; otherwise this field shall be omitted.

[0135] - If the 'Offer / Request Indicator' indicates that SCI format 2-C is used for delivering inter-UE coordination information:

[0136] - The UE shall set the value of the 'Resource Set Type' field as indicated by higher layers.

[0137] - The UE shall set the value of the 'Resource Combination' field (clause 8.1.5A) as instructed by higher layers.

[0138] - The UE shall set the value of 'Lowest Subchannel Index' as indicated by higher layers

[0139] - The UE shall set the value of 'first resource location' as indicated by higher layers

[0140] - The UE shall set the value of 'reference slot position' as indicated by higher layers

[0141] The UE shall set the content of SCI format 2-D as follows:

[0142] - The UE shall set the value of the '[SL PRS Resource ID]' field as instructed by higher layers.

[0143] - The UE shall set the value of the '[SL PRS Request]' field as instructed by higher layers.

[0144] - The UE shall set the value of the '[Embedded SCI Format]' field as indicated by higher layers.

[0145] - If 'Embedded SCI format' indicates that SCI format 2-A is embedded within this SCI format 2-D, the UE shall include the fields of SCI format 2-A set as specified above in the '[Embedded SCI format payload]' field and add the necessary padding so that the size of SCI format 2-D is the same as in the case of embedded SCI format 2-B.

[0146] - If 'Embedded SCI format' indicates that SCI format 2-B is embedded within this SCI format 2-D, the UE shall include the fields of SCI format 2-B set as specified above in the '[Embedded SCI format payload]' field.

[0147] 8.1.1 Transmission scheme

[0148] Only one transmission scheme is defined for PSSCH and is used for all PSSCH transmissions.

[0149] PSSCH transmission is performed using at most two antenna ports, where antenna ports 1000-1001 are defined in clause 8.2.4 of [4, TS38.211].

[0150] 8.1.2 Resource Allocation

[0151] In sidelink resource allocation mode 1:

[0152] - For PSSCH and PSCCH transmissions, dynamic grants, configured grant type 1 and configured grant type 2 are supported. Configured grant type 2 sidelink transmissions are semi-statically scheduled by SL grants according to clause 10.2A of [6, TS 38.213] in the valid activation DCI.

[0153] 8.1.2.1 Resource Allocation in the Time Domain

[0154] The UE shall transmit the PSSCH in the same time slot as the associated PSCCH.

[0155] The smallest resource allocation unit in the time domain is a time slot.

[0156] The UE shall transmit PSSCH in consecutive symbols within a slot, with the following restrictions:

[0157] - The UE shall not transmit PSSCH in symbols not configured for the sidelink. The symbols used for the sidelink are configured according to the higher layer parameters sl-StartSymbol and sl-LengthSymbols, where sl-StartSymbol is the symbol index of the first symbol of sl-LengthSymbols consecutive symbols configured for the sidelink.

[0158] - Within a time slot, PSSCH resource allocation starts at symbol sl-StartSymbol+1, except when startingSymbolFirst and startingSymbolSecond are provided for SL-BWP. If startingSymbolFirst and startingSymbolSecond are provided for SL-BWP, then for time slots without PSFCH symbols, there are 2 candidate starting symbols for PSSCH transmission. PSSCH resource allocation starts at the next symbol after each candidate starting symbol. In a time slot, the UE may use the second candidate starting symbol provided by startingSymbolSecond only if the UE fails to access the channel before the first starting symbol provided by startingSymbolFirst. The UE shall not use the second starting symbol in a time slot with PSFCH symbols.

[0159] - If PSFCH is configured in this slot, the UE shall not transmit PSSCH in symbols configured for use by PSFCH.

[0160] - The UE shall not transmit PSSCH in the last symbol configured for sidelink.

[0161] - If PSFCH is configured in this time slot, the UE shall not transmit PSSCH in the symbol immediately preceding the symbol configured for use by PSFCH.

[0162] -…

[0163] 8.1.2.2 Resource Allocation in the Frequency Domain

[0164] The resource allocation unit in the frequency domain is a subchannel.

[0165] The subchannel assignment for the sidelink transmission is determined using the "Frequency Resource Assignment" field in the associated SCI.

[0166] The lowest subchannel used for sidelink transmissions is the subchannel of the lowest PRB on which the associated PSCCH is transmitted.

[0167] If a PSSCH scheduled by a PSCCH would overlap with resources containing the PSCCH, then resources corresponding to the union of the PSCCH and the associated PSCCH DM-RS for the scheduled PSSCH are not available for the PSSCH.

[0168] …

[0169] 8.1.4 UE procedure for determining the resource subset to be reported to higher layers in PSSCH resource selection in sidelink resource allocation mode 2

[0170] In resource allocation mode 2, higher layers may request the UE to determine a subset of resources from which the higher layers will select resources for PSSCH / PSCCH transmission. To trigger this procedure, in time slot n, higher layers provide the following parameters for this PSSCH / PSCCH transmission:

[0171] …

[0172] 8.1.5 UE procedure for determining time slots and resource blocks for PSSCH transmissions associated with SCI format 1-A

[0173] The set of time slots and resource blocks used for PSSCH transmission is determined by the resources for PSCCH transmission containing the associated SCI format 1-A and the fields 'Frequency resource assignment', 'Time resource assignment' of the associated SCI format 1-A, as described below.

[0174] 8.2 UE procedures for transmitting sidelink reference signals

[0175] 8.2.1 CSI-RS transmission procedure

[0176] The UE transmits sidelink CSI-RS within a unicast PSSCH transmission if the following conditions hold:

[0177] - CSI reporting is enabled by the higher layer parameter sl-CSI-Acquisition; and

[0178] - The 'CSI Request' field in the corresponding SCI format 2-A or 2-C is set to 1.

[0179] The following parameters for CSI-RS transmission are configured for each CSI-RS configuration:

[0180] -sl-CSI-RS-FirstSymbol indicates the first OFDM symbol in the PRB used for SL CSI-RS

[0181] -sl-CSI-RS-FreqAllocation indicates the number of antenna ports and frequency domain allocation for SL CSI-RS.

[0182] …

[0183] 8.2.4 SL PRS transmission procedure

[0184] The following parameters for SL PRS transmission are associated with each SL PRS resource:

[0185] -[SL PRS Resource ID] indicates the identification of the SL PRS resource. The SL PR resource is identified by a SL PR Resource ID that is unique within a slot of a dedicated SL PR resource pool. For a shared resource pool, the SL PRS resource is uniquely identified by a combination of the SL PRS Resource ID and the SLPRS frequency domain allocation within a slot.

[0186] -[SL PRS Comb Offset and Comb Size] Indicates the comb offset and comb size of the SL PRS resource

[0187] - [Starting symbol and number of SL PRS symbols] indicates the starting symbol index within the slot and the number of symbols of the SL PRS resource.

[0188] - [SL PRS frequency domain allocation] indicates the frequency location [and the number of resource blocks in the shared resource pool used for SL PRS transmission].

[0189] Each SL PRS transmission is associated with a PSCCH transmission in the same slot.

[0190] In case of a dedicated pool for SL positioning, the PSCCH carries SCI format 1-B associated with SL PRS transmission.

[0191] The UE may report the association information of the transmitted SL PRS resources and the UE Tx ARP ID.

[0192] 8.2.4.1 Resource Allocation

[0193] In sidelink resource allocation mode 1:

[0194] - For SL PRS transmission, the UE may be configured with dynamic grant, configured grant type 1 or configured grant type 2.

[0195] 8.2.4.1.1 Resource allocation in the time domain

[0196] The UE shall transmit the SL PRS in the same timeslot as the associated PSCCH.

[0197] The UE shall transmit the SL PRS in consecutive symbols within a slot.

[0198] The UE does not transmit multiple SL PRS resources in the same time slot.

[0199] For a shared resource pool, the UE transmits the SL PRS in PSSCH symbols according to clause 8.1.2.1, [with the following restrictions:

[0200] - The number of contiguous symbols 'M' used for SL PRS transmission shall correspond to one of the SL PRS resources in the parameters.

[0201] - The UE shall not transmit the SL PRS in symbols in which the associated PSCCH is transmitted.

[0202] - The UE shall not transmit SL PRS and PSSCH DMRS in the same symbol.

[0203] - The UE shall transmit the SL PRS on adjacent symbols between or after symbols where the PSSCH DMRS is transmitted.

[0204] - The UE shall transmit the SL PRS only after the last symbol with the second level SCI.

[0205] - For a given value of 'M', the SL PRS resource is mapped to the last consecutive 'M' SL symbols in the slot that satisfy all other constraints.

[0206] -The UE shall not transmit PSSCH and SL PRS in the same symbol. ]

[0207] SL-PRS resources and PSFCH (including the previous slot symbol) are not mapped on the same symbol.

[0208] For a dedicated resource pool, the UE transmits the SL PRS subject to the following restrictions:

[0209] - The UE shall not transmit the SL PRS and the associated PSCCH in the same symbol;

[0210] - The number of contiguous symbols and starting symbol used for SL PRS transmission shall correspond to one of the SL PRS resources in parameter [].

[0211] In sidelink resource allocation mode 1 of the shared resource pool, the time domain behavior of sidelink dynamic grant and sidelink configured grant of SL PRS follows the behavior in clause 8.1.2.1.

[0212] In sidelink resource allocation mode 1 of a dedicated resource pool, the time domain behavior of sidelink dynamic grants and sidelink configured grants for SL PRS follows the behavior in clause 8.1.2.1 with the following modifications:

[0213] -["DCI format 3_0" is replaced by "DCI format 3_2"].

[0214] - "PSSCH" is replaced by "SL PRS".

[0215] 8.2.4.1.2 Resource allocation in the frequency domain

[0216] For the shared resource pool, the frequency domain resource assignment of the SL PRS resources is the same as that of the PSSCH in the same time slot.

[0217] For a dedicated resource pool, the frequency domain resource assignment of the SL PRS resources is the same as the frequency resources of the resource pool.

[0218] 8.2.4.2 UE procedure for determining resource subset to be reported to higher layers in SL PRS resource selection in dedicated resource pool in sidelink resource allocation mode 2

[0219] In resource allocation mode 2, in a dedicated resource pool, higher layers may request the UE to determine a subset of resources from which higher layers will select resources for SL PRS[ / PSCCH] transmission. To trigger this procedure, in time slot n, higher layers provide the following parameters for this SL PRS[ / PSCCH] transmission:

[0220] …

[0221] 8.2.4.2 UE procedure for determining timeslots and SL PRS resources associated with SCI format 1-B in the dedicated resource pool

[0222] The time slot and the set of SL PRS resources used for SL PRS transmission are determined by the PSCCH containing the associated SCI format 1-B and the fields '[SL-PRS resource ID]', '[time resource assignment]' of the associated SCI format 1-B, as described below.

[0223] Determine the set of time slots as in clause 8.1.5, with the following modifications:

[0224] - “SCI format 1-A” is replaced by “SCI format 1-B”,

[0225] - [Potential parameter name change].

[0226] The first SL PRS resource is determined according to the subchannel containing the associated SCI format 1-B used for PSCCH transmission: the index of the subchannel in the resource pool is the same as the index of the SL PRS resource provided by [higher layer parameter].

[0227] If [sl-MaxNumPerReserve] is 2, the index of the second SL PRS resource is indicated by the field [Resource ID indication].

[0228] [If [sl-MaxNumPerReserve] is 3, the index of the second / third SL PRS resource is indicated by the field [Resource ID indication].]

[0229] If the TRIV determined according to clause 8.1.5 indicates N < sl-MaxNumPerReserve, the SL PRS resource indexes corresponding to the last sl-MaxNumPerReserve minus N resources are not used.

[0230] The number of time slots in a set of time and frequency resources for the transmission opportunity of SL PRS is given by C resel where C resel = 10 * SL_RESOURCE_RESELECTION_COUNTER[10, TS 38.321] (if configured), otherwise C resel is set to 1.

[0231] If the SL PRS resource in a time slot is determined as the time and frequency resource for SL PRS transmission corresponding to the selected sidelink grant (described in [10, TS 38.321]), the same SL PRS resource in the time slot is also determined for SL PRS transmission corresponding to the same sidelink grant, where j = 1, 2, …, C resel - 1, and according to clause 8.1.7, P rsvp_TX (if provided) is converted from milliseconds to logical time slots, resulting in P′ rsvp_TX , and is determined by clause 8. Here, P rsvp_TX is the resource reservation interval indicated by the higher layer.

[0232] …

[0233] 8.3 UE Procedure for Receiving Physical Sidelink Shared Channel

[0234] For sidelink resource allocation mode 1, upon detecting SCI format 1-A on PSCCH, the UE may decode PSSCH according to the detected SCI formats 2-A, 2-B and 2-C and the associated PSSCH resource configuration configured by higher layers. The UE does not need to decode more than one PSCCH at each PSCCH resource candidate.

[0235] For sidelink resource allocation mode 2, upon detecting SCI format 1-A on PSCCH, the UE may decode the PSSCH according to the detected SCI formats 2-A, 2-B and 2-C and the associated PSSCH resource configuration configured by higher layers. The UE does not need to decode more than one PSCCH at each PSCCH resource candidate.

[0236] If SCI format 1-A indicates an MCS table that is not supported by the UE, the UE is required to decode neither the corresponding SCI formats 2-A, 2-B, and 2-C nor the PSSCH associated with SCI format 1-A.

[0237] 8.4 UE procedures for receiving reference signals

[0238] …

[0239] 8.4.4 SL PRS Receiving Procedure

[0240] The UE may be configured via [higher layer parameters] to measure and report one or more of SL RSTD, SL Rx-Tx time difference, SL RTOA, SL AoA, SL PRS-RSRP, and SL PRS-RSRPP measurements for the first detected path and / or the additional detected paths. The UE may report the ARP ID associated with the reported measurements. The UE may provide ARP location information for the ARP ID via [higher layer parameters].

[0241] The UE uses the same ARP to transmit and receive the sidelink positioning reference signal and perform SL Rx-Tx time difference measurement at the same time.

[0242] When the UE reports one or more of SL RSTD, SL Rx-Tx time difference, SL RTOA, SL AoA, SL PRS-RSRP and SL PRS-RSRPP measurements, the UE may include the SL PRS resource ID.

[0243] For SL RSTD, SL Rx-Tx time difference, SL RTOA, SL AoA, SL PRS-RSRP and SL PRS-RSRPP measurements, the UE reports the associated SL PRS reception timestamp via the higher layer parameter [sl-prs-time-stamp]. For SL Rx-Tx time difference, the UE may report the associated SL PRS transmission timestamp via the higher layer parameter [sl-prs-time-stamp]. The timestamp contains the SFN, slot number, and optionally nr-PhysCellID , nr-ARFCN, nr-CellGlobalID, or a timestamp containing the DFN and timeslot number.

[0244] The UE may report the LoS / NLoS indicator via [nr-los-nlos-Indicator] associated with each SL RSTD, SL Rx-Tx time difference, SL RTOA, SL AoA, SL PRS-RSRP and SLPRS-RSRPP measurements.

[0245] The UE may report synchronization information synchronization source type and / or relative time difference with associated quality metrics via [higher layer parameters]. For SL RSTD measurement, the UE may report reference UE information.

[0246] For SL RTOA measurements, the SFN or DFN initialization time may be provided by the UE or the network to the UE.

[0247] The location information of other UEs may be provided to the UE via [higher layer parameters]. The UE may report the location information of the UE to the network.

[0248] The expected SL AoA and the uncertainty range of the expected SL AoA may be provided to the UE via [higher layer parameters].

[0249] The UE may report the quality metric [temporal quality] corresponding to SL RSTD, SL RTOA or SL Rx-Tx time difference measurement. The UE may report the quality metric [angular quality] corresponding to SL AoA measurement. [If the '[SL PRS Request]' field in the SCI associated with the received SL PRS is set to 1, the UE shall report this request for SL PRS transmission to higher layers.]

[0250] 8.5 UE Procedure for Reporting Channel State Information (CSI)

[0251] 8.5.1 Channel State Information Framework

[0252] CSI consists of a channel quality indicator (CQI) and a rank indicator (RI). CQI and RI are always reported together.

[0253] 8.5.1.1 Report Configuration

[0254] The UE shall calculate the CSI parameters (if reported) assuming the following dependencies between them:

[0255] - The CQI should be calculated conditioned on the reported RI.

[0256] CSI reporting may be aperiodic (using [10, TS 38.321]). Table 8.5.1.1-1 shows the supported combinations of CSI reporting configuration and CSI-RS configuration and how CSI reporting is triggered for CSI-RS configuration. Aperiodic CSI-RS is configured and triggered / activated as described in clause 8.5.1.2.

[0257] Table 8.5.1.1-1: Triggering / activation of CSI reporting for possible CSI-RS configurations

[0258] CSI-RS Configuration Non-periodic CSI reports Aperiodic CSI-RS Triggered by SCI.

[0259] For CSI reporting, wideband CQI reporting is supported. For the entire CSI reporting band, wideband CQI is reported for a single codeword.

[0260] **************************End of Quote [2]********************************

[0261] In TS 38.212 ([3] 3GPP TS 38.212 V18.0.0 (2023-09)), SL-related control information is specified.

[0262] ************************** Quote [3] Start **********************************

[0263] 8.3 Sidelink Control Information on PSCCH

[0264] The SCI carried on the PSCCH is the first-level SCI, which transmits sidelink scheduling information.

[0265] 8.3.1 Level 1 SCI Format

[0266] …

[0267] 8.3.1.1 SCI Format 1-A

[0268] SCI format 1-A is used for scheduling PSSCH and level 2 SCI on PSSCH

[0269] The following information is transmitted using SCI Format 1-A:

[0270] - Priority - 3 bits, as specified in clause 5.4.3.3 of [12, TS 23.287] and clause 5.22.1.3.1 of [8, TS 38.321]. A value of '000' in the priority field corresponds to a priority value of '1', a value of '001' in the priority field corresponds to a priority value of '2', and so on.

[0271] - Frequency resource assignment - the number of bits determined as follows:

[0272] -…

[0273] - Time Resource Assignment - 5 bits, when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 2; otherwise 9 bits, when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 3, as defined in clause 8.1.5 of [6, TS 38.214].

[0274] -Resource reservation period- bits, as defined in clause 16.4 of [5, TS 38.213], where N rsv_period It is the number of entries in the higher layer parameter sl-ResourceReservePeriodList if the higher layer parameter sl-MultiReserveResource is configured; otherwise it is 0 bit.

[0275] -DMRS Mode- bits, as defined in clause 8.4.1.1.2 of [4, TS 38.211], where N 模式 It is the number of DMRS patterns configured by the higher layer parameter sl-PSSCH-DMRS-TimePatternList.

[0276] - Level 2 SCI format - 2 bits, as defined in Table 8.3.1.1-1.

[0277] - Beta_offset indicator - 2 bits, as provided by higher layer parameter sl-BetaOffsets2ndSCI and Table 8.3.1.1-2.

[0278] - Number of DMRS ports - 1 bit, as defined in Table 8.3.1.1-3.

[0279] - Modulation and coding scheme - 5 bits, as defined in clause 8.1.3 of [6, TS 38.214].

[0280] - Additional MCS table indicator - as defined in clause 8.1.3.1 of [6, TS 38.214]: 1 bit if one MCS table is configured by the higher layer parameter sl-Additional-MCS-Table; 2 bits if two MCS tables are configured by the higher layer parameter sl-Additional-MCS-Table; otherwise 0 bit.

[0281] -PSFCH Overhead Indication - 1 bit, as defined in clause 8.1.3.2 of [6, TS 38.214], provided that the higher layer parameter sl-PSFCH-Period = 2 or 4; otherwise 0 bit.

[0282] - Reserved - The number of bits determined by:

[0283] -N 预留 bits, as configured by the higher layer parameter sl-NumReservedBits, where the value is set to zero, provided that the higher layer parameter sl-IndicationUE-B is not configured, or the higher layer parameter sl-IndicationUE-B is configured to 'disable';

[0284] -Otherwise (N 预留 -1) bit, where the value is set to zero.

[0285] - Conflict Message Receiver Flag - 0 or 1 bit

[0286] - 1 bit, provided that the higher layer parameter sl-IndicationUE-B is configured to 'enabled', wherein a bit value of 0 indicates that the UE is not likely to be a UE that receives conflicting information, and a bit value of 1 indicates that the UE may be a UE that receives conflicting information, as defined in clause 16.3.0 of [5, TS 38.213];

[0287] -Otherwise 0 bit.

[0288] Table 8.3.1.1-1: Level 2 SCI format

[0289] Value of the Level 2 SCI format field Level 2 SCI format 00 SCI Format 2-A 01 SCI Format 2-B 10 SCI Format 2-C 11 SCI Format 2-D

[0290] …

[0291] 8.3.1.2 SCI Format 1-B

[0292] SCI format 1-B is used to schedule SL PRS of dedicated resource pools.

[0293] The following information is transmitted with the help of SCI Format 1-B:

[0294] - Priority - 3 bits, as specified in clause xx of [12, TS 23.586] and clause xx of [8, TS 38.321]. A value of '000' in the priority field corresponds to a priority value of '1', a value of '001' in the priority field corresponds to a priority value of '2', and so on.

[0295] - Source ID - 12 or 24 bits, determined by higher layer parameter XYZ, as defined in clause xx of [6, TS 38.214].

[0296] - Destination ID - 24 bits, as defined in clause xx of [6, TS 38.214].

[0297] - Broadcast type indicator - 2 bits, as defined in Table 8.3.1.2-1 and in clause xx of [6, TS 38.214].

[0298] -Resource reservation period- bits, as defined in clause xx of [5, TS 38.213], where N rsv_period It is the number of entries in the higher layer parameter reservationPeriodAllowed-Dedicated-SL-PRS-RP if the higher layer parameter reservationPeriodAllowed-Dedicated-SL-PRS-RP is configured; otherwise it is 0 bit.

[0299] - Time Resource Assignment - 5 bits, when the value of the higher layer parameter sl-MaxNumPerReserveSL-PRS is configured to 2; otherwise 9 bits, when the value of the higher layer parameter sl-MaxNumPerReserveSL-PRS is configured to 3, as defined in clause xxx of [6, TS38.214].

[0300] - Resource ID Indication - If the value is set to 2, the value of the higher layer parameter sl-MaxNumPerReserveSL-PRS is set to 2; otherwise, the value is set to x, and the value of the higher layer parameter sl-MaxNumPerReserveSL-PRS is set to 3. SL-PRS is the total number of SL PRS resources within the time slots in the dedicated resource pool used for SL PRS transmission and is provided by the higher layer parameter XYZ.

[0301] -SL PRS Request - 1 bit, as defined in clause xx of [TS 38.214], when higher layer parameters XYZ are provided; otherwise 0 bit.

[0302] -Reserved-N 预留 Bit, as configured by higher layer parameter XYZ, where the value is set to zero.

[0303] Table 8.3.1.2-1: Broadcast type indicator

[0304] The value of the broadcast type indicator Broadcast Type 00 broadcast 01 Multicast 10 Unicast 11 Reserve

[0305] 8.4 Sidelink Control Information on PSSCH

[0306] The SCI carried on the PSSCH is a level 2 SCI, which transmits sidelink scheduling information and / or inter-UE coordination related information.

[0307] 8.4.1 Level 2 SCI Format

[0308] …

[0309] 8.4.1.1 SCI Format 2-A

[0310] SCI format 2-A is used to decode the PSSCH through the HARQ operation when the HARQ-ACK information includes ACK or NACK, when the HARQ-ACK information includes only NACK, or when there is no feedback of the HARQ-ACK information.

[0311] The following information is transmitted with the help of SCI Format 2-A:

[0312] -HARQ process number - 4 bits.

[0313] - New data indicator - 1 bit.

[0314] - Redundancy Version - 2 bits, as defined in Table 7.3.1.1.1-2.

[0315] - Source ID - 8 bits, as defined in clause 8.1 of [6, TS 38.214].

[0316] - Destination ID - 16 bits, as defined in clause 8.1 of [6, TS 38.214].

[0317] - HARQ feedback enable / disable indicator - 1 bit, as defined in clause 16.3 of [5, TS 38.213].

[0318] - Broadcast type indicator - 2 bits, as defined in Table 8.4.1.1-1 and in clause 8.1 of [6, TS 38.214].

[0319] - CSI Request - 1 bit, as defined in clause 8.2.1 of [6, TS 38.214] and in clause 8.1 of [6, TS 38.214].

[0320] Table 8.4.1.1-1: Broadcast type indicator

[0321]

[0322] 8.4.1.2 SCI Format 2-B

[0323] SCI format 2-B is used to decode the PSSCH through the HARQ operation when the HARQ-ACK information includes only NACK or when there is no feedback of the HARQ-ACK information.

[0324] The following information is transmitted with the help of SCI Format 2-B:

[0325] -HARQ process number - 4 bits.

[0326] - New data indicator - 1 bit.

[0327] - Redundancy Version - 2 bits, as defined in Table 7.3.1.1.1-2.

[0328] - Source ID - 8 bits, as defined in clause 8.1 of [6, TS 38.214].

[0329] - Destination ID - 16 bits, as defined in clause 8.1 of [6, TS 38.214].

[0330] - HARQ feedback enable / disable indicator - 1 bit, as defined in clause 16.3 of [5, TS 38.213].

[0331] - Zone ID - 12 bits, as defined in clause 5.8.11 of [9, TS 38.331].

[0332] -Communication Range Requirement - 4 bits, determined by the higher layer parameter sl-ZoneConfigMCR-Index.

[0333] 8.4.1.3 SCI Format 2-C

[0334] SCI format 2-C is used to decode the PSSCH and provide or request inter-UE coordination information. SCI format 2-C may be used only for unicast.

[0335] The following information is transmitted with the help of SCI Format 2-C:

[0336] -HARQ process number - 4 bits

[0337] - New data indicator - 1 bit

[0338] - Redundancy version - 2 bits, as defined in Table 7.3.1.1.1-2

[0339] - Source ID - 8 bits, as defined in clause 8.1 of [6, TS 38.214]

[0340] - Destination ID - 16 bits, as defined in clause 8.1 of [6, TS 38.214]

[0341] - HARQ feedback enable / disable indicator - 1 bit, as defined in clause 16.3 of [5, TS 38.213]

[0342] - CSI Request - 1 bit, as defined in clause 8.2.1 of [6, TS 38.214] and clause 8.1 of [6, TS 38.214]

[0343] - Provide / Request Indicator - 1 bit, where a value of 0 indicates that SCI format 2-C is used to provide inter-UE coordination information, and a value of 1 indicates that SCI format 2-C is used to request inter-UE coordination information

[0344] If the 'Offer / Request Indicator' field is set to 0, then all remaining fields are set as follows:

[0345] - Resource combination - bits, as defined in clause 8.1.5A of [6, TS 38.214], where

[0346] - And N rsv_period is the number of entries in the higher layer parameter sl-ResourceReservePeriodList if the higher layer parameter sl-MultiReserveResource is configured; otherwise Y = 0

[0347] - is the number of subchannels in the resource pool provided by the higher layer parameter sl-NumSubchannel

[0348] - First resource position - 8 bits, as defined in clause 8.1.5A of [6, TS 38.214].

[0349] - Reference time slot position - bits, as defined in clause 8.1.5A of [6, TS 38.214], where μ is defined in Table 4.2-1 of clause 4.2 of [4, TS 38.211].

[0350] - Resource set type - 1 bit, where a value of 0 indicates a preferred resource set and a value of 1 indicates a non-preferred resource set.

[0351] -Lowest Subchannel Index- bits, as defined in clause 8.1.5A of [6, TS 38.214].

[0352] If the 'Offer / Request Indicator' field is set to 1, then all remaining fields are set as follows:

[0353] - Priority - 3 bits, as specified in clause 5.4.3.3 of [12, TS 23.287] and clause 5.22.1.3.1 of [8, TS 38.321]. A value of '000' in the priority field corresponds to a priority value of '1', a value of '001' in the priority field corresponds to a priority value of '2', and so on.

[0354] -Number of subchannels- bits, as defined in clause 8.1.4A of [6, TS 38.214].

[0355] -Resource reservation period- bits, as defined in clause 8.1.4A of [6, TS 38.214], where N rsv_period It is the number of entries in the higher layer parameter sl-ResourceReservePeriodList if the higher layer parameter sl-MultiReserveResource is configured; otherwise it is 0 bit.

[0356] - Resource selection window location - bits, as defined in clause 8.1.4A of [6, TS 38.214], where μ is defined in Table 4.2-1 of clause 4.2 of [4, TS 38.211].

[0357] - Resource set type - 1 bit, where a value of 0 indicates a request for provision of inter-UE coordination information for preferred resource sets and a value of 1 indicates a request for provision of inter-UE coordination information for non-preferred resource sets, provided that the higher layer parameter sl-DetermineResourceType is configured to 'ueb'; otherwise, 0 bit.

[0358] -Padding bits.

[0359] For operations in the same resource pool, zeros shall be appended to the SCI format 2-C whose 'Offer / Request Indicator' field is set to 1 until the payload size equals the payload size of the SCI format 2-C whose 'Offer / Request Indicator' field is set to 0.

[0360] 8.4.1.4 SCI Format 2-D

[0361] SCI format 2-D is used for decoding of PSSCH and scheduling of SL PRS of the shared resource pool.

[0362] The following information is transmitted with the help of SCI format 2-D:

[0363] -SL PRS Resource ID- Bit, where value N SL-PRS is the total number of SL PRS resource IDs within the timeslots in the shared resource pool used for SL PRS transmission and is provided by the higher layer parameter XYZ.

[0364] -SL PRS Request - 1 bit, as defined in clause xx of [6, TS 38.214], when higher layer parameters XYZ are provided; otherwise 0 bit.

[0365] -Embedded SCI Format - 2 bits. This field indicates the Embedded SCI format as defined in Table 8.4.1.4-1.

[0366] -Embedded SCI Format Payload - Number of bits determined according to Table 8.4.1.4-1. This field is set to the associated payload of the embedded SCI format indicated by the 'Embedded SCI Format' field, as defined in Table 8.4.1.4-1.

[0367] Table 8.4.1.4-1: Embedded SCI format and payload

[0368]

[0369]

[0370] …

[0371] 8.4.4 Rate Matching

[0372] For a level 2 SCI transmission on PSSCH with SL-SCH, the number of coded modulation symbols generated for the level 2 SCI transmission before being repeated for layer 2 (if present) is denoted as Q S ' CI2 , which is determined as follows:

[0373] …

[0374] 8.4.5 Multiplexing of Coded Level 2 SCI Bits onto PSSCH

[0375] The coded level 2 SCI bits are multiplexed onto the PSSCH according to the procedure in clause 8.2.1.

[0376] ***************************End of Quote [3]********************************

[0377] In the draft CR of TS 38.321 ([5] R2-2312264), SL-PRS related standard changes in the MAC layer are specified.

[0378] *************************** Quote [5] Start **********************************

[0379] 3.1 Definition

[0380] For the purposes of this document, the terms and definitions given in TR 21.905 [1] and below apply. A term defined in this document takes precedence over the definition of the same term (if any) in TR 21.905 [1].

[0381] …

[0382] Ranging / sidelink positioning: AS functionality implements ranging-based services and sidelink positioning, such as in TS 23.586 [xx] in.

[0383] Serving cell: PCell, PSCell or SCell in TS 38.331[5].

[0384] Sidelink transmission information: as specified in clauses 8.3 and 8.4 of TS 38.212 [9] for SL-SCH transmission or SL-PRS transmission with or without SL-SCH transmission on the SL-PRS shared resource pool The sidelink transmission information included in the SCI of the UE consists of the following: sidelink HARQ information, which includes NDI, RV, sidelink process ID, HARQ feedback enable / disable indicator; sidelink identification information, which includes broadcast type indicator, source layer 1 ID and destination layer 1 ID; and sidelink other information, which includes CSI request , SL-PRS request, SL-PRS resource ID , priority, communication range requirement and zone ID.

[0385] SL-PRS dedicated resource pool: Sidelink resource pool that can be used for SL-PRS transmission and cannot be used for PSSCH transmission. Source pool.

[0386] SL-PRS shared resource pool: A sidelink resource pool that can be used for transmission of both SL-PRS and PSSCH.

[0387] Information about SL-PRS transmission in the SL-PRS dedicated resource pool: Information about SL-PRS transmission in the SL-PRS dedicated resource pool The information is contained in the SCI for SL-PRS transmission on the SL-PRS dedicated resource pool, as specified in TS 38.212 [9], which It is composed of the following

[0388] -SL-PRS identification information, including broadcast type indicator, source ID and destination ID;

[0389] -SL-PRS transmits other information, including SL-PRS priority, SL-PRS request, SL-PRS resource ID and resource reservation Retention cycle.

[0390] =============================Next Change=========================

[0391] …

[0392] 5.22 SL-SCH data transmission and SL-PRS transmission

[0393] 5.22.1 SL-SCH Data and SL-PRS Teleport

[0394] 5.22.1.1 SL Grant Receipt and SCI Transmission

[0395] Sidelink grants are received dynamically on the PDCCH, semi-statically configured by the RRC or autonomously selected by the MAC entity. The MAC entity may have sidelink grants on active SL BWPs to determine the set of PSSCH durations in which transmissions of SCI occur, and the set of PSSCH durations in which transmissions of SL-SCH associated with SCI occur. A MAC entity may have an active The sidelink grant on the SL-PRS shared resource pool of the BWP is activated to determine the PSCCH duration in which the transmission of the SCI occurs The set, and the SL-PRS transmission timing and PSSCH duration at which the transmission of the SL-PRS and SL-SCH associated with the SCI occurs The MAC entity may have a sidelink grant on the SL-PRS dedicated resource pool with an active BWP to determine where the transmission The set of PSCCH durations in which transmission of the SCI occurs, and the set of SL-PRS durations in which transmission of the SL-PRS associated with the SCI occurs Transmission timing collection. A sidelink grant addressed to a SLCS-RNTI with NDI=1 is considered a dynamic sidelink grant. As in In clause 7.3.1.4.3 of TS38.212 [9], the sidelink addressed to the SL-PRS-CS-RNTI with activation / release indication = 1 The grant is considered a dynamic sidelink grant. If the MAC entity has been configured with sidelink resource allocation mode 1, Or if MAC The entity has been configured with resource allocation scheme 1 and receives a PDCCH for resource allocation in the SL-PRS shared resource pool. distribute , as indicated in TS 38.331 [5], then for each PDCCH opportunity and for each grant received for this PDCCH opportunity, the MAC entity shall:

[0396] 1> If a sidelink grant has been received on the PDCCH for the SL-RNTI of the MAC entity:

[0397] 2> If the NDI received on the PDCCH has not yet transitioned compared to the value in the previously received HARQ information for the HARQ process ID:

[0398] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration and SL-PRS Transmission timing (if applicable), A single MAC PDU for a corresponding sidelink process according to clause 8.1.2 of TS 38.214 [7] and SL-PRS according to clause 8.1.4 of TS 38,214[7] one or more retransmissions;

[0399] 2> Otherwise:

[0400] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration and SL-PRS Transmission timing (if applicable), for initial transmission and a single MAC PDU according to clause 8.1.2 of TS 38.214 [7] and SL-PRS retransmission (if available);

[0401] NOTE: When SL-PRS is transmitted on the SL-PRS shared resource pool, only after the LCP procedure in clause 5.22.1.4.1 Then determine the PSSCH duration and SL-PRS transmission timing.

[0402] 1> Otherwise, if a sidelink grant has been received on the PDCCH for the SLCS-RNTI of the MAC entity:

[0403] 2> If the PDCCH content indicates a retransmission of the identified HARQ process ID that has been set for the activated configured sidelink identified by sl-ConfigIndexCG:

[0404] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration and SL-PRS Teleport timing (if applicable) , for a single MAC PDU according to clause 8.1.2 of TS 38.214 [7] and SL-PRS One or more retransmissions.

[0405] 2> Otherwise, if the PDCCH content indicates a configured grant type 2 deactivation for a configured sidelink grant:

[0406] 3> Trigger a configured side link grant confirm for the configured side link grant.

[0407] 2> Otherwise, if the PDCCH content indicates a configured grant type 2 activation for a configured sidelink grant:

[0408] 3> trigger a configured side link grant confirmation for the configured side link grant;

[0409] 3>Store the configured side link grant;

[0410] 3 >initialize or reinitialize a configured sidelink grant to determine a set of PSCCH durations and a set of PSSCH durations for transmission of multiple MAC PDUs according to clause 8.1.2 of TS 38.214 [7], and for use according to TS SL-PRS transmission opportunity set for transmission of multiple SL-PRSs as per clause 8.2.4 of 38.214[7] (if applicable) .

[0411] 1> If dynamic sidelink grant is available for retransmission of a MAC PDU that has been positively acknowledged as specified in clause 5.22.1.3.1a:

[0412] 2> Clear the PSCCH duration and PSSCH duration corresponding to the retransmission of the MAC PDU from the sidelink grant.

[0413] Editor's Note: When the FFS MAC PDU has been positively acknowledged by resource allocation scheme 1, the SL-PRS shared resource pool SL-PRS transmission.

[0414] If the MAC entity has been configured with sidelink resource allocation scheme 1 and receives a PDCCH for SL- Resource allocation is performed on the PRS dedicated resource pool, as in TS 38.331 [5], then for each PDCCH opportunity, the MAC entity shall:

[0415] 1> If a sidelink grant for the SL-PRS-RNTI of the MAC entity has been received on the PDCCH: (i.e., for Dynamic Grant

[0416] 2 > Use the received sidelink grant to determine the PSCCH duration for transmission or retransmission of SL-PRS time and corresponding SL-PRS timing.

[0417] 1> Otherwise, if a sidelink grant for the SL-PRS-CS-RNTI for the MAC entity has been received on the PDCCH: (i.e., configured sidelink grant type 2)

[0418] 2> If the PDCCH content indicates retransmission of SL-PRS transmission:

[0419] 3> Use the received sidelink grant to determine the PSCCH duration for one or more retransmissions of SL-PRS Duration and SL-PRS transmission timing, as in clause 8.2.4 of TS 38.214 [7].

[0420] 2> Otherwise, if the PDCCH content indicates a configured grant type 2 activation for a configured sidelink grant:

[0421] 3>Store the configured side link grant;

[0422] 3> trigger a configured grant confirmation for the configured side link grant;

[0423] 3> Initialize or reinitialize the configured sidelink grant to determine the PSCCH duration for transmission of SL-PRS The duration set and the corresponding SL-PRS timing.

[0424] 2> Otherwise, if the PDCCH content indicates a configured type 2 deactivation for a configured sidelink grant:

[0425] 3> Trigger a configured grant confirm for a configured sidelink grant.

[0426] If the MAC entity has been configured with sidelink resource allocation mode 2 to transmit or is configured with resource allocation Option 2 for transmission , using a resource pool in the carrier, as indicated in TS 38.331 [5] or TS 36.331

[21] , based on full sensing, or partial sensing, or random selection, or any combination, then for each side link process and SL-PRS transmission , the MAC entity shall:

[0427] NOTE 0: For SL-PRS transmission on the SL-PRS dedicated resource pool through resource allocation scheme 2, Partial sensing.

[0428] NOTE 1: If the MAC entity is configured with sidelink resource allocation mode 2 or resource allocation scheme 2 To transmit using a resource pool in a carrier, as indicated in TS 38.331 [5] or TS 36.331

[21] , the MAC entity may generate a selected sidelink grant on the resource pool based on random selection, or partial sensing, or full sensing only after releasing the configured sidelink grant (if any).

[0429] NOTE 2: The MAC entity expects that the PSFCH is always configured by RRC for at least one resource pool in sl-TxPoolSelectedNormal and for resource pools in sl-TxPoolExceptional if at least a logical channel configured with sl-HARQ-FeedbackEnabled is set to enabled.

[0430] NOTE 2A: For transmission of the sidelink inter-UE coordination request MAC CE, the MAC entity selects the TX resource pool where the IUC resource set is required. For transmission of the sidelink inter-UE coordination information MAC CE, the MAC entity selects the TX resource pool where the IUC resource set is located.

[0431] …

[0432] For each PSCCH duration on the SL-PRS dedicated resource pool, the MAC entity shall:

[0433] 1> if the MAC entity is not configured with multiple SL-PRS transmissions using resource allocation scheme 2; or

[0434] 1> If the MAC entity is configured with resource allocation scheme 1:

[0435] 2> Set the resource reservation period to 0.

[0436] 1> Otherwise, if the MAC entity is configured with multiple SL-PRS transmissions using resource allocation scheme 2:

[0437] 2>Set the resource reservation period to the selected value.

[0438] Editor's Note: When FFS triggers SCI from a peer UE, the SL-PRS priority is determined by the peer UE's UCI or the UE's own The priority in the higher layer is determined by itself.

[0439] Editor's Note: FFS determines the SL-PRS priority when the SL-PRS is triggered by the UE's own higher layers.

[0440] for Not on the SL-PRS dedicated resource pool The HARQ process ID associated with the first time slot of a configured sidelink grant transmitted by the SL is derived from the following equation:

[0441] HARQ process ID=[floor(CURRENT_slot / PeriodicitySL)]modulo sl-NrOfHARQ-Processes+sl-HARQ-ProcID-offset

[0442] in CURRENT_slot refers to the current logical slot in the associated resource pool and PeriodicitySL is defined in clause 5.8.3.

[0443] …

[0444] 5.22.1.3 Sidelink HARQ Operation and SL-PRS transmission on the SL-PRS shared resource pool

[0445] 5.22.1.3.1 Sidelink HARQ Entity

[0446] The MAC entity includes at most one sidelink HARQ entity for transmitting on the SL-SCH, thereby maintaining several parallel sidelink processes.

[0447] The maximum number of transmitting sidelink processes associated with a sidelink HARQ entity is 16. A sidelink process may be configured to transmit multiple MAC PDUs. To transmit multiple MAC PDUs in sidelink resource allocation mode 2, the maximum number of transmitting sidelink processes associated with a sidelink HARQ entity is 4.

[0448] Editor's Note: FFS allows the maximum number of SL processes transmitted by SL-PRS.

[0449] The delivered sidelink grant and its associated sidelink transmission information are associated with the sidelink process. Each sidelink process supports one TB.

[0450] for Not on the SL-PRS dedicated resource pool For each sidelink grant, the sidelink HARQ entity shall:

[0451] 1> if the MAC entity determines that the sidelink is granted for the initial transmission, as specified in clause 5.22.1.1; or

[0452] 1> if the sidelink grant is a configured sidelink grant and no MAC PDU is obtained in the sl-PeriodCG of the configured sidelink grant; or

[0453] 1> If the sidelink grant is a dynamic sidelink grant or a selected sidelink grant and no MAC PDU was obtained in the previous sidelink grant when the PSCCH duration and level 2 SCI on PSSCH of the previous sidelink grant are not within the SL DRX active time with data to be sent as specified in clause 5.28.3 at either destination:

[0454] Note 1: Vacant.

[0455] 2> (re)associate the sidelink process to this grant, and for the associated sidelink process:

[0456] 2> If all PSCCH durations and PSSCH durations for initial transmission of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0457] ●3> Ignore sidelink grant.

[0458] NOTE 1A: The sidelink HARQ entity shall associate the selected sidelink grant to the sidelink process determined by the MAC entity.

[0459] 2> Otherwise:

[0460] 3> Get the MAC PDU to be transmitted from the multiplexing and combining entity (if any);

[0461] ●3> If the MAC PDU to be transmitted has been obtained:

[0462] 4> If HARQ process ID has been set for sidelink grant:

[0463] ●5> (re)associate the HARQ process ID corresponding to the sidelink grant to the sidelink process.

[0464] NOTE 1a: There is a one-to-one mapping between HARQ process IDs and sidelink processes in a MAC entity configured to use sidelink resource allocation mode 1.

[0465] 4> Determine the sidelink transmission information of the TB for the source and destination pair of the MAC PDU as follows:

[0466] ●5> Set the source layer 1 ID to the 8 LSBs of the source layer 2 ID of the MAC PDU;

[0467] ●5> Set the destination layer 1 ID to the 16 LSBs of the destination layer 2 ID of the MAC PDU;

[0468] ●5> (re)associate the sidelink process to the sidelink process ID;

[0469] NOTE 1b: How the UE determines the sidelink process ID in the SCI depends on the UE implementation for the NR sidelink.

[0470] ●5> consider that the NDI has been converted compared to the previously transmitted value corresponding to the sidelink identification information and the sidelink process ID of the MAC PDU, and set the NDI to the converted value;

[0471] NOTE 2: The initial value of NDI set for the first transmission of the associated sidelink process depends on the UE implementation.

[0472] Note 3: Vacant.

[0473] ●5> If the MAC PDU is used for NR side link discovery:

[0474] 6> Set the broadcast type indicator to broadcast.

[0475] 5> Otherwise:

[0476] 6> Set the broadcast type indicator to one of broadcast, multicast and unicast as indicated by the upper layer.

[0477] Editor's Note: The broadcast type indicator is determined based on the logical channel priority order in Section 5.22.1.4. The legacy sidelink communication specification may have issues and how FFS can address this question.

[0478] ●5> if HARQ feedback is enabled for the MAC PDU according to clause 5.22.1.4.2;

[0479] 6> Set the HARQ feedback enable / disable indicator to enabled.

[0480] 5> Otherwise:

[0481] 6> Set the HARQ feedback enable / disable indicator to disable.

[0482] ● 5 > Set the priority to MAC PDU and SL-PRS (if present) The highest priority value of the logical channel (if any) and MAC CE (if included) in;

[0483] Note 3A: …

[0484] ●5> If HARQ feedback is enabled for multicast:

[0485] 6> If both the group size and the member ID are provided by upper layers, and the group size is not greater than the number of candidate PSFCH resources associated with this sidelink grant:

[0486] 7> Select Positive-Negative Confirmation or Negative Confirmation Only.

[0487] NOTE 4: The choice of positive-negative acknowledgement or only negative acknowledgement depends on the UE implementation.

[0488] 6> Otherwise:

[0489] 7> Select Negative confirmation only.

[0490] 6> If Negative Acknowledgement Only is selected, the UE's location information is available, and sl-TransRange has been configured for the logical channel in the MAC PDU, and sl-ZoneConfig is configured as specified in TS 38.331 [5]:

[0491] 7> Set the communication range requirement to the value of the longest communication range of the logical channel in the MAC PDU;

[0492] 7> Determine the value of sl-ZoneLength corresponding to the communication range requirement, and set Zone_id to the value of Zone_id calculated using the determined value of sl-ZoneLength, as specified in TS 38.331 [5].

[0493] ●5>Set the redundant version to the selected value.

[0494] ● 5> If the sidelink grant is matched with the one from higher layers to trigger the peer UE identified by the destination Layer 2 ID The SL-PRS transmitted request is associated with:

[0495] 6> Set SL-PRS Request to Request.

[0496] ● 5> Set the SL-PRS Resource ID to [value of field] in the sidelink transmission information (if available).

[0497] Editor's Note: How FFS determines the SL-PRS resource ID and its impact on MAC.

[0498] 4> TB's MAC PDU, SL-PRS (if available) , sidelink grant and sidelink transmit information delivered to an associated sidelink process;

[0499] 4> Instructs the associated sidelink process to trigger a new transmission.

[0500] 3> Otherwise:

[0501] 4>Flush the HARQ buffer of the associated side link process.

[0502] 1> Otherwise (i.e., retransmit):

[0503] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH, the configured sidelink grant, or the selected sidelink grant is associated to a sidelink process whose HARQ buffer is empty; or

[0504] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH is not associated to any sidelink process; or

[0505] 2> If the PSCCH duration and PSSCH duration for one or more retransmissions of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0506] ●3> Ignore sidelink grant.

[0507] 2> Otherwise:

[0508] 3> Identify the side link process associated with this grant, and for the associated side link process:

[0509] 4> MAC PDU and the SL-PRS (if available) The sidelink grant is delivered to the associated sidelink process;

[0510] 4> Instruct the associated sidelink process to trigger retransmission.

[0511] 5.22.1.3.1a Sidelink Process

[0512] A sidelink process is associated with a HARQ buffer.

[0513] New transmissions and retransmissions are performed on the resources indicated in the sidelink grant as specified in clause 5.22.1.1 with the MCS selected as specified in clause 8.1.3.1 and clause 5.22.1.1 of TS 38.214 [7].

[0514] The process maintains a counter SL_RESOURCE_RESELECTION_COUNTER if the sidelink process is configured to perform transmission of multiple MAC PDUs with sidelink resource allocation mode 2. For other configurations of the sidelink process, this counter is not available.

[0515] The priority of a MAC PDU is determined by the highest priority of the logical channel or MAC CE in the MAC PDU.

[0516] If the sidelink HARQ entity requests a new transmission, the sidelink process shall:

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

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

[0519] 1> Generate a transfer as described below.

[0520] If the sidelink HARQ entity requests a retransmission, the sidelink process shall:

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

[0522] 1> Generate a transfer as described below.

[0523] …

[0524] ===========================Next Change===========================

[0525] 5.22.1.4.1 Logical channel priority sorting

[0526] 5.22.1.4.1.1 Overview

[0527] The sidelink logical channel prioritization procedure is applied whenever a new transmission is performed.

[0528] …5.22.1.4.1.2 Logical channels and SL-PRS Choice

[0529] For each SCI corresponding to a new transmission, the MAC entity shall:

[0530] 1 > If sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon is configured according to TS 38.331[5] ,and;

[0531] 1> If the new transmission does not match SL-PRS dedicated resource pool The sidelink grant is associated with:

[0532] 2> If the new transmission is associated with a sidelink grant in sl-DiscTxPoolSelected or sl-DiscTxPoolScheduling configured in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon:

[0533] 3> Select a destination associated with NR sidelink discovery as specified in TS 23.304

[26] , which is in the SL active time for SL transmit opportunities if SL DRX is applied to the destination, and among the logical channels that meet all of the following conditions for the SL grant associated with the SCI:

[0534] 4> SL data for NR sidelink discovery is available for transmission; and

[0535] 4> in the presence of any logical channel with SBj>0, SBj>0; and

[0536] 4> if configured, sl-configuredGrantType1Allowed is set to true if the SL grant is a configured grant type 1; and

[0537] 4> If configured, sl-AllowedCG-List contains the configured grant index associated with the SL grant.

[0538] 2> Otherwise:

[0539] 3> Select a destination associated with one of unicast, multicast and broadcast (excluding a destination associated with NR sidelink discovery as specified in TS 23.304

[26] ), which is in the SL active time for SL transmit opportunity if SL DRX is applied to the destination, and has a MAC CE and a logical channel with the highest priority and pending SL-PRS transmission At least one of the following conditions is met for the SL grant associated with the SCI and the MAC CE (if any): and SL-PRS Among the logical channels:

[0540] 4> SL data for NR sidelink communication is available for transmission; and

[0541] 4> in the presence of any logical channel with SBj>0, SBj>0; and

[0542] 4> if configured, sl-configuredGrantType1Allowed is set to true if the SL grant is a configured grant type 1; and

[0543] 4> If configured, the sl-AllowedCG-List contains the configured grant index associated with the SL grant; and

[0544] 4> If PSFCH is not configured for the SL grant associated with the SCI, sl-HARQ-FeedbackEnabled is set to disabled.

[0545] 1> Otherwise, if sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon is not configured according to TS 38.331 [5] configured, and;

[0546] 1> If the new transmission is not associated with a sidelink grant on the SL-PRS dedicated resource pool:

[0547] 2 >Select a destination associated with one of unicast, multicast and broadcast, which is in the SL active time for SL transmit opportunity if SL DRX is applied to the destination, and has a MAC CE and a logical channel with the highest priority and pending SL-PRS transmission At least one of the following conditions is met for the SL grant associated with the SCI and the MAC CE (if any): and SL-PRS (if present) Among the logical channels:

[0548] 3>SL data is available for transmission; and

[0549] 3> in the presence of any logical channel with SBj>0, SBj>0; and

[0550] 3> if configured, sl-configuredGrantType1Allowed is set to true if the SL grant is a configured grant type 1; and

[0551] 3> If configured, the sl-AllowedCG-List contains the configured grant index associated with the SL grant; and

[0552] 3> If PSFCH is not configured for the SL grant associated with the SCI, sl-HARQ-FeedbackEnabled is set to disabled.

[0553] NOTE 1: If multiple destinations have a logical channel with the same highest priority that meets all of the above conditions or if multiple destinations have a MAC CE and / or a logical channel with the same priority as the MAC CE that meets all of the above conditions, which destination is selected among them depends on the UE implementation.

[0554] 1> Otherwise: (SL grant is associated on a dedicated SL-PRS resource pool)

[0555] 2> Select a SL associated with one of unicast, multicast, and broadcast and having a SL grant associated with SCI Destination of the highest priority pending SL-PRS transmission.

[0556] Editor's Note: FFS is used as an additional criterion for destination selection in SL-PRS shared and dedicated resource pools.

[0557] 1> If the new transmission is not associated with a sidelink grant on the SL-PRS dedicated resource pool , then select the logical channel that satisfies all of the following conditions from among the logical channels belonging to the selected destination:

[0558] 2>SL data is available for transmission; and

[0559] 2>…

[0560] Note 2: …

[0561] 5.22.1.4.1.3 Allocation of sidelink resources

[0562] For each side link grant associated with the SL-PRS shared resource pool, the MAC entity shall:

[0563] 1> if there is a SL-PRS to be transmitted for the selected destination; and

[0564] 2> If all SL-SCH data in a logical channel with a lower priority value than SL-PRS can be allocated resource:

[0565] · 3> Determine that pending SL-PRS may be transmitted in the sidelink grant.

[0566] 2> The transport block size for new transmission of SL-SCH is derived according to clause 8.1.3.2 in TS38.214 [7].

[0567] Editor's Note: FFS is a mechanism used to prevent high-priority PRS from occupying all resources. Rapp considers this an optimization, but it can be Further discussion.

[0568] Editor's Note: A more detailed procedure used by FFS to determine whether to transmit PRS.

[0569] For the corresponding SL-SCH For each newly transmitted SCI, the MAC entity shall:

[0570] 1> Allocate resources to logical channels as follows:

[0571] 2> Logical channels selected for SL grant under SBj>0 in clause 5.22.1.4.1.2 are allocated resources in descending priority order. If the sPBR of a logical channel is set to infinity, the MAC entity shall allocate resources for all data available for transmission on the logical channel before satisfying the sPBR of lower priority logical channels;

[0572] 2> Decrease SBj by the total size of the MAC SDU serving the above logical channel j;

[0573] 2> If any resources remain, all logical channels selected in clause 5.22.1.4.1.2 are served in strictly descending priority order (regardless of the value of SBj) until the data or SL grants for that logical channel are exhausted (whichever occurs first). Logical channels configured with equal priority shall be served equally.

[0574] …

[0575] …

[0576] 5.22.1.xxSL-PRS Transmission on SL-PRS Dedicated Resource Pool

[0577] For each newly transmitted SCI of SL-PRS, the MAC entity shall:

[0578] 1 >Set the destination ID to the destination Layer 2 ID corresponding to the SL-PRS transmission;

[0579] 1> If [12bitSourceID] is configured:

[0580] 2> Set the source ID to the 12 [most / least significant bits] corresponding to the source layer 2 ID transmitted by the SL-PRS;

[0581] 1> Otherwise, if [24bitSourceID] is configured:

[0582] 2> Set the source ID to the source layer 2 ID corresponding to the SL-PRS transmission;

[0583] 1> Set the broadcast type indicator to one of broadcast, multicast, and unicast selected in clause 5.22.1.2.1.2 indivual;

[0584] 1> Set the SL-PRS priority to the value indicated by the upper layer;

[0585] 1>Set SL-PRS resource ID;

[0586] Editor's Note: How does FFS determine the SL-PRS resource ID and its impact on transmission on the SL-PRS dedicated resource pool? ring.

[0587] 1> If higher layers trigger SL-PRS transmission to the peer UE identified by the destination Layer 2 ID:

[0588] 2> Set SL-PRS request to request.

[0589] Editor's Note: FFS When the Source ID length is configured as 12 bits, is it the MSB or LSB of the UE's Source Layer 2 ID.

[0590] For each retransmission of the SL-PRS, the MAC entity shall use the same SCI field as used for the corresponding new transmission. SCI field.

[0591] For each new transmission or retransmission of SL-PRS, the MAC entity shall:

[0592] 1> if there is no uplink transmission; or

[0593] 1> If there is an uplink transmission, and the sidelink transmission takes precedence over the uplink transmission:

[0594] 2> Instruct the physical layer to transmit SL-PRS with associated SL-PRS transmission information on the SL-PRS dedicated resource pool. SCI given;

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

[0596] 1> If this transmission corresponds to the last transmission of the SL-PRS transmission:

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

[0598] Editor's Note: How FFS maintains resource reselection counters for resource selection in the SL-PRS dedicated resource pool.

[0599] Prioritize the transmission of SL-PRS over the uplink transmission of the MAC entity or another MAC entity if the following conditions are met: Link transmission:

[0600] 1> If the MAC entity is not able to perform this sidelink transmission and all uplink transmissions simultaneously while transmitting, and and

[0601] 1> If [ul-PrioritizationThres] is configured, and if all NR uplink transmissions have logical The highest priority value of the channel is not less than [ul-PrioritizationThres], and

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

[0603] Editor's Note: Does FFS still need to be prioritized over SL-PRS for uplink transmission by higher layers? The criteria for prioritization.

[0604] ==============================Next Change== ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝

[0605] 5.22.1.yy SL-PRS Resource Request

[0606] SL-PRS transmission can be triggered by lower layer signaling from a peer UE or the UE's own higher layers. The request procedure is used to provide the gNB with information about the SL-PRS that the UE needs to transmit.

[0607] If resource allocation scheme 1 for SL-PRS transmission is configured, the MAC entity shall:

[0608] 1> If aperiodic SL-PRS is triggered:

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

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

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

[0612] The MAC entity shall:

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

[0614] 2> If due to logical channel prioritization, UL-SCH resources are available for new transmissions and these UL-SCH resources Adaptable SL-PRS Resource Request MAC CE plus its sub-header:

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

[0616] 2> Otherwise:

[0617] 3 >Trigger a scheduling request for the SL-PRS RESOURCE REQUEST MAC CE as specified in clause 5.4.4.

[0618] When a MAC PDU is transmitted and this PDU contains a SL-PRS resource request MAC CE, the SL-PRS resource request shall be cancelled. MACCE.

[0619] Editor's Note: FFS is used to cancel other conditions of MAC CE.

[0620] 5.22.2 SL-SCH Data and SL-PRS take over

[0621] 5.22.2.1 SCI reception

[0622] The SCI may indicate whether there is a transmission on the SL-SCH and provide related HARQ information. SCI can also indicate whether SL-PRS transmission exists. SL-SCH transmission with or without corresponding SL-PRS on the SL-PRS shared resource pool The SCI consists of two parts: level 1 SCI on PSCCH and level 2 SCI on PSSCH, as specified in clause 8.1 of TS 38.214 [7]. The SCI for SL-PRS transmission on the SL-PRS dedicated resource pool consists of a single part on the PSCCH, such as TS Specified in 38.212[9].

[0623] The MAC entity shall:

[0624] 1> For each PSCCH duration during which the MAC entity monitors the PSCCH:

[0625] 2> If level 1 SCI has been received on PSCCH:

[0626] 3> determining a set of PSSCH durations in which the received portion of the SCI is used for reception of level 2 SCI and transport blocks;

[0627] 3> If a Level 2 SCI has been received on PSSCH for this PSSCH duration:

[0628] 4 >Store SCI as a block with the same and SL-PRS (if available) and an SCI valid for the PSSCH duration corresponding to the transmission of the associated HARQ information and QoS information;

[0629] 2> Otherwise, if SCI has been received on PSCCH reception on the SL-PRS dedicated resource pool for SL-PRS transmission:

[0630] ●3> Determine the SL-PRS transmission timing corresponding to the SCI;

[0631] The corresponding SL-PRS on the SL-PRS dedicated resource pool transmits information.

[0632] 1> For each PSSCH duration for which the MAC entity has a valid SCI:

[0633] 2 >Deliver the SCI and associated sidelink transmission information to the sidelink HARQ entity.

[0634] 1> For each SL-PRS transmission opportunity where the MAC entity has a valid SCI:

[0635] 2 >As in clause 5.22.2.2.2, for SL-

[0636] PRS, and as in clause 5.22.2.x, for SL-

[0637] PRS, performs SL-PRS reception according to the SL-PRS transmission information in the SCI.

[0638] …

[0639] 5.22.2.2.2 Sidelink Process

[0640] For each PSSCH duration in which a transmission occurs for the sidelink process, one TB and associated HARQ information are received from the sidelink HARQ entity.

[0641] For each TB received and SL-PRS (if available) , and the associated sidelink transmission information, the sidelink process shall:

[0642] 1> If this is a new transmission:

[0643] 2>Try to decode the received data.

[0644] 1> Otherwise, if this is a retransmission:

[0645] 2> If this TB of data has not been successfully decoded:

[0646] 3> Instructs the physical layer to combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data.

[0647] 1> if the data that the MAC entity attempted to decode was successfully decoded for this TB; or

[0648] 1> If data for this TB was previously successfully decoded:

[0649] 2> If this is the first successful decode for this TB of data:

[0650] 3> If this TB is associated to unicast and the DST field of the decoded MAC PDU subheader is equal to the 8 MSBs of any of the UE's source layer 2 IDs, with the 16 LSBs equal to the destination ID in the corresponding SCI:

[0651] 4> if the SRC field of the decoded MAC PDU subheader is equal to the 16 MSBs of any of the UE's destination Layer 2 IDs, of which the 8 LSBs are equal to the source ID in the corresponding SCI; or

[0652] 4> If this TB corresponds to a logical channel with LCID equal to 0 or 1 and is determined to be the first TB:

[0653] 5 >Deliver the decoded MAC PDU to the decomposition and demultiplexing entity.

[0654] 5> If the sidelink transmission information in the SCI contains a field for SL-PRS reception:

[0655] 6 >Instructs the physical layer to perform SL-PRS reception.

[0656] 3> If this TB is associated with multicast or broadcast:

[0657] 4> if the DST field of the decoded MAC PDU subheader is equal to the 8 MSBs of any of the UE's destination Layer 2 IDs, where the 16 LSBs are equal to the destination ID in the corresponding SCI; or

[0658] 4> If this TB corresponds to a logical channel with LCID equal to 58, and the DST field of the decoded MAC PDU subheader is equal to the 8 MSBs of any of the UE's source layer 2 IDs, with the 16 LSBs equal to the destination ID in the corresponding SCI:

[0659] 5 >Deliver the decoded MAC PDU to the decomposition and demultiplexing entity.

[0660] 5> If the sidelink transmission information in the SCI contains a field for SL-PRS reception:

[0661] 6>Instruct the physical layer to perform SL-PRS reception.

[0662] NOTE: Whether a TB is the first TB may be determined based on the source layer 2ID and destination layer 2ID pair.

[0663] 2> The side link process is considered not to be occupied.

[0664] 1> Otherwise:

[0665] 2> Instruct the physical layer to replace the data in the soft buffer for this TB with the data that the MAC entity is attempting to decode.

[0666] …

[0667] Editor's Note: FFS determines how to generate PFSCH when SL-PRS is transmitted on a shared resource pool.

[0668] 5.22.2.x SL-PRS reception on SL-PRS dedicated resource pool For each When transmitting SL-PRS, the MAC entity shall:

[0669] 1> If this SL-PRS transmission is associated with unicast:

[0670] 2> If the destination ID in the corresponding SCI is equal to the source ID of the UE; and

[0671] 2> If [12bitSourceID] is configured and the source ID in the corresponding SCI is equal to 12 digits of the UE's destination ID [Most / Least Significant Bit], or if [24bitSourceID] is configured and the source ID in the corresponding SCI is equal to the destination ID of the UE Location ID:

[0672] 3> Instruct the physical layer to perform SL-PRS reception at the SL-PRS transmission opportunity.

[0673] 1> Otherwise, if this SL-PRS transmission is associated with broadcast or multicast:

[0674] 2> If the destination ID in the corresponding SCI is equal to the destination ID of the UE

[0675] 3> Instruct the physical layer to perform SL-PRS reception at the SL-PRS transmission opportunity.

[0676] …

[0677] ==========================Next Change============================

[0678] 6.1.3.xx SL-PRS Resource Request MAC CE

[0679] The SL-PRS Resource Request MAC CE consists of a MAC sub-tag with [eLCID / LCID] as specified in Table 6.2.1-1b. Header identifier. It has the following fields:

[0680] - Destination Layer 2 ID: The destination index field identifies the destination. The length of this field is 5 bits. The value is set to a pair The SL destination identifier should be associated to the same destination as reported in [ffs_RRCConfiguredList] (if present). The value is the SL destination index in [ffs_RRCConfiguredList] as specified in TS38.331[5]. The values ​​are indexed in the same ascending order as the IDs, starting with 0. When multiple lists are reported, the values ​​are in the same order as The same order presented in the SidelinkUEInformaitonNR message is indexed sequentially across all lists;

[0681] - Priority: The priority of the SL-PRS that the UE wants to transmit.

[0682] =========================Next Change=============================

[0683] *************************End of Quote [5]*******************************

[0684] In RAN1#112bis ([6] RAN1 Chairman's Notes of 3GPP TSG RAN WG1#112bis), there are some agreements on sidelink positioning.

[0685] ************************** Quote [6] starts **********************************

[0686] protocol

[0687] ●SL PRS resources refer to the time-frequency resources within the time slot of the dedicated SL PRS resource pool used for SL PRS transmission.

[0688] ○FFS: For shared resource pools

[0689] ●The characteristics associated with SL PRS resources include at least:

[0690] ○SL PRS resource ID,

[0691] ○ SL PRS comb offset and associated SL PRS comb size (N),

[0692] ○SL PRS start symbol and the number of SL PRS symbols (M),

[0693] ○SL PRS frequency domain allocation,

[0694] ○ Note: Additional parameters may be included when marked with / .

[0695] ○FFS: other time domain aspects (if any)

[0696] ● SL PRS resources are identified by a SL PRS resource ID that is unique within a time slot of a dedicated SL PRS resource pool.

[0697] NOTE 1: The above does not imply that all these parameters need to be transmitted / (pre-)configured

[0698] protocol

[0699] For SL-PRS transmission, a dedicated resource pool or a shared resource pool or both may be (pre-)configured in a unique SLBWP of a carrier.

[0700] • A UE may be (pre-)configured with one or more dedicated SL resource pools.

[0701] • A UE may be (pre-)configured with one or more shared SL resource pools.

[0702] protocol

[0703] Regarding SCI signaling in the shared resource pool, in addition to SL PRS transmission, the UE also transmits

[0704] ● Option 1: SCI1-A and Level 2 SCI formats for SL-PRS indication

[0705] ○FFS: Contains details of new or existing Level 2 SCI

[0706] protocol

[0707] In scheme 2, regarding the triggering of SL-PRS,

[0708] ● Support SL-PRS transmission triggered by the UE's own higher layers at the physical layer

[0709] ● Working assumption: UE-A is supported to request UE-B to transmit SL-PRS via lower layer signaling sent by UE-A.

[0710] o SL-1 is transmitted by UE-B's own higher layers in response to a lower layer request from UE-A

[0711] PRS

[0712] ○FFS: Lower layer signaling corresponds to SCI, MAC-CE or SL-PRS

[0713] *************************End of Quote [6]****************************

[0714] In RAN1#113 ([7] RAN1 Chairman's Notes of 3GPP TSG RAN WG1#113), there are some agreements on sidelink positioning.

[0715] *************************Quote [7] begins****************************

[0716] protocol

[0717] For a shared resource pool, the SL PRS bandwidth is the same as the bandwidth indicated for the PSSCH.

[0718] protocol

[0719] For shared resource pools

[0720] ●SL PRS resources refer to the time-frequency resources used for SL PRS transmission within a time slot.

[0721] The characteristics associated with the SL PRS resources in the time slots of the shared resource pool include at least:

[0722] ○SL PRS resource ID,

[0723] ○ SL PRS comb offset and associated SL PRS comb size (N),

[0724] ○SL PRS start symbol and the number of SL PRS symbols (M),

[0725] ○SL PRS frequency domain allocation

[0726] -SL PRS frequency domain allocation is not used to identify a unique SL PRS resource ID

[0727] ● SL PRS resources are identified by a combination of SL PRS resource ID and SL PRS frequency domain allocation. This combination is unique within a time slot of the shared resource pool.

[0728] NOTE 1: The above does not imply that all these parameters need to be transmitted / (pre-)configured

[0729] protocol

[0730] PSSCH is not included in the dedicated resource pool for SL positioning.

[0731] protocol

[0732] In a shared resource pool,

[0733] ● Regarding PSCCH and SL-PRS multiplexing, support for the previous protocol alternative B.1. (i.e., only TDMing is supported)

[0734] protocol

[0735] In a shared resource pool, the SL-PRS, the associated PSCCH, and the PSSCH scheduled by the PSCCH are included in the same time slot:

[0736] ● Regarding PSSCH and SL-PRS multiplexing, for the agreed comb sizes 1, 2, 4, only TDMing is supported

[0737] protocol

[0738] In a shared resource pool, the SL-PRS, the associated PSCCH, and the PSSCH scheduled by the PSCCH are included in the same time slot:

[0739] ●PSSCH is used for the 2nd SCI and SL-SCH

[0740] ○ Note: The UE may have no data available for transmission. It is up to RAN2 to define the provisioning support for this case.

[0741] **************************End of Quote [7]********************************

[0742] In RAN1#114 ([8] RAN1 Chairman's Notes of 3GPP TSG RAN WG1#114), there are some agreements on sidelink positioning.

[0743] ************************** Quote [8] Start **********************************

[0744] protocol

[0745] In a shared resource pool, when PSSCH and SL-PRS are multiplexed in the same time slot, they share the same source ID, destination ID, and broadcast type fields.

[0746] protocol

[0747] In a shared resource pool,

[0748] To indicate SCI format 2-D, the reserved state of the "Level 2 SCI Format" field (code point "11") in SCI format 1-A is used

[0749] protocol

[0750] In the shared resource pool, the fields in the SCI format 2-D include the following fields:

[0751] ●SL PRS resource information indication of the current time slot - upper limit (log2 (# SL-PRS resources (pre-) configured in the resource pool) bits)

[0752] SL PRS request - 0 or 1 bit

[0753] ●Embedded SCI format - [X] bit

[0754] o If the "Embedded SCI Format" field is set to [0], then the SCI 2-A field with necessary padding is included

[0755] ○ If the "Embedded SCI Format" field is set to [1], then the SCI 2-B field is included

[0756] **************************End of quote [8]********************************

[0757] In RAN1#114bis ([9] RAN1 Chairman's Notes of 3GPP TSG RAN WG1#114bis), there are some agreements on sidelink positioning.

[0758] ************************** Quote [9] Start ********************************** 9 9.4.1 9.4.2 9.4.3

[0763] protocol

[0764] The following working assumptions from RAN1#114 are confirmed with the following updates:

[0765] ○For shared resource pools,

[0766] ■ Explicit (pre-) configuration of SL PRS resources in the time slots applicable to the indicated frequency domain allocation includes:

[0767] ●SL PRS resource ID, (M,N) mode, comb offset.

[0768] ■ For a given value of 'M', the SL PRS resource corresponds to the last 'M' consecutive SL symbols available for SL PRS in the slot, i.e., considering the PSSCH DMRS, , CSI-RS, PSFCH, gap symbol, AGC symbol, PSCCH multiplexing

[0769] protocol

[0770] Regarding the dedicated resource pool used for positioning, it is recommended that editors adjust the terminology used to:

[0771] ● "Dedicated SL PRS Resource Pool" as defined in 38.214, as follows:

[0772] o The side link resource pool that can be used for transmission of SL PRS but not for transmission of PSSCH will be referred to as a dedicated SLPRS resource pool.

[0773] protocol

[0774] Regarding the shared resource pool used for positioning, it is recommended that editors adjust the terminology used to:

[0775] The “shared SL PRS resource pool” as defined in 38.214 is as follows:

[0776] The side link resource pool that can be used for transmission of both SL PRS and PSSCH will be referred to as a shared SL PRS resource pool.

[0777] For the New Radio (NR) version 16 / 17 sidelink design, the sidelink timeslot can be used for the Physical Sidelink Broadcast Channel (PSBCH) or the Physical Sidelink Control Channel (PSCCH) / Physical Sidelink Shared Channel (PSSCH) / Physical Sidelink Feedback Channel (PSFCH) transmission / reception. PSBCH is time division multiplexed (TDM) from PSCCH / PSSCH / PSFCH at the timeslot level. This means that the sidelink timeslots other than the timeslots used for PSBCH can be used for PSCCH / PSSCH / PSFCH transmission / reception. In addition, the concept of the sidelink resource pool for sidelink communication is used for PSCCH / PSSCH and / or PSFCH transmission / reception. The sidelink (communication) resource pool will include a set of sidelink timeslots (except at least the timeslots used for PSBCH) and a set of frequency resources. Different side link (communication) resource pools can perform TDM and / or frequency division multiplexing (FDM). More specifically, the PSCCH in one side link (communication) resource pool can only schedule the PSSCH resources in the same side link (communication) resource pool. The PSCCH in one side link (communication) resource pool cannot schedule the PSSCH resources in another side link (communication) resource pool. For PSCCH / PSSCH, the associated PSFCH is in the same side link (communication) resource pool, not in different side link (communication) resource pools.

[0778] A side link (communication) resource pool will include multiple subchannels in the frequency domain, where the subchannel includes multiple adjacent physical resource blocks (PRBs) in the frequency domain. A PRB includes multiple resource elements (REs), for example, a PRB consists of 12 REs. The configuration of the side link resource pool will indicate the number of PRBs for each subchannel in the corresponding side link resource pool. Subchannel-based resource allocation in the frequency domain is supported for PSSCH. For PSSCH resources scheduled by PSCCH in the same side link time slot, a fixed relationship between PSCCH and PSSCH resources is specified, which means that PSCCH will be located in the lowest (indexed) subchannel of the scheduled PSSCH resources. For scheduled PSSCH resources in different time slots, the starting frequency position of the scheduled PSSCH resources will be scheduled / indicated by the side link control information instead of a fixed relationship.

[0779] In the current NR version 16 / 17 sidelink design, one sidelink control information (Sidelink Control Information, SCI) may indicate up to three PSSCH resources via frequency resource assignment and / or time resource assignment in the SCI. The SCI may include level 1 SCI and level 2 SCI. Level 1 SCI may be transmitted via PSCCH. Level 2 SCI may be transmitted via multiplexing with scheduled PSSCH resources in the same sidelink time slot, such as the first PSSCH resource. In other words, the SCI may schedule up to two PSSCH resources, such as the second PSSCH resource and / or the third PSSCH resource, in a later sidelink time slot. The up to three PSSCH resources are in different time slots in the sidelink (communication) resource pool. The up to three PSSCH resources are within 32 consecutive time slots in the sidelink resource pool. Up to three PSSCH resources scheduled by SCI are utilized / associated with the same sidelink data packet (e.g., the same Transport Block (TB) or the same Medium Access Control (MAC) Protocol Data Unit (PDU)). It should be noted that independent PSCCH / SCI is not supported in the NR sidelink, which means that for each PSSCH transmission in a timeslot, there will be a corresponding PSCCH / SCI transmission in the same timeslot, and vice versa.

[0780] In addition, a transmitting (TX) user equipment (UE) may transmit via multiple PSSCHs (eg, Figure 5The TX UE may transmit SCI 1 in time slot n1 for indicating / scheduling PSSCH 1 to 3. The TX UE may transmit SCI 2 in time slot n2 for indicating / scheduling PSSCH 2 to 4. The TX UE may transmit SCI 3 in time slot n3 for indicating / scheduling PSSCH 3 to 5. The TX UE may transmit SCI 4 in time slot n4 for indicating / scheduling PSSCH 4 to 6. The TX UE may transmit SCI 5 in time slot n5 for indicating / scheduling PSSCH 5 to 6. The TX UE may transmit SCI 6 in time slot n6 for indicating / scheduling PSSCH 6. For the same sidelink data packet, the TX UE may indicate / set SCI 1-6 to / as the same Hybrid Automatic Repeat Request (HARQ) process number, the same New Data Indicator (NDI) value, the same (Layer 1) Source Identifier (ID), the same (Layer 1) Destination ID, and the same broadcast type.

[0781] In the current NR Release 16 / 17 sidelink design, two sidelink resource allocation modes are defined for NR sidelink communications:

[0782] - Mode 1 is that the base station / network node may schedule sidelink resources used by the UE for sidelink transmission.

[0783] - Mode 2 is that the UE determines (ie, the base station / network node does not schedule) the sidelink transmission resources within the sidelink resources configured by the base station / network node or the pre-configured sidelink resources.

[0784] For UE (autonomous) selection modes, such as NR sidelink resource allocation mode 2, since the transmission resources are not scheduled via the network node, the UE may need to perform sensing before selecting resources for transmission (e.g., sensing-based transmission) to avoid resource conflicts and interference with other UEs (especially UEs using the NR sidelink). Full sensing is supported from the NR Rel-16 sidelink, while partial sensing is supported from the NR Rel-17 sidelink. Based on the results of the sensing procedure, the UE may determine the valid / identified resource set. The valid / identified resource set may be reported to higher layers (of the UE). The UE may (randomly) select one or more valid / identified resources from the valid / identified resource set to perform sidelink transmission from the UE. The sidelink transmission from the UE may be a PSCCH and / or PSSCH transmission. As Figure 5As shown in , the TX UE may (randomly) select 6 valid / identified resources to perform PSSCH 1-6 transmissions for transmitting the same sidelink data packet.

[0785] For network scheduling modes, such as NR sidelink resource allocation mode 1, dynamic grant, configured grant type 1, and configured grant type 2 are supported in [2] 3GPP TS 38.214 V18.0.0. With respect to dynamic grant, a network node may transmit a sidelink (SL) grant to a TX UE on a Uu interface, such as a downlink control information (DCI) format 3_0 scrambled by an SL-Radio Network Temporary Identifier (RNTI) for scheduling up to three PSSCH resources (for the same sidelink data packet). The sidelink grant also includes a "resource pool index" for indicating a sidelink (communication) resource pool, wherein the scheduled up to three PSCCH / PSSCH resources are within the indicated sidelink (communication) resource pool. In response to the received sidelink grant, the TX UE may perform PSCCH and PSSCH transmissions on a PC5 interface for the sidelink data packet. As Figure 5 As shown in , the TX UE may receive a first side link grant indicating three resources for performing PSSCH 1-3 transmission for transmitting the same side link data packet. The TX UE may receive a second side link grant indicating another three resources for performing PSSCH 4-6 transmission for transmitting the same side link data packet. The network may indicate / set the same SL HARQ process number and the same NDI value in the first side link grant and the second side link grant, so the TX UE may know that the first side link grant and the second side link grant are for the same side link data packet.

[0786] Uu interface means a wireless interface for communication between a network and a UE. PC5 interface means a wireless interface for communication (directly) between UEs / devices.

[0787] In NR Release 18, new reference signals for SL positioning / ranging are introduced, which are called SL positioning reference signals (Positioning Reference Signal, PRS). SL PRS (or SL-PRS) measurements can be used for positioning / ranging solutions, such as SL round trip time (RTT), SL angle of arrival (AoA), SL time difference of arrival (TDOA), and SL angle of departure (AoD). To support time-based positioning methods, a larger bandwidth for SL PRS may be required for higher accuracy positioning. The required bandwidth for SL PRS is likely to be 10 MHz, 20 MHz, or even higher, especially in higher frequency bands.

[0788] In addition, given the large bandwidth requirement of a given SL PRS, a comb-like-N SL PRS design can be supported to provide more available SL PRS resources, and the configured / adjusted number of symbols can be supported as one SL PRS occasion. Potential candidate values for N can be 1, 2, 4, 6, and given M symbols and comb-like-N, there are at least some possible SL PRS mode designs:

[0789] - Fully interleaved SL PRS mode, M = N, and at each symbol, a different RE offset is used.

[0790] - Partially interleaved SL PRS mode, M < N, and at each symbol, a different RE offset is used.

[0791] - Non-interleaved SL PRS mode, N > 1, and at each symbol, the same RE offset is used.

[0792] Preferably, in some embodiments, for a comb-like-N SL PRS design / structure, the possible frequency / comb offset can be from 0 to (N - 1).

[0793] Regarding SL PRS resources / transmission, there are two sidelink resource pools:

[0794] Dedicated SL PRS resource pool and shared SL PRS resource pool (shared with sidelink communication).

[0795] In the dedicated SL PRS pool, there are no PSSCH / PSFCH resources. The TX UE can transmit a PSCCH carrying SCI format 1-B for scheduling / allocating SL PRS resources / transmission within the same time slot.

[0796] In the shared SL PRS resource pool, SL PRS transmissions may be multiplexed with PSSCH resources. The TX UE may transmit PSCCH carrying SCI format 1-A and also transmit level 2 SCI, e.g., SCI format 2-D, for scheduling / allocating both SL PRS resources / transmissions and PSSCH transmissions in the same slot. When PSSCH and SL PRS are multiplexed in the same slot, they shall share the same source ID, destination ID, broadcast type fields.

[0797] For SL PRS resource allocation, Scheme / Mode 1 and Scheme / Mode 2 are introduced.

[0798] - Scheme / Mode 1: Network-centric operation SL PRS resource allocation (e.g. similar to legacy NR Mode 1 for PSSCH).

[0799] --Network nodes (e.g., next generation Node B (gNB), Location Management Function (LMF), gNB, and LMF) allocate resources for SL PRS.

[0800] - Scheme / Mode 2: TX UE autonomous SL PRS resource allocation (e.g. similar to legacy NR Mode 2 for PSSCH).

[0801] --At least one of the UEs participating in the sidelink positioning operation is allocated resources for the SL PRS.

[0802] According to RAN1#112bis ([6] RAN1 Chairman's Notes of 3GPP TSG RAN WG1) and 114bis ([9] RAN1 Chairman's Notes of 3GPP TSG RAN WG1), it supports UE-A to request UE-B to transmit SL PRS via lower layer signaling sent by UE-A, where the lower layer signaling sent by UE-A is SCI with the SL PRS request field set to 1, such as SCI format 1-B or SCI format 2-D. When UE-B receives SCI format 1-B or 2-D with the SL PRS request field set to 1, UE-B will report this request for SL PRS transmission to the higher layer of UE-B. Subsequently, the higher layer of UE-B can trigger the lower layer of UE-B to transmit SLPRS. In addition, for the shared SL PRS resource pool, the SL PRS resources in the time slot are identified by a combination of the SL PRS resource ID and the SL PRS frequency domain allocation. The SL PRS frequency domain allocation is equal to the multiplexed PSSCH frequency domain allocation. The SL PRS resource ID is associated with a (M, N) pattern and comb offset based on the (pre-)configuration of the SL PRS resources in / for a timeslot.

[0803] According to the draft CR of TS 38.321 cited below ([5] R2-2312264), it appears that in a shared SL PRS resource pool, SL PRS transmissions should be multiplexed from an initial PSSCH transmission, and then the same SL PRS transmission may be multiplexed in subsequent PSSCH retransmissions. Figure 5 As shown in , if the TX UE wants to multiplex the SL PRS transmission with the PSSCH transmission, the TX UE should start multiplexing the SL PRS transmission with the PSSCH 1 transmission. Once the TX UE multiplexes the SL PRS transmission with PSSCH 1, the TX UE may continue to multiplex the SL PRS transmission with subsequent PSSCH retransmissions (i.e., PSSCH 2 to 6). However, if the TX UE triggers or is triggered to transmit the SL PRS at a timing later than time slot n1, the TX UE cannot multiplex the SL PRS transmission in any of the PSSCH retransmissions, even if they are associated with the same source ID, destination ID, broadcast type. Such restrictions will cause delays in SL PRS transmissions.

[0804] Secondly, when PSSCH and SL PRS transmissions are multiplexed in the same time slot, the SL PRS resource ID is set in / from the initial PSSCH transmission. There is no chance to reset the SL PRS resource ID in a PSSCH retransmission. Given the SL PRS resource ID, the SL PRS transmission is associated with an (M,N) pattern and a comb offset. However, in some cases, the available symbols for PSSCH and SL PRS will change in different time slots. For example, if Figure 6 As shown in , in time slot A without PSFCH resources, there can be up to 4 symbols for SL PRS transmission (M≤4); and in time slot B with PSFCH resources, there can be up to 3 symbols for SL PRS transmission (M≤3). This is because SL PRS transmission cannot be performed in symbols with PSSCH Demodulation Reference Signal (DMRS) (i.e., in Figure 6 In these cases, it is unclear how to handle the multiplexing of PSSCH and SL PRS transmissions.

[0805] Third, it seems that in a shared SL PRS resource pool, the SL PRS request field set to request / 1 should fromThe initial PSSCH transmission is set. There is no chance to reset the SL PRS request field in PSSCH retransmissions. It may result in that if the TXUE requests the paired UE to transmit SL PRS in the initial PSSCH transmission, the TX UE will continuously request the paired UE to transmit SL PRS in subsequent PSSCH retransmissions. Such continuous requests may cause unnecessary multiple SLPRS transmissions from the paired UE. If the TX UE does not request the paired UE to transmit SL PRS in the initial PSSCH transmission, the TX UE will not be able to request the paired UE to transmit SL PRS in subsequent PSSCH retransmissions. It will cause a delay in requesting SL PRS from the paired UE.

[0806] Fourth, in the current TS 38.212 ([3] 3GPP TS 38.212 V18.0.0), the SL PRS request field is present in SCI format 1-B for the dedicated SL PRS resource pool and in SCI format 2-D for the shared SL PRS resource pool. However, since SCI format 2-D schedules both SL PRS and PSSCH transmissions, this means that if the TX UE wants to request the paired UE to transmit SL PRS, i.e., sets the SL PRS request field to request / 1, the TX UE needs to first transmit the SL PRS scheduled by SCI format 2-D, even if the TX UE does not trigger such SL PRS transmission to the paired UE.

[0807] -----------------------------------------Begin Quote--------------------------------------

[0808] for Not on the SL-PRS dedicated resource pool For each sidelink grant, the sidelink HARQ entity shall:

[0809] 1> if the MAC entity determines that the sidelink is granted for the initial transmission, as specified in clause 5.22.1.1; or

[0810] 1> if the sidelink grant is a configured sidelink grant and no MAC PDU is obtained in the sl-PeriodCG of the configured sidelink grant; or

[0811] 1> If the sidelink grant is a dynamic sidelink grant or a selected sidelink grant and no MAC PDU was obtained in the previous sidelink grant when the PSCCH duration and level 2 SCI on PSSCH of the previous sidelink grant are not within the SL DRX active time with data to be sent as specified in clause 5.28.3 at either destination:

[0812] Note 1: Vacant.

[0813] 2> (re)associate the sidelink process to this grant, and for the associated sidelink process:

[0814] 2> If all PSCCH durations and PSSCH durations for initial transmission of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0815] 3> Ignore sidelink grant.

[0816] NOTE 1A: The sidelink HARQ entity shall associate the selected sidelink grant to the sidelink process determined by the MAC entity.

[0817] 2> Otherwise:

[0818] 3> Get the MAC PDU to be transmitted from the multiplexing and combining entity (if any);

[0819] 3> If the MAC PDU to be transmitted has been obtained:

[0820] 4> If HARQ process ID has been set for sidelink grant:

[0821] 5> (re)associate the HARQ process ID corresponding to the sidelink grant to the sidelink process.

[0822] NOTE 1a: There is a one-to-one mapping between HARQ process IDs and sidelink processes in a MAC entity configured to use sidelink resource allocation mode 1.

[0823] 4> Determine the sidelink transmission information of the TB for the source and destination pair of the MAC PDU as follows:

[0824] 5> Set the source layer 1 ID to the 8 least significant bits (LSB) of the source layer 2 ID of the MAC PDU;

[0825] 5> Set the destination layer 1 ID to the 16 LSBs of the destination layer 2 ID of the MAC PDU;

[0826] 5> (re)associate the sidelink process to the sidelink process ID;

[0827] …

[0828] 5>Set the redundancy version to the selected value.

[0829] 5> If the sidelink grant is the same as from the higher layer to trigger the SL- The request transmitted by PRS is associated with:

[0830] 6> Set SL-PRS Request to Request.

[0831] 5> Set the SL-PRS Resource ID to [value of field] in the sidelink transmission information (if available).

[0832] Editor's Note: How FFS determines the SL-PRS resource ID and its impact on MAC.

[0833] 4> TB's MAC PDU, SL-PRS (if available), sidelink grant and sidelink transmit information are delivered to the associated sidelink process;

[0834] 4> Instructs the associated sidelink process to trigger a new transmission.

[0835] 3> Otherwise:

[0836] 4>Flush the HARQ buffer of the associated side link process.

[0837] 1> Otherwise (i.e., retransmit):

[0838] 2> if the HARQ process ID corresponding to the sidelink grant received on the Physical Downlink Control Channel (PDCCH), the configured sidelink grant or the selected sidelink grant is associated to a sidelink process whose HARQ buffer is empty; or

[0839] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH is not associated to any sidelink process; or

[0840] 2> If the PSCCH duration and PSSCH duration for one or more retransmissions of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0841] 3> Ignore sidelink grant.

[0842] 2> Otherwise:

[0843] 3> Identify the side link process associated with this grant, and for the associated side link process:

[0844] 4> MAC PDU and the SL-PRS (if available) The sidelink grant is delivered to the associated sidelink process;

[0845] 4> Instruct the associated sidelink process to trigger retransmission.

[0846] ------------------------------------------End of quote-------------------------------------

[0847] To address these issues, various concepts, mechanisms, methods, aspects and / or embodiments are provided in the following content.

[0848] Concept A

[0849] Concept A allows the TX UE to start multiplexing the SL PRS transmission with the first PSSCH retransmission in the first time slot. The TX UE may not multiplex the SL PRS transmission with the initial / new PSSCH transmission. The TX UE may perform the initial / new PSSCH transmission before the TX UE performs the first PSSCH retransmission. The initial / new PSSCH transmission and the first PSSCH retransmission are used to transmit the same sidelink data packet or MAC PDU.

[0850] Preferably, in some embodiments, the TX UE may trigger an SLPRS transmission or be triggered for an SL PRS transmission in a first timing later than an initial / new PSSCH transmission. Preferably, in some embodiments, the trigger may occur before the timing of sending the initial / new PSSCH transmission, and there is not enough time or enough space / resources (e.g., some Quality of Service (QoS) / decoding requirements of the initial / first PSSCH transmission) to multiplex the SL PRS into the initial / new PSSCH transmission.

[0851] Preferably, in certain embodiments, Concept A also allows that the TX UE may not multiplex the SL PRS transmission with the second PSSCH retransmission in the second time slot, wherein the second PSSCH retransmission is performed after the first PSSCH retransmission, and wherein the second PSSCH retransmission and the first PSSCH retransmission are used to transmit the same sidelink data packet or MAC PDU. Preferably, in certain embodiments, the TX UE may cancel the triggering of the SL PRS transmission in the second timing before the second PSSCH retransmission or the second time slot. Preferably, in certain embodiments, the TX UE may cancel the triggering of the SL PRS transmission in the second timing after the first PSSCH retransmission. Preferably, in certain embodiments, in response to the SL PRS transmission multiplexed with the first PSSCH retransmission, the TX UE may cancel the triggering of the SL PRS transmission. Preferably, in certain embodiments, in response to the TX UE performing the SL PRS transmission for a first number of times, the TX UE may cancel the triggering of the SL PRS transmission. The first number may be specified or (pre) configured (e.g., configured in a sidelink resource pool configuration or an SL PRS related configuration), or provided by a higher layer (e.g., any one of a MAC layer, a Radio Resource Control (RRC) layer, a Sidelink Positioning Protocol (SLPP) layer, or a positioning / ranging application layer). Preferably, in some embodiments, the TX UE may perform a first number of PSSCH transmissions multiplexed with an SL PRS transmission. The first number of PSSCH transmissions includes a first PSSCH transmission. Preferably, in some embodiments, the TX UE may perform the first number of PSSCH transmissions before a second PSSCH retransmission. Preferably or alternatively, in some embodiments, the second PSSCH retransmission may not be multiplexed with the SL PRS transmission, for example, due to insufficient symbols for the SL PRS transmission in the second PSSCH retransmission, or due to the presence of PSFCH resources in the second time slot.

[0852] Preferably, in certain embodiments, the SL PRS transmission and the first PSSCH retransmission are associated with the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID, and the same broadcast type.

[0853] Preferably, in some embodiments, the first PSSCH retransmission and the initial / new PSSCH transmission are associated with the same HARQ process number, the same NDI value, the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID and the same broadcast type. Preferably, in some embodiments, the first PSSCH retransmission and the second PSSCH retransmission are associated with the same HARQ process number, the same new data indicator (NDI) value, the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID and the same broadcast type. Preferably, in some embodiments, the first PSSCH retransmission, the initial / new PSSCH transmission and / or the second PSSCH retransmission are performed by the TX UE in the same side link resource pool.

[0854] For example, Figure 5 As shown in , the TX UE may perform PSSCH 1 and PSSCH 2 transmissions without multiplexing SL PRS transmissions. The TX UE may trigger SL PRS transmission or be triggered for SL PRS transmission in a first timing later than time slot n2 and earlier than time slot n3. In response to the trigger, the TX UE may perform PSSCH 3-5 transmissions with multiplexing SL PRS transmissions. In this case, the first number may be 3. In response to SL PRS transmissions multiplexed in PSSCH 3-5 transmissions, the TX UE may cancel the triggering of SL PRS transmissions. The TX UE may perform PSSCH 6 transmission without multiplexing SL PRS transmissions.

[0855] Preferably or alternatively, in some embodiments, PSSCH 3 to 5 may be associated with the same or different MAC PDUs. In the case of different MAC PDUs, this means that the TX UE may multiplex the SL PRS transmissions corresponding to the same trigger into different MAC PDUs or into different PSSCH transmissions for transmitting different side link data packets or MAC PDUs. The TX UE may (trigger) request more / additional new SL grants (e.g., sending a Scheduling Request (SR) in mode 1 or triggering a MAC CE or selecting a new side link grant in mode 2) for sending / multiplexing the remaining SL PRS transmissions corresponding to the same trigger.

[0856] Preferably, in certain embodiments, based on method / concept A, a text suggestion 1 (bold and underlined) may be provided as follows.

[0857] ========================Text Proposal 1=========================

[0858] for Not on the SL-PRS dedicated resource pool For each sidelink grant, the sidelink HARQ entity shall:

[0859] 1> if the MAC entity determines that the sidelink is granted for the initial transmission, as specified in clause 5.22.1.1; or

[0860] 1> if the sidelink grant is a configured sidelink grant and no MAC PDU is obtained in the sl-PeriodCG of the configured sidelink grant; or

[0861] 1> If the sidelink grant is a dynamic sidelink grant or a selected sidelink grant and no MAC PDU was obtained in the previous sidelink grant when the PSCCH duration and level 2 SCI on PSSCH of the previous sidelink grant are not within the SL DRX active time with data to be sent as specified in clause 5.28.3 at either destination:

[0862] Note 1: Vacant.

[0863] 2> (re)associate the sidelink process to this grant, and for the associated sidelink process:

[0864] 2> If all PSCCH durations and PSSCH durations for initial transmission of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0865] 3> Ignore sidelink grant.

[0866] NOTE 1A: The sidelink HARQ entity shall associate the selected sidelink grant to the sidelink process determined by the MAC entity.

[0867] 2> Otherwise:

[0868] 3> Get the MAC PDU to be transmitted from the multiplexing and combining entity (if any);

[0869] 3> If the MAC PDU to be transmitted has been obtained:

[0870] 4> If HARQ process ID has been set for sidelink grant:

[0871] 5> (re)associate the HARQ process ID corresponding to the sidelink grant to the sidelink process.

[0872] NOTE 1a: There is a one-to-one mapping between HARQ process IDs and sidelink processes in a MAC entity configured to use sidelink resource allocation mode 1.

[0873] 4> Determine the sidelink transmission information of the TB for the source and destination pair of the MAC PDU as follows:

[0874] 5> Set the source layer 1 ID to the 8 LSBs of the source layer 2 ID of the MAC PDU;

[0875] 5> Set the destination layer 1 ID to the 16 LSBs of the destination layer 2 ID of the MAC PDU;

[0876] 5> (re)associate the sidelink process to the sidelink process ID;

[0877] …

[0878] 5>Set the redundancy version to the selected value.

[0879] 5> If the sidelink grant is the same as from the higher layer to trigger the SL- The request transmitted by PRS is associated with:

[0880] 6> Set SL-PRS Request to Request.

[0881] 5> Set the SL-PRS Resource ID to [value of field] in the sidelink transmission information (if available).

[0882] Editor's Note: How FFS determines the SL-PRS resource ID and its impact on MAC.

[0883] 4> TB's MAC PDU, SL-PRS (if available) , sidelink grant and sidelink transmit information delivered to an associated sidelink process;

[0884] 4> Instructs the associated sidelink process to trigger a new transmission.

[0885] 3> Otherwise:

[0886] 4>Flush the HARQ buffer of the associated side link process.

[0887] 1> Otherwise (i.e., retransmit):

[0888] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH, the configured sidelink grant, or the selected sidelink grant is associated to a sidelink process whose HARQ buffer is empty; or

[0889] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH is not associated to any sidelink process; or

[0890] 2> If the PSCCH duration and PSSCH duration for one or more retransmissions of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0891] 3> Ignore sidelink grant.

[0892] 2> Otherwise:

[0893]

[0894] 3> Identify the side link process associated with this grant, and for the associated side link process:

[0895] 4> MAC PDU and SL-PRS (if available) The side link grant is delivered to the associated side link process; (add 1)

[0896] 4> MAC PDU and SL-PRS (if ) The side link grant is delivered to the associated side link process; (Add 2)

[0897] 4> Instruct the associated sidelink process to trigger retransmission.

[0898] =======================End of Text Proposal 1========================

[0899] Concept B

[0900] Concept B is that the TX UE may change the SL PRS resources and / or SL PRS resource IDs in different multiplexed PSSCH transmissions for the same sidelink data packet or MAC PDU.

[0901] In one embodiment, the TX UE may multiplex a first SL PRS transmission associated with a first SL PRS resource ID and a first PSSCH transmission in a first time slot. The TX UE may multiplex a second SL PRS transmission associated with a second SL PRS resource ID and a second PSSCH transmission in a second time slot, wherein the first PSSCH transmission and the second PSSCH transmission are used to transmit the same side link data packet. Concept B is that the first SL PRS resource ID may be different from the second SL PRS resource ID. Preferably, in certain embodiments, the first SL PRS transmission and the second SL PRS transmission may be associated with different numbers of SL PRS symbols, different comb-N structures, or different comb / frequency / RE offsets.

[0902] Preferably, in some embodiments, a first SL PRS resource ID may be associated with a first number of SL PRS symbols, a comb-N1 structure, and a first comb / frequency / RE offset. Preferably, in some embodiments, a second SL PRS resource ID may be associated with a second number of SL PRS symbols, a comb-N2 structure, and a second comb / frequency / RE offset. Preferably, in some embodiments, the first number of SL PRS symbols is different from the second number of SL PRS symbols. Preferably, in some embodiments, N1 is different from N2. Preferably, in some embodiments, the first comb / frequency / RE offset is different from the second comb / frequency / RE offset.

[0903] Preferably, in some embodiments, the second SL PRS transmission may be a retransmission of the first SL PRS transmission. Preferably, in some embodiments, the first SL PRS transmission and the first PSSCH transmission are associated with the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID and the same broadcast type. Preferably, in some embodiments, the second SL PRS transmission and the second PSSCH transmission are associated with the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID and the same broadcast type.

[0904] Preferably, in some embodiments, the first SL PRS transmission and the second SL PRS transmission may be associated with the same SL PRS trigger (eg, triggered from a higher layer). Preferably, in some embodiments, the first SL PRS transmission and the second SL PRS transmission may be associated with the same sidelink positioning service.

[0905] Preferably, in certain embodiments, the TX UE performs the first PSSCH transmission and the second PSSCH transmission in the same side link resource pool (eg, the same shared SL PRS resource pool).

[0906] Preferably, in some embodiments, the first time slot in the side link resource pool does not include a PSFCH symbol / resource / opportunity. Preferably, in some embodiments, in response to the first time slot not having a PSFCH symbol / resource / opportunity, the TX UE may determine a first SL PRS resource ID.

[0907] Preferably, in some embodiments, the second time slot in the side link resource pool includes a PSFCH symbol / resource / opportunity. Preferably, in some embodiments, in response to the second time slot having a PSFCH symbol / resource / opportunity, the TX UE may determine a second SL PRS resource ID.

[0908] Preferably, in certain embodiments, the TX UE may determine different SL PRS resource IDs in response to whether a timeslot includes a PSFCH symbol / resource / opportunity.

[0909] Preferably, in some embodiments, the TX UE may perform multiple PSSCH transmissions for transmitting the same side link data packet. Preferably, in some embodiments, the multiple PSSCH transmissions may include a first PSSCH transmission set in a first time slot set that does not have PSFCH symbols / resources / opportunities in the side link resource pool. If / when the TX UE determines to multiplex the SL PRS transmission with any one of the first PSSCH transmission set, the TX UE determines to multiplex the SL PRS transmission associated with the first SL PRS resource ID. Preferably, in some embodiments, the multiple PSSCH transmissions may include a second PSSCH transmission set in a second time slot set that has PSFCH symbols / resources / opportunities in the side link resource pool. If / when the TX UE determines to multiplex the SLPRS transmission with any one of the second PSSCH transmission set, the TX UE determines to multiplex the SL PRS transmission associated with the second SL PRS resource ID.

[0910] In one embodiment, the TX UE may multiplex a first SL PRS transmission associated with a first SL PRS resource ID and a first PSSCH transmission in a first time slot. The TX UE may not multiplex the SL PRS transmission with a third PSSCH transmission in a third time slot, wherein the first PSSCH transmission and the third PSSCH transmission are used to transmit the same sidelink data packet.

[0911] Preferably, in some embodiments, the third SL PRS transmission may be a retransmission of the first SL PRS transmission. Preferably, in some embodiments, the first SL PRS transmission and the first PSSCH transmission are associated with the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID and the same broadcast type.

[0912] Preferably, in certain embodiments, the TX UE performs the first PSSCH transmission and the third PSSCH transmission in the same side link resource pool (eg, the same shared SL PRS resource pool).

[0913] Preferably, in some embodiments, the first time slot in the side link resource pool does not include a PSFCH symbol / resource / opportunity. Preferably, in some embodiments, in response to the first time slot not having a PSFCH symbol / resource / opportunity, the TX UE may determine a first SL PRS resource ID.

[0914] Preferably, in some embodiments, the third time slot in the side link resource pool includes PSFCH symbols / resources / opportunities. Preferably, in some embodiments, in response to the third time slot having PSFCH symbols / resources / opportunities, the TX UE may determine not to multiplex the SL PRS transmission with the third PSSCH transmission.

[0915] Preferably, in certain embodiments, the TX UE may determine whether to multiplex the SL PRS transmission in response to whether the timeslot includes a PSFCH symbol / resource / opportunity.

[0916] Preferably, in some embodiments, the TX UE may perform multiple PSSCH transmissions for transmitting the same side link data packet. Preferably, in some embodiments, the multiple PSSCH transmissions may include a first PSSCH transmission set in a first time slot set that does not have PSFCH symbols / resources / opportunities in the side link resource pool. If / when the TX UE determines to multiplex the SL PRS transmission with any one of the first PSSCH transmission sets, the TX UE determines to multiplex the SL PRS transmission associated with the first SL PRS resource ID. Preferably, in some embodiments, the multiple PSSCH transmissions may include a third PSSCH transmission set of a third time slot set having PSFCH symbols / resources / opportunities in the side link resource pool. In response to whether the time slot includes PSFCH symbols / resources / opportunities, the TX UE may determine whether to multiplex the SL PRS transmission.

[0917] On the other hand the TX UE may keep the same SL PRS resources and / or SL PRS resource ID in different multiplexed PSSCH transmissions for the same sidelink data packet or MAC PDU. The RX UE shall demultiplex the SL PRS considering or based on the PSFCH occasion and the SL PRS resource ID.

[0918] For any of the embodiments above or herein, a timeslot including / having PSFCH symbols / resources / opportunities may include or mean or replace a timeslot including / having symbols for SL PRS that are less than a threshold. The threshold may be a first number of SL PRS symbols, or a specified or configured value.

[0919] For any of the embodiments above or herein, a time slot not including / having PSFCH symbols / resources / opportunities may include or mean or replace a time slot including / having symbols for SL PRS greater than or equal to a threshold.

[0920] For any of the embodiments above or herein, a time slot including / having PSFCH symbols / resources / opportunities may include or mean or substitute for a time slot including / having symbols for PSSCH that are less than a configured or specified value.

[0921] For any of the embodiments above or herein, a time slot not including / having PSFCH symbols / resources / opportunities may include or mean or replace a time slot including / having symbols for PSSCH greater than a configured or specified value.

[0922] Preferably, in certain embodiments, based on method / concept B, text suggestion 2 (bold and underlined) may be provided as follows.

[0923] ==========================Text Proposal 2===========================

[0924] for Not on the SL-PRS dedicated resource pool For each sidelink grant, the sidelink HARQ entity shall:

[0925] 1> if the MAC entity determines that the sidelink is granted for the initial transmission, as specified in clause 5.22.1.1; or

[0926] 1> if the sidelink grant is a configured sidelink grant and no MAC PDU is obtained in the sl-PeriodCG of the configured sidelink grant; or

[0927] 1> If the sidelink grant is a dynamic sidelink grant or a selected sidelink grant and no MAC PDU was obtained in the previous sidelink grant when the PSCCH duration and level 2 SCI on PSSCH of the previous sidelink grant are not within the SL DRX active time with data to be sent as specified in clause 5.28.3 at either destination:

[0928] Note 1: Vacant.

[0929] 2> (re)associate the sidelink process to this grant, and for the associated sidelink process:

[0930] 2> If all PSCCH durations and PSSCH durations for initial transmission of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0931] 3> Ignore sidelink grant.

[0932] NOTE 1A: The sidelink HARQ entity shall associate the selected sidelink grant to the sidelink process determined by the MAC entity.

[0933] 2> Otherwise:

[0934] 3> Get the MAC PDU to be transmitted from the multiplexing and combining entity (if any);

[0935] 3> If the MAC PDU to be transmitted has been obtained:

[0936] 4> If HARQ process ID has been set for sidelink grant:

[0937] 5> (re)associate the HARQ process ID corresponding to the sidelink grant to the sidelink process.

[0938] NOTE 1a: There is a one-to-one mapping between HARQ process IDs and sidelink processes in a MAC entity configured to use sidelink resource allocation mode 1.

[0939] 4> Determine the sidelink transmission information of the TB for the source and destination pair of the MAC PDU as follows:

[0940] 5> Set the source layer 1ID to the 8 LSBs of the source layer 2ID of the MAC PDU; 5> Set the destination layer 1ID to the 16 LSBs of the destination layer 2ID of the MAC PDU;

[0941] 5> (re)associate the sidelink process to the sidelink process ID;

[0942] …

[0943] 5>Set the redundancy version to the selected value.

[0944] 5> If the sidelink grant is the same as from the higher layer to trigger the SL- The request transmitted by PRS is associated with:

[0945] 6> Set SL-PRS Request to Request.

[0946] 5> Set the SL-PRS Resource ID to [value of field] in the sidelink transmission information (if available).

[0947] Editor's Note: How FFS determines the SL-PRS resource ID and its impact on MAC.

[0948] 4> TB's MAC PDU, SL-PRS (if available), sidelink grant and sidelink transmit information are delivered to the associated sidelink process;

[0949] 4> Instructs the associated sidelink process to trigger a new transmission.

[0950] 3> Otherwise:

[0951] 4>Flush the HARQ buffer of the associated side link process.

[0952] 1> Otherwise (i.e., retransmit):

[0953] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH, the configured sidelink grant, or the selected sidelink grant is associated to a sidelink process whose HARQ buffer is empty; or

[0954] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH is not associated to any sidelink process; or

[0955] 2> If the PSCCH duration and PSSCH duration for one or more retransmissions of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0956] 3> Ignore sidelink grant.

[0957] 2> Otherwise:

[0958] (Add 1)

[0959] (Added 2)

[0960] 3> Identify the side link process associated with this grant, and for the associated side link process:

[0961] 4> MAC PDU and SL-PRS (if available) The side link grant is delivered to the associated side link process; (add 1)

[0962] 4> MAC PDU and SL-PRS (if ) The side link grant is delivered to the associated side link process; (Add 2)

[0963] 4> Instruct the associated sidelink process to trigger retransmission.

[0964]

[0965] =======================End of Text Proposal 2========================

[0966] Concept C

[0967] Concept C is to allow the TX UE to request SL PRS from other UEs / destinations starting in the first SCI that schedules the first PSSCH retransmission in the first time slot. Preferably, in some embodiments, the TX UE may transmit the first SCI and the first PSSCH retransmission to other UEs / destinations in the first time slot. Preferably, in some embodiments, the TX UE may set a field in the first SCI to indicate the SL PRS request, for example, setting the "SL PRS Request" field to Request / 1.

[0968] Preferably, in some embodiments, the TX UE may not request SL PRS from other UEs / destinations via another SCI that schedules the initial / new PSSCH transmission. Before the TX UE performs the first PSSCH retransmission, the TX UE may transmit another SCI and the initial / new PSSCH transmission. The initial / new PSSCH transmission and the first PSSCH retransmission are used to transmit the same sidelink data packet.

[0969] Preferably, in certain embodiments, the TX UE may determine to request a SL PRS from other UEs / destinations in a first timing later than an initial / new PSSCH transmission.

[0970] Preferably, in certain embodiments, Concept C also allows the TX UE to request a SL PRS from other UEs / destinations in a second SCI that does not schedule a second PSSCH retransmission in a second time slot, wherein the second PSSCH retransmission is performed after the first PSSCH retransmission, and wherein the second PSSCH retransmission and the first PSSCH retransmission are used to transmit the same side link data packet. Preferably, in certain embodiments, the TX UE may cancel the SL PRS request in a second timing before the second PSSCH retransmission or the second time slot. Preferably, in certain embodiments, the TX UE may cancel the SL PRS request in a second timing after the first PSSCH retransmission. Preferably, in certain embodiments, the TX UE may cancel the SL PRS request in response to the transmission of the first SCI or the first PSSCH retransmission.

[0971] Preferably, in some embodiments, the first PSSCH retransmission and the initial / new PSSCH transmission are associated with the same HARQ process number, the same NDI value, the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID and the same broadcast type. Preferably, in some embodiments, the first PSSCH retransmission and the second PSSCH retransmission are associated with the same HARQ process number, the same NDI value, the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID and the same broadcast type. Preferably, in some embodiments, the first PSSCH retransmission, the initial / new PSSCH transmission, the second PSSCH retransmission are performed by the TX UE in the same side link resource pool. Preferably, in some embodiments, the side link resource pool is a shared SL PRS resource pool.

[0972] Preferably, in certain embodiments, another SCI may schedule initial / new PSSCH transmissions with SL PRS multiplexing.Another SCI may include SCI format 2-D.

[0973] Preferably or alternatively, in certain embodiments, another SCI may schedule initial / new PSSCH transmission without SL PRS multiplexing.Another SCI may include any of SCI formats 1-A, 2-A, 2-B, 2-C.

[0974] Preferably, in some embodiments, the first SCI may schedule the first PSSCH retransmission and the first SL PRS transmission in the first time slot. Preferably, in some embodiments, the first SCI may include SCI format 2-D. Preferably, in some embodiments, SCI format 2-D may include a "SL PRS request" field. Preferably, in some embodiments, any of SCI formats 1-A, 2-A, 2-B or 2-C may not include the "SL PRS request" field. Preferably, in some embodiments, the first SL PRS transmission and the first PSSCH retransmission are associated with the same (layer 1 or layer 2) source ID, the same (layer 1 or layer 2) destination ID and the same broadcast type.

[0975] Preferably or alternatively, in some embodiments, the first SCI may schedule the first PSSCH retransmission in the first time slot and not schedule the SL PRS transmission. Preferably, in some embodiments, the first SCI may not include / indicate SL PRS resource related information, for example, an SL PRS resource ID indicator. Preferably, in some embodiments, the first SCI may include any one of SCI formats 1-A, 2-A, 2-B, 2-C. Preferably, in some embodiments, if the configuration of the side link resource pool includes SLPRS related configuration, for example, SL PRS resource ID configuration, any one of SCI formats 1-A, 2-A, 2-B or 2-C may include a "SL PRS request" field. Preferably, in some embodiments, if the configuration of the side link resource pool does not include SL PRS related configuration, any one of SCI formats 1-A, 2-A, 2-B or 2-C may not include a "SL PRS request" field. Preferably or alternatively, in some embodiments, the first SCI may include / indicate SL PRS resource related information, for example, an SL PRS resource ID indicator. Preferably, in some embodiments, the first SCI may include an SCI format 2-D. Preferably, in some embodiments, the SCI format 2-D may include a "SL PRS request" field. Preferably, in some embodiments, the SCI format 2-D may indicate that there is no SL PRS transmission in the first time slot. Preferably, in some embodiments, the SCI format 2-D may indicate a specific SL PRS resource ID corresponding to no SL PRS transmission or deactivated SL PRS transmission. Preferably, in some embodiments, the specific SL PRS resource ID may be specified or (pre) configured. Preferably, in some embodiments, one or more fields of the SCI format 2-D may indicate one or more specific values ​​for indicating no SL PRS transmission or deactivated SL PRS transmission.

[0976] For example, Figure 5As shown in , the TX UE may perform PSSCH 1 and PSSCH 2 transmissions when the SCI does not indicate a SL PRS request. The TX UE may determine to request SL PRS from other UEs / destinations in a first timing later than time slot n2 and earlier than time slot n3. The TX UE may perform PSSCH 3 transmission when the SCI indicates a SL PRS request. In response to the transmission of the SCI indicating the SL PRS request, the TX UE may cancel the SL PRS request. The TX UE may perform PSSCH 4-6 transmissions when the SCI does not indicate a SL PRS request.

[0977] Preferably, in certain embodiments, based on method / concept C, text suggestion 3 (bold and underlined) may be provided as follows.

[0978] =========================Text Proposal 3===========================

[0979] for Not on the SL-PRS dedicated resource pool For each sidelink grant, the sidelink HARQ entity shall:

[0980] 1> if the MAC entity determines that the sidelink is granted for the initial transmission, as specified in clause 5.22.1.1; or

[0981] 1> if the sidelink grant is a configured sidelink grant and no MAC PDU is obtained in the sl-PeriodCG of the configured sidelink grant; or

[0982] 1> If the sidelink grant is a dynamic sidelink grant or a selected sidelink grant and no MAC PDU was obtained in the previous sidelink grant when the PSCCH duration and level 2 SCI on PSSCH of the previous sidelink grant are not within the SL DRX active time with data to be sent as specified in clause 5.28.3 at either destination:

[0983] Note 1: Vacant.

[0984] 2> (re)associate the sidelink process to this grant, and for the associated sidelink process:

[0985] 2> If all PSCCH durations and PSSCH durations for initial transmission of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[0986] 3> Ignore sidelink grant.

[0987] NOTE 1A: The sidelink HARQ entity shall associate the selected sidelink grant to the sidelink process determined by the MAC entity.

[0988] 2> Otherwise:

[0989] 3> Get the MAC PDU to be transmitted from the multiplexing and combining entity (if any);

[0990] 3> If the MAC PDU to be transmitted has been obtained:

[0991] 4> If HARQ process ID has been set for sidelink grant:

[0992] 5> (re)associate the HARQ process ID corresponding to the sidelink grant to the sidelink process.

[0993] NOTE 1a: There is a one-to-one mapping between HARQ process IDs and sidelink processes in a MAC entity configured to use sidelink resource allocation mode 1.

[0994] 4> Determine the sidelink transmission information of the TB for the source and destination pair of the MAC PDU as follows:

[0995] 5> Set the source layer 1ID to the 8 LSBs of the source layer 2ID of the MAC PDU; 5> Set the destination layer 1ID to the 16 LSBs of the destination layer 2ID of the MAC PDU;

[0996] 5> (re)associate the sidelink process to the sidelink process ID;

[0997] …

[0998] 5>Set the redundancy version to the selected value.

[0999] 5> If the sidelink grant is the same as from the higher layer to trigger the SL- The request transmitted by PRS is associated with:

[1000] 6> Set SL-PRS Request to Request.

[1001] 5> Set the SL-PRS Resource ID to [value of field] in the sidelink transmission information (if available).

[1002] Editor's Note: How FFS determines the SL-PRS resource ID and its impact on MAC.

[1003] 4> TB's MAC PDU, SL-PRS (if available), sidelink grant and sidelink transmit information are delivered to the associated sidelink process;

[1004] 4> Instructs the associated sidelink process to trigger a new transmission.

[1005] 3> Otherwise:

[1006] 4>Flush the HARQ buffer of the associated side link process.

[1007] 1> Otherwise (i.e., retransmit):

[1008] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH, the configured sidelink grant, or the selected sidelink grant is associated to a sidelink process whose HARQ buffer is empty; or

[1009] 2> if the HARQ process ID corresponding to the sidelink grant received on the PDCCH is not associated to any sidelink process; or

[1010] 2> If the PSCCH duration and PSSCH duration for one or more retransmissions of a MAC PDU for a dynamic sidelink grant or a configured sidelink grant are not within the SL DRX active time with data to be sent at the destination as specified in clause 5.28.3:

[1011] 3> Ignore sidelink grant.

[1012] 2> Otherwise:

[1013]

[1014] 3> Identify the side link process associated with this grant, and for the associated side link process:

[1015] 4> MAC PDU and SL-PRS (if available) The sidelink grant is delivered to the associated sidelink process;

[1016] 4> Instruct the associated sidelink process to trigger retransmission.

[1017] =======================End of Text Proposal 3========================

[1018] Preferably or alternatively, in some embodiments, Concept C may allow the TX UE to start requesting SL PRS from other UEs / destinations in the third SCI that schedules the first SLPRS retransmission in the first time slot. Preferably, in some embodiments, the TX UE may transmit the third SCI and the first SL PRS retransmission to other UEs / destinations in the first time slot. Preferably, in some embodiments, the TX UE may set a field in the third SCI to indicate the SL PRS request, for example, setting the "SL PRS Request" field to Request / 1.

[1019] Preferably, in some embodiments, the TX UE may request SL PRS from other UEs / destinations without another SCI scheduling the initial / new SL PRS transmission. Before the TX UE performs the first SL PRS retransmission, the TX UE may transmit another SCI and the initial / new SL PRS transmission. The initial / new SL PRS transmission and the first SL PRS retransmission are associated with the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID, the same broadcast type, the same priority value and / or the same SL PRS trigger.

[1020] Preferably, in certain embodiments, the TX UE may determine to request the SL PRS from other UEs / destination in a first timing later than the initial / new SL PRS transmission.

[1021] Preferably, in certain embodiments, Concept C also allows that the TX UE may not request a SL PRS from other UEs / destinations in a fourth SCI that schedules a second SL PRS retransmission in a second time slot, wherein the second SL PRS retransmission is performed after the first SL PRS retransmission, and wherein the second SL PRS retransmission and the first SL PRS retransmission are associated with the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID, the same broadcast type, the same priority value and / or the same SL PRS trigger. Preferably, in certain embodiments, the TX UE may cancel the SL PRS request in a second timing before the second SL PRS retransmission or the second time slot. Preferably, in certain embodiments, the TX UE may cancel the SL PRS request in a second timing after the first SL PRS retransmission. Preferably, in certain embodiments, the TX UE may cancel the SL PRS request in response to the transmission of the third SCI or the first SL PRS retransmission.

[1022] Preferably, in some embodiments, the first SL PRS retransmission, the initial / new SL PRS transmission and the second SL PRS retransmission are performed by the TX UE in the same side link resource pool. Preferably, in some embodiments, the side link resource pool is a dedicated SL PRS resource pool.

[1023] Preferably, in certain embodiments, another SCI may schedule initial / new SL PRS transmission.Another SCI may include SCI format 1-B.

[1024] Preferably, in some embodiments, the third SCI may schedule the first SL PRS retransmission in the first time slot. Preferably, in some embodiments, the third SCI may include SCI format 1-B. Preferably, in some embodiments, the SCI format 1-B may include an "SLPRS request" field. Preferably, in some embodiments, the SCI format 1-B may indicate that there is no SL PRS transmission in the first time slot.

[1025] Preferably, in some embodiments, the third SCI may not schedule the first SL PRS retransmission in the first time slot. SCI format 1-B may indicate a specific SL PRS resource ID corresponding to no SL PRS transmission or deactivated SL PRS transmission. Preferably, in some embodiments, the specific SL PRS resource ID may be specified or (pre)configured. Preferably, in some embodiments, one or more fields of SCI format 1-B may indicate one or more specific values ​​for indicating no SL PRS transmission or deactivated SL PRS transmission.

[1026] Preferably, in certain embodiments, based on method / concept C, a text suggestion 4 (bold and underlined) may be provided as follows.

[1027] =========================Text Proposal 4===========================

[1028] 5.22.1.xx SL-PRS Transmission on SL-PRS Dedicated Resource Pool

[1029] For each newly transmitted SCI of SL-PRS, the MAC entity shall:

[1030] 1 >Set the destination ID to the destination Layer 2 ID corresponding to the SL-PRS transmission;

[1031] 1> If [12bitSourceID] is configured:

[1032] 2> Set the source ID to the 12 [most / least significant bits] corresponding to the source layer 2 ID transmitted by the SL-PRS;

[1033] 1> Otherwise, if [24bitSourceID] is configured:

[1034] 2> Set the source ID to the source layer 2 ID corresponding to the SL-PRS transmission;

[1035] 1> Set the broadcast type indicator to one of broadcast, multicast, and unicast selected in clause 5.22.1.2.1.2 indivual;

[1036] 1> Set the SL-PRS priority to the value indicated by the upper layer;

[1037] 1>Set SL-PRS resource ID;

[1038] Editor's Note: How does FFS determine the SL-PRS resource ID and its impact on transmission on the SL-PRS dedicated resource pool? ring.

[1039] 1> If higher layers trigger SL-PRS transmission to a peer UE identified by destination Layer 2 ID:

[1040] 2> Set SL-PRS request to request.

[1041] Editor's Note: FFS When the Source ID length is configured as 12 bits, is it the MSB or LSB of the UE's Source Layer 2 ID.

[1042] For each retransmission of SL-PRS, the MAC entity shall use The SCI field that is the same as the SCI field used for the corresponding new transmission.

[1043] For each retransmission of SL-PRS The MAC entity shall:

[1044]

[1045]

[1046] use The SCI field corresponding to the new transmission

[1047] =======================End of Text Proposal 4========================

[1048] It should be noted that any of the methods, alternatives, concepts, examples and embodiments above and herein may be combined in whole or in part, or applied simultaneously or separately.

[1049]

[00136] To the extent possible of the methods, alternatives, concepts, examples and embodiments described above and in detail herein, the following aspects and embodiments are possible.

[1050] Preferably, in some embodiments, the SL PRS may be a SL channel state information reference signal (Channel State Information Reference Signal, CSI-RS).

[1051] Preferably, in certain embodiments, the SL PRS is not the SL CSI-RS.

[1052] Preferably, in some embodiments, the SL PRS may be represented / replaced by a sidelink reference signal.

[1053] Preferably, in certain embodiments, the sidelink reference signal may be applied / used for (absolute and / or relative) positioning and / or ranging.

[1054] Preferably, in some embodiments, the sidelink reference signal may be applied to / used for any one of a time-based positioning / ranging method and / or an angle-based positioning / ranging method. Preferably, in some embodiments, the sidelink reference signal may be applied to / used for any one of TDoA, RTT-based positioning / ranging, AoA, AoD, or positioning based on carrier phase measurement.

[1055] Preferably, in some embodiments, the sidelink reference signal may be a SL beam management RS. Preferably, in some embodiments, the sidelink reference signal may be a SL CSI-RS (for beam management) that is not combined within the PSSCH (bandwidth) in the frequency domain. Preferably, in some embodiments, the sidelink reference signal may require a large bandwidth. Preferably, in some embodiments, the sidelink reference signal may be used for (high resolution) positioning, sensing or imaging. Preferably, in some embodiments, the sidelink reference signal may be used for beam management (e.g., in FR2).

[1056] Preferably, in certain embodiments, any of the above-described concepts, methods, alternatives and embodiments for SL PRS may be applied to other reference signals (e.g., reference signals designed / introduced in future 5G, 6G, etc.).

[1057] Preferably, in certain embodiments, any of the above concepts, methods, alternatives and embodiments for SL PRS may be applied to SL CSI-RS (for beam management).

[1058] Preferably, in certain embodiments, any of the above-described concepts, methods, alternatives and embodiments for SL PRS may be applied to reference signals for (high-resolution) positioning (e.g., reference signals designed / introduced in future 5G, 6G, etc.).

[1059] Preferably, in certain embodiments, any of the above-described concepts, methods, alternatives and embodiments for SL PRS may be applied to reference signals for (high-resolution) sensing (e.g., reference signals designed / introduced in future 5G, 6G, etc.).

[1060] Preferably, in certain embodiments, any of the above-described concepts, methods, alternatives and embodiments for SL PRS may be applied to reference signals for (high-resolution) imaging (e.g., reference signals designed / introduced in future 5G, 6G, etc.).

[1061] Preferably, in some embodiments, the shared SL PRS resource pool is used / configured for PSSCH transmission / reception and / or SL PRS transmission / reception. Preferably, in some embodiments, the shared SL PRS resource pool may be a side link resource pool used for PSSCH transmission / reception and enabled / configured / supported for SL PRS transmission / reception / measurement.

[1062] Preferably, in certain embodiments, the sidelink communication resource pool may be a sidelink resource pool used for PSSCH transmission / reception and not enabled / configured / supported for SL PRS transmission / reception / measurement.

[1063] Preferably, in some embodiments, the dedicated SL PRS resource pool may be a side link resource pool that at least includes / provides SL PRS resources and / or side link control resources. Preferably, in some embodiments, the dedicated SL PRS resource pool does not include side link data resources (i.e., does not include PSSCH resources). Preferably, in some embodiments, the dedicated SL PRS resource pool for SL PRS does not include side link feedback resources.

[1064] Preferably, in some embodiments, the sidelink data packet may include or refer to a (sidelink) transport block (TB) or a (sidelink) MAC PDU. The (sidelink) MAC PDU may include a MAC subheader, a MAC CE (if available) and / or sidelink data from a sidelink logical channel (if available).

[1065] Preferably, in some embodiments, PSSCH may refer to sidelink data transmission.

[1066] Preferably, in some embodiments, PSFCH may refer to Sidelink Feedback Transmission.

[1067] Preferably, in some embodiments, PSCCH may mean Sidelink Control Transmission.

[1068] Preferably, in some embodiments, the SCI / PSCCH associated with the SL PRS may contain / include information for scheduling / indicating / allocating SL PRS resources.

[1069] Preferably, in some embodiments, the side link control information in the shared SL PRS resource pool or the side link communication resource pool may be transmitted / delivered via the level 1 SCI and the level 2 SCI. Preferably, in some embodiments, the side link control information in the shared SL PRS resource pool or the side link communication resource pool may be delivered at least in the PSCCH. Preferably, in some embodiments, the side link control information in the shared SL PRS resource pool or the side link communication resource pool may include the level 1 SCI. Preferably, in some embodiments, the level 1 SCI may be transmitted via the PSCCH. Preferably, in some embodiments, the side link control information in the shared SL PRS resource pool or the side link communication resource pool may include the level 2 SCI. Preferably, in some embodiments, the level 2 SCI may be transmitted via multiplexing with the PSSCH. Preferably, in some embodiments, SCI format 1 or SCI format 1-X is the level 1 SCI. Preferably, in some embodiments, SCI format 2-A or 2-B or 2-C or 2-D or 2-X is the level 2 SCI.

[1070] Preferably, in certain embodiments, SCI formats 2-A, 2-B, 2-C do not include SL PRS resource related information / field.

[1071] Preferably, in certain embodiments, SCI format 2-D includes SL PRS resource related information / field.

[1072] Preferably, in some embodiments, in order to transmit the PSSCH in a time slot or a sub-time slot, the TX UE needs to transmit the SCI in the time slot or the sub-time slot for scheduling the PSSCH.

[1073] Preferably, in some embodiments, in order to transmit the SL PRS in a time slot or a sub-time slot, the TX UE needs to transmit the SCI in the time slot or the sub-time slot for scheduling the SL PRS.

[1074] Preferably, in some embodiments, the time slot may refer to a side link time slot. Preferably, in some embodiments, the time slot may be represented / replaced as a Transmission Time Interval (TTI).

[1075] Preferably, in some embodiments, a sidelink time slot may mean a time slot used for a sidelink. Preferably, in some embodiments, a TTI may be a subframe (for a sidelink) or a time slot (for a sidelink) or a sub-time slot (for a sidelink). Preferably, in some embodiments, a TTI includes a plurality of symbols, such as 12 or 14 symbols. Preferably, in some embodiments, a TTI may be a time slot (completely / partially) including sidelink symbols. Preferably, in some embodiments, a TTI may mean a transmission time interval for sidelink (data) transmission. Preferably, in some embodiments, a sidelink time slot or a time slot for a sidelink may contain all orthogonal frequency division multiplexing (OFDM) symbols that can be used for sidelink transmission. Preferably, in some embodiments, a sidelink time slot or a time slot for a sidelink may contain a continuous number of symbols that can be used for sidelink transmission. Preferably, in some embodiments, a sidelink time slot or a time slot for a sidelink means that a time slot is included / included in a sidelink resource pool.

[1076] Preferably, in some embodiments, the symbol may mean a symbol indicated / configured to be used for a side link.

[1077] Preferably, in some embodiments, a time slot may mean / include a sidelink time slot associated with a (sidelink) resource pool. Preferably, in some embodiments, a time slot may not mean / include a sidelink time slot associated with other (sidelink) resource pools.

[1078] Preferably, in some embodiments, a subchannel is a unit for sidelink resource allocation / scheduling (for PSSCH). Preferably, in some embodiments, a subchannel may include multiple adjacent PRBs in the frequency domain. Preferably, in some embodiments, the number of PRBs used for each subchannel may be (pre)configured for the sidelink resource pool. Preferably, in some embodiments, the sidelink resource pool (pre)configuration may indicate / configure the number of PRBs used for each subchannel. Preferably, in some embodiments, the number of PRBs used for each subchannel may be any one of 10, 12, 15, 20, 25, 50, 75, 100. Preferably, in some embodiments, a subchannel may be represented as a unit for sidelink resource allocation / scheduling. Preferably, in some embodiments, a subchannel may mean a set of consecutive PRBs in the frequency domain. Preferably, in some embodiments, a subchannel may mean a set of consecutive resource elements in the frequency domain.

[1079] Preferably, in some embodiments, the first UE may have / maintain / establish multiple side link links / connections on the PC5 interface. For different side link links / connections, the first UE may perform side link transmission to / receive from side links of different paired UEs.

[1080] Preferably, in some embodiments, the first UE may have / maintain / establish a first side link link / connection and a second side link link / connection. The paired UE of the first side link link / connection may be different from the paired UE of the second side link link / connection. Preferably, in some embodiments, the side link logical channel associated with the first side link link / connection (of the paired UE) may be separated / independent from the side link logical channel associated with the second side link link / connection (of the paired UE).

[1081] Preferably, in some embodiments, UE may be / mean / include / replace a device.

[1082] Preferably, in some embodiments, the sidelink transmission / reception may be UE-to-UE transmission / reception. Preferably, in some embodiments, the sidelink transmission / reception may be device-to-device transmission / reception. Preferably, in some embodiments, the sidelink transmission / reception may be vehicle-to-everything (V2X) transmission / reception. Preferably, in some embodiments, the sidelink transmission / reception may be pedestrian-to-everything (P2X) transmission / reception. Preferably, in some embodiments, the sidelink transmission / reception may be on the PC5 interface.

[1083] Preferably, in some embodiments, the PC5 interface may be a wireless interface for communication between devices. Preferably, in some embodiments, the PC5 interface may be a wireless interface for communication between devices. Preferably, in some embodiments, the PC5 interface may be a wireless interface for communication between UEs. Preferably, in some embodiments, the PC5 interface may be a wireless interface for V2X or P2X communication. Preferably, in some embodiments, the Uu interface may be a wireless interface for communication between a network node and a device. Preferably, in some embodiments, the Uu interface may be a wireless interface for communication between a network node and a UE.

[1084] Preferably, in some embodiments, the first UE may be a first device. Preferably, in some embodiments, the first UE may be a vehicle UE. Preferably, in some embodiments, the first UE may be a V2X UE.

[1085] Preferably, in some embodiments, the second UE may be a second device. Preferably, in some embodiments, the second UE may be a vehicle UE. Preferably, in some embodiments, the second device may be a V2X UE.

[1086] Preferably, in some embodiments, the first UE and the second device are different devices.

[1087] Various examples and embodiments of the invention are described below.

[1088] refer to Figure 7 , utilizing this and other concepts, systems and methods of the present invention, a method 1000 for a first device in a wireless communication system includes: receiving a configuration of a first side link resource pool for side link data transmission and / or a side link reference signal (step 1002), performing a new / initial side link data transmission for transmitting a side link data packet, wherein the new / initial side link data transmission does not multiplex the side link reference signal (step 1004), and performing a first side link data retransmission for transmitting the same side link data packet while multiplexing the side link reference signal transmission in a first time slot (step 1006).

[1089] In various embodiments, the first device triggers or is triggered for sidelink reference signal transmission in a first timing later than an initial / new sidelink data transmission.

[1090] In various embodiments, the first device performs a second side link data retransmission in a second time slot for transmitting the same side link data packet, wherein the second side link data retransmission does not multiplex a side link reference signal, wherein the second side link data retransmission is performed after the first side link data retransmission.

[1091] In various embodiments, the first device cancels the triggering of the sidelink reference signal transmission in a second timing before the second sidelink data retransmission or the second time slot, or in response to the first sidelink data transmission in the case of multiplexed sidelink reference signal transmission, the first device cancels the triggering of the sidelink reference signal transmission, or in response to the first device performing the sidelink reference signal transmission for a first number of times, the first device cancels the triggering of the sidelink reference signal transmission.

[1092] In various embodiments, the second sidelink data retransmission cannot multiplex the sidelink reference signal transmission, for example, due to insufficient symbols for the sidelink reference signal transmission in the second sidelink data retransmission or due to the presence of sidelink feedback resources in the second time slot.

[1093] In various embodiments, the new / initial sidelink data transmission, the first sidelink data retransmission, and / or the second sidelink data retransmission are performed in a sidelink resource pool.

[1094] Return to reference Figure 3 and 4In one or more embodiments, from the perspective of a first device in a wireless communication system, the device 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 can execute the program code 312 to: (i) receive a configuration of a first sidelink resource pool for sidelink data transmission and / or sidelink reference signal; (ii) perform a new / initial sidelink data transmission for transmitting a sidelink data packet, wherein the new / initial sidelink data transmission does not multiplex the sidelink reference signal, and (iii) perform a first sidelink data retransmission for transmitting the same sidelink data packet when the sidelink reference signal transmission is multiplexed in the first time slot. In addition, the CPU 308 can execute the program code 312 to perform all described actions, steps and methods described above, below or otherwise described herein.

[1095] refer to Figure 8 , utilizing this and other concepts, systems and methods of the present invention, a method 1010 for a first device in a wireless communication system includes: receiving a configuration of a first sidelink resource pool for sidelink data transmission and / or sidelink reference signal from a network (step 1012), determining a first sidelink reference signal resource ID (step 1014), multiplexing a first sidelink reference signal transmission and a first sidelink data transmission in a first time slot, wherein the first sidelink reference signal transmission is associated with the first sidelink reference signal resource ID (step 1016), determining a second sidelink reference signal resource ID (step 1018), and multiplexing a second sidelink reference signal transmission and a second sidelink data transmission in a second time slot, wherein the second sidelink reference signal transmission is associated with the second sidelink reference signal resource ID, and the first sidelink data transmission and the second sidelink data transmission are used to transmit the same sidelink data packet (step 1020).

[1096] In various embodiments, the second sidelink reference signal resource ID is allowed to be different from the first sidelink reference signal resource ID, and / or the second sidelink reference signal resource ID is the same as or different from the first sidelink reference signal resource ID.

[1097] In various embodiments, the determination of the first sidelink reference signal resource ID is separate or independent from the determination of the second sidelink reference signal resource ID.

[1098] In various embodiments, the first sidelink data transmission is an initial transmission for transmitting the same sidelink data packet, and the second sidelink data transmission is a retransmission for transmitting the same sidelink data packet.

[1099] In various embodiments, the first sidelink data transmission and the second sidelink data transmission are different retransmissions of the same sidelink data packet.

[1100] In various embodiments, the method further includes: in response to whether the time slot includes one or more side link feedback symbols, resources or opportunities, determining a side link reference signal resource ID associated with the side link reference signal transmission located in the first side link resource pool in the time slot, and / or in response to the first time slot not including one or more side link feedback symbols, resources, opportunities in the first side link resource pool, determining the first side link reference signal resource ID, and / or in response to the second time slot including one or more side link feedback symbols, resources, opportunities in the first side link resource pool, determining the second side link reference signal resource ID.

[1101] In various embodiments, the first sidelink data transmission and the second sidelink data transmission are performed in a sidelink resource pool.

[1102] In various embodiments, the first sidelink reference signal transmission and the second sidelink reference signal transmission are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID and / or the same broadcast type, and / or the first sidelink reference signal transmission and the sidelink data packet are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID and / or the same broadcast type, and / or the second sidelink reference signal transmission and the sidelink data packet are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID and / or the same broadcast type.

[1103] In various embodiments, a first sidelink reference signal resource ID corresponds (or is mapped) to a first number of sidelink symbols, a first comb size, and a first comb offset, and / or a second sidelink reference signal resource ID corresponds (or is mapped) to a second number of sidelink symbols, a second comb size, and a second comb offset, and / or a first resource of a first sidelink reference signal transmission is associated with the first sidelink reference signal resource ID, and / or a second resource of a second sidelink reference signal transmission is associated with a second sidelink reference signal resource ID.

[1104] In various embodiments, the first sidelink data retransmission means a first PSSCH transmission, and / or the second sidelink data retransmission means a second PSSCH transmission, and / or the sidelink reference signal means a SL PRS, and / or the sidelink reference signal means a sidelink CSI-RS for beam management, and / or the sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or the first sidelink reference signal means a first SL PRS, and / or the first sidelink reference signal means a first sidelink CSI-RS for beam management, and / or the first sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or the second sidelink reference signal means a second SL PRS, and / or the second sidelink reference signal means a second sidelink CSI-RS for beam management, and / or the second sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging.

[1105] Return to reference Figure 3 and 4 In one or more embodiments, from the perspective of a first device in a wireless communication system, the device 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 can execute the program code 312 to: (i) receive a configuration of a first side link resource pool for side link data transmission and / or side link reference signal from a network; (ii) determine a first side link reference signal resource ID; (iii) multiplex the first side link reference signal transmission and the first side link data transmission in a first time slot, wherein the first side link reference signal transmission is associated with the first side link reference signal resource ID; (iv) determine a second side link reference signal resource ID; and (v) multiplex the second side link reference signal transmission and the second side link data transmission in a second time slot, wherein the second side link reference signal transmission is associated with the second side link reference signal resource ID, and the first side link data transmission and the second side link data transmission are used to transmit the same side link data packet. In addition, the CPU 308 can execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[1106] refer to Fig. 9, utilizing this and other concepts, systems and methods of the present invention, a method 1030 for a first device in a wireless communication system includes: receiving a configuration of a first sidelink resource pool for sidelink data transmission and / or a sidelink reference signal from a network (step 1032), triggering the first sidelink reference signal for transmission based on signaling sent from a second device or based on an upper layer of the first device (step 1034), setting a first sidelink reference signal resource ID associated with a first transmission of the first sidelink reference signal for an initial transmission carrying a sidelink data packet (step 1036), performing an initial multiplexing of the first transmission of the first sidelink reference signal to the second device, The method further comprises: starting transmission, wherein the first transmission of the first sidelink reference signal is associated with the first sidelink reference signal resource ID (step 1038), setting a second sidelink reference signal resource ID associated with the second transmission of the first sidelink reference signal for retransmission of a carrying sidelink data packet (step 1040), and performing a retransmission multiplexed with the second transmission of the first sidelink reference signal to a second device, wherein the second transmission of the first sidelink reference signal is associated with the second sidelink reference signal resource ID, and wherein the first sidelink reference signal resource ID and the second sidelink reference signal resource ID are determined by an upper layer of the first device (step 1042).

[1107] In various embodiments, a first transmission of a first sidelink reference signal and a second transmission of the first sidelink reference signal are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID, and / or the same broadcast type, and / or the first sidelink reference signal and the sidelink data packet for transmission are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID, and / or the same broadcast type, and / or the first transmission of the first sidelink reference signal and the sidelink data packet are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID, and / or the same broadcast type, and / or the second transmission of the first sidelink reference signal and the sidelink data packet are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID, and / or the same broadcast type.

[1108] In various embodiments, a first side link reference signal resource ID corresponds (or is mapped) to a first number of side link symbols, a first comb size, and a first comb offset, and / or a second side link reference signal resource ID corresponds (or is mapped) to a second number of side link symbols, a second comb size and a second comb offset, and / or a first resource of a first transmission of a first side link reference signal is associated with the first side link reference signal resource ID, and / or a second resource of a second transmission of the first side link reference signal is associated with the second side link reference signal resource ID.

[1109] In various embodiments, initial transmission means initial PSSCH retransmission, and / or retransmission means PSSCH retransmission, and / or side link reference signal means SL PRS, and / or side link reference signal means side link CSI-RS for beam management, and / or side link reference signal is used for any of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or first side link reference signal means first SL PRS, and / or first side link reference signal means first side link CSI-RS for beam management, and / or first side link reference signal is used for any of positioning, ranging, beam management, high-resolution positioning, sensing or imaging.

[1110] Return to reference Figure 3 and 4 In one or more embodiments, from the perspective of a first device in a wireless communication system, the device 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 executable program code 312 is to: (i) receive a configuration of a first side link resource pool for side link data transmission and / or a side link reference signal from a network; (ii) trigger the first side link reference signal for transmission based on signaling sent from a second device or based on an upper layer of the first device; (iii) set a first side link reference signal resource ID associated with a first transmission of the first side link reference signal for an initial transmission of a carrying side link data packet; (iv) perform an initial transmission multiplexed with the first transmission of the first side link reference signal to a second device, wherein the first transmission of the first side link reference signal is associated with the first side link reference signal resource ID; (v) set a second side link reference signal resource ID associated with a second transmission of the first side link reference signal for a retransmission of the carrying side link data packet; and (vi) perform a retransmission multiplexed with the second transmission of the first side link reference signal to the second device, wherein the second transmission of the first side link reference signal is associated with the second side link reference signal resource ID, and wherein the first side link reference signal resource ID and the second side link reference signal resource ID are determined by an upper layer of the first device. Furthermore, CPU 308 may execute program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[1111] refer to Fig.10, utilizing this and other concepts, systems and methods of the present invention, a method 1050 for a first device in a wireless communication system includes: receiving a configuration of a first sidelink resource pool for sidelink data transmission and / or sidelink reference signal from a network (step 1052), triggering a sidelink reference signal transmission based on signaling sent from a second device or based on an upper layer of the first device (step 1054), (allowing) the upper layer of the first device to determine two sidelink reference signal resource IDs for a first transmission and a second transmission, respectively, wherein the first transmission and the second transmission carry the same sidelink data packet (step 1056), setting a first sidelink reference signal resource ID associated with the first sidelink reference signal for the first transmission (step 1058), performing a first transmission multiplexed with the first sidelink reference signal to the second device (step 1060), setting a second sidelink reference signal resource ID associated with the second sidelink reference signal for the second transmission (step 1062), and performing a second transmission multiplexed with the second sidelink reference signal to the second device (step 1064).

[1112] In various embodiments, the first transmission is an initial transmission for transmitting the same sidelink data packet, and the second transmission is a retransmission for transmitting the same sidelink data packet.

[1113] In various embodiments, the first transmission and the second transmission are different retransmissions for transmitting the same sidelink data packet.

[1114] In various embodiments, the first sidelink reference signal and the second sidelink reference signal are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID and / or the same broadcast type, and / or the first sidelink reference signal and the same sidelink data packet are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID and / or the same broadcast type, and / or the second sidelink reference signal and the same sidelink data packet are associated with any of the same (layer 1 or layer 2) destination ID, the same (layer 1 or layer 2) source ID and / or the same broadcast type.

[1115] In various embodiments, a first side link reference signal resource ID corresponds (or is mapped) to a first number of side link symbols, a first comb size, and a first comb offset, and / or a second side link reference signal resource ID corresponds (or is mapped) to a second number of side link symbols, a second comb size, and a second comb offset, and / or a first resource of a first side link reference signal is associated with the first side link reference signal resource ID, and / or a second resource of a second side link reference signal is associated with a second side link reference signal resource ID.

[1116] In various embodiments, the first transmission means a first PSSCH transmission, and / or the second transmission means a second PSSCH transmission, and / or the sidelink reference signal means a SL PRS, and / or the sidelink reference signal means a sidelink CSI-RS for beam management, and / or the sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or the first sidelink reference signal means a first SL PRS, and / or the first sidelink reference signal means a first sidelink CSI-RS for beam management, and / or the first sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or the second sidelink reference signal means a second SL PRS, and / or the second sidelink reference signal means a second sidelink CSI-RS for beam management, and / or the second sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging.

[1117] Return to reference Figure 3 and 4 In one or more embodiments, from the perspective of a first device in a wireless communication system, the device 300 includes program code 312 stored in a memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive a configuration of a first sidelink resource pool for sidelink data transmission and / or sidelink reference signal from a network; (ii) trigger a sidelink reference signal transmission based on signaling sent from a second device or based on an upper layer of the first device; (iii) allow the upper layer of the first device to determine two sidelink reference signal resource IDs for a first transmission and a second transmission, respectively, wherein the first transmission and the second transmission carry the same sidelink data packet; (iv) set a first sidelink reference signal resource ID associated with the first sidelink reference signal for the first transmission; (v) perform a first transmission multiplexed with the first sidelink reference signal to the second device; (vi) set a second sidelink reference signal resource ID associated with the second sidelink reference signal for the second transmission; and (vii) perform a second transmission multiplexed with the second sidelink reference signal to the second device. Furthermore, CPU 308 may execute program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[1118] Any combination of the concepts or teachings above or herein may be fully or partially combined or formed into new embodiments. The disclosed details and embodiments can be used to at least (but not limited to) solve the problems mentioned above and herein.

[1119] It should be noted that any of the methods, alternatives, steps, examples and embodiments presented herein may be applied independently, individually and / or in combination with multiple methods, alternatives, steps, examples and embodiments.

[1120] Various aspects of the present disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more aspects of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement a device or practice method. In addition, other structures, functionality, or structure and functionality other than one or more of the aspects described herein or different from one or more of the aspects described herein can be used to implement such devices or to practice such methods. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequencies. In some aspects, parallel channels can be established based on pulse positions or offsets. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

[1121] Those of ordinary skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[1122] It should be further understood by those of ordinary skill in the art that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source code or some other technique), and various forms of programs or design code with instructions (which may be referred to herein as "software" or "software modules" for convenience), or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those of ordinary skill in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[1123] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an 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 in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[1124] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in an example order, but are not meant to be limited to the specific order or hierarchy presented.

[1125] The steps of the method or algorithm described in conjunction with the various aspects disclosed herein may be implemented directly with hardware, with a software module executed by a processor, or with a combination of the two. Software modules (e.g., including executable instructions and related data) and other data may reside in a data memory, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. Sample storage media may be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to as a "processor" herein) so that the processor can read information (e.g., code) from the storage medium and write the information to the storage medium. Example storage media may be integrated with the processor. The processor and storage medium may be present in an ASIC. The ASIC may reside in a user device. In an alternative, the processor and storage medium may reside in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium, which includes code related to one or more aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[1126] Although the present invention has been described in conjunction with various aspects and examples, it will be appreciated that the present invention is capable of further modifications. This application is intended to cover any changes, uses or adaptations of the present invention, which generally follow the principles of the present invention and include such deviations from the present disclosure, which are within the scope of known and customary practice in the technical field to which the present invention belongs.

Claims

1. A method of a first device, characterized in that, include: receiving, from a network, a configuration of a first sidelink resource pool for sidelink data transmission and / or a sidelink reference signal; Determining a first sidelink reference signal resource identifier; multiplexing a first sidelink reference signal transmission and a first sidelink data transmission in a first time slot, wherein the first sidelink reference signal transmission is associated with the first sidelink reference signal resource identifier; Determining a second sidelink reference signal resource identifier; as well as A second sidelink reference signal transmission and a second sidelink data transmission are multiplexed in a second time slot, wherein the second sidelink reference signal transmission is associated with the second sidelink reference signal resource identifier, and the first sidelink data transmission and the second sidelink data transmission are used to transmit the same sidelink data packet.

2. The method according to claim 1, characterized in that: The second sidelink reference signal resource identifier is allowed to be different from the first sidelink reference signal resource identifier, and / or The second sidelink reference signal resource identifier is the same as or different from the first sidelink reference signal resource identifier.

3. The method according to claim 1, characterized in that The determination of the first sidelink reference signal resource identification is separate from or independent of the determination of the second sidelink reference signal resource identification.

4. The method according to claim 1, characterized in that: The first sidelink data transmission is an initial transmission for transmitting the same sidelink data packet, and The second sidelink data transmission is a retransmission for transmitting the same sidelink data packet.

5. The method according to claim 1, characterized in that The first sidelink data transmission and the second sidelink data transmission are different retransmissions for transmitting the same sidelink data packet.

6. The method according to claim 1, characterized in that Further including: Responsive to whether a timeslot includes one or more sidelink feedback symbols, resources, or opportunities, determining a sidelink reference signal resource identifier associated with a sidelink reference signal transmission in the first sidelink resource pool in the timeslot; and / or In response to the first time slot not including one or more side link feedback symbols, resources, opportunities in the first side link resource pool, determining the first side link reference signal resource identifier; and / or In response to the second time slot including one or more side link feedback symbols, resources, and opportunities in the first side link resource pool, determining the second side link reference signal resource identifier.

7. The method according to claim 1, characterized in that The first sidelink data transmission and the second sidelink data transmission are performed in the sidelink resource pool.

8. The method according to claim 1, characterized in that: The first sidelink reference signal transmission and the second sidelink reference signal transmission are associated with any of a same destination identification, a same source identification and / or a same broadcast type, and / or The first sidelink reference signal transmission and the sidelink data packet are associated with any of the same destination identification, the same source identification and / or the same broadcast type, and / or The second sidelink reference signal transmission and the sidelink data packet are associated with any of the same destination identification, the same source identification and / or the same broadcast type.

9. The method according to claim 1, characterized in that: The first sidelink reference signal resource identifier corresponds to a first number of sidelink symbols, a first comb size and a first comb offset, and / or The second sidelink reference signal resource identifier corresponds to a second number of sidelink symbols, a second comb size and a second comb offset, and / or The first resource transmitted by the first sidelink reference signal is associated with the first sidelink reference signal resource identifier, and / or The second resource for transmitting the second sidelink reference signal is associated with the second sidelink reference signal resource identifier.

10. The method according to claim 1, characterized in that: The first sidelink data retransmission means a first physical sidelink shared channel transmission, and / or The second sidelink data retransmission means a second physical sidelink shared channel transmission, and / or The sidelink reference signal refers to a sidelink positioning reference signal, and / or The sidelink reference signal refers to a sidelink channel state information reference signal used for beam management, and / or The sidelink reference signal is used for any of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or The first sidelink reference signal means a first sidelink positioning reference signal, and / or The first sidelink reference signal means a first sidelink channel state information reference signal used for beam management, and / or The first sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or The second sidelink reference signal means a second sidelink positioning reference signal, and / or The second sidelink reference signal means a second sidelink channel state information reference signal used for beam management, and / or The second sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging.

11. A method of a first device, characterized in that, include: receiving, from a network, a configuration of a first sidelink resource pool for sidelink data transmission and / or a sidelink reference signal; triggering a first sidelink reference signal for transmission based on signaling sent from a second device or based on an upper layer of the first device; setting, for an initial transmission of a carrying sidelink data packet, a first sidelink reference signal resource identifier associated with a first transmission of the first sidelink reference signal; performing the initial transmission multiplexed with the first transmission of the first sidelink reference signal to the second device, wherein the first transmission of the first sidelink reference signal is associated with the first sidelink reference signal resource identification; setting a second sidelink reference signal resource identifier associated with a second transmission of the first sidelink reference signal for a retransmission carrying the sidelink data packet; as well as The retransmission multiplexed with the second transmission of the first sidelink reference signal is performed to the second device, wherein the second transmission of the first sidelink reference signal is associated with the second sidelink reference signal resource identifier, and wherein the first sidelink reference signal resource identifier and the second sidelink reference signal resource identifier are determined by the upper layer of the first device.

12. The method according to claim 11, characterized in that: The first transmission of the first sidelink reference signal and the second transmission of the first sidelink reference signal are associated with any of a same destination ID, a same source ID and / or a same broadcast type, and / or The first sidelink reference signal and the sidelink data packet for transmission are associated with any one of the same destination identifier, the same source identifier and / or the same broadcast type, and / or The first transmission of the first sidelink reference signal and the sidelink data packet are associated with any of the same destination identification, the same source identification and / or the same broadcast type, and / or The second transmission of the first sidelink reference signal and the sidelink data packet are associated with any of the same destination identification, the same source identification and / or the same broadcast type.

13. The method according to claim 11, characterized in that: The first sidelink reference signal resource identifier corresponds to a first number of sidelink symbols, a first comb size and a first comb offset, and / or The second sidelink reference signal resource identifier corresponds to a second number of sidelink symbols, a second comb size and a second comb offset, and / or The first resource of the first transmission of the first sidelink reference signal is associated with the first sidelink reference signal resource identifier, and / or The second resource of the second transmission of the first sidelink reference signal is associated with the second sidelink reference signal resource identification.

14. The method according to claim 11, characterized in that: The initial transmission means an initial physical sidelink shared channel retransmission, and / or The retransmission means physical sidelink shared channel retransmission, and / or The sidelink reference signal refers to a sidelink positioning reference signal, and / or The sidelink reference signal refers to a sidelink channel state information reference signal used for beam management, and / or The sidelink reference signal is used for any of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or The first sidelink reference signal means a first sidelink positioning reference signal, and / or The first sidelink reference signal means a first sidelink channel state information reference signal used for beam management, and / or The first sidelink reference signal is used for any of positioning, ranging, beam management, high-resolution positioning, sensing or imaging.

15. A method of a first device, characterized in that, include: receiving, from a network, a configuration of a first sidelink resource pool for sidelink data transmission and / or a sidelink reference signal; triggering a sidelink reference signal transmission based on signaling sent from a second device or based on an upper layer of the first device; allowing the upper layer of the first device to determine two sidelink reference signal resource identifiers for a first transmission and a second transmission, respectively, wherein the first transmission and the second transmission carry the same sidelink data packet; setting, for the first transmission, a first sidelink reference signal resource identifier associated with a first sidelink reference signal; performing the first transmitting multiplexed with the first sidelink reference signal to the second device; setting, for the second transmission, a second sidelink reference signal resource identifier associated with a second sidelink reference signal; as well as The second transmitting multiplexed with the second sidelink reference signal is performed to the second device.

16. The method according to claim 15, characterized in that: The first transmission is an initial transmission for transmitting the same sidelink data packet, and The second transmission is a retransmission for transmitting the same sidelink data packet.

17. The method according to claim 15, characterized in that The first transmission and the second transmission are different retransmissions for transmitting the same sidelink data packet.

18. The method according to claim 15, characterized in that: The first sidelink reference signal and the second sidelink reference signal are associated with any one of a same destination identifier, a same source identifier and / or a same broadcast type, and / or The first sidelink reference signal and the same sidelink data packet are associated with any one of the same destination identifier, the same source identifier and / or the same broadcast type, and / or The second sidelink reference signal and the same sidelink data packet are associated with any one of the same destination identification, the same source identification and / or the same broadcast type.

19. The method according to claim 15, characterized in that: The first sidelink reference signal resource identifier corresponds to a first number of sidelink symbols, a first comb size and a first comb offset, and / or The second sidelink reference signal resource identifier corresponds to a second number of sidelink symbols, a second comb size and a second comb offset, and / or The first resource of the first sidelink reference signal is associated with the first sidelink reference signal resource identifier, and / or The second resource of the second sidelink reference signal is associated with the second sidelink reference signal resource identifier.

20. The method according to claim 15, characterized in that: The first transmission means a first physical sidelink shared channel transmission, and / or The second transmission means a second physical sidelink shared channel transmission, and / or The sidelink reference signal refers to a sidelink positioning reference signal, and / or The sidelink reference signal refers to a sidelink channel state information reference signal used for beam management, and / or The sidelink reference signal is used for any of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or The first sidelink reference signal means a first sidelink positioning reference signal, and / or The first sidelink reference signal means a first sidelink channel state information reference signal used for beam management, and / or The first sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging, and / or The second sidelink reference signal means a second sidelink positioning reference signal, and / or The second sidelink reference signal means a second sidelink channel state information reference signal used for beam management, and / or The second sidelink reference signal is used for any one of positioning, ranging, beam management, high-resolution positioning, sensing or imaging.

Images