Method and apparatus for sidelink transmission using beamforming in a communication system

Abstract

Methods, systems, and devices are provided for sidelink transmissions using beamforming in a wireless communication system, wherein the method of a first user equipment includes performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second user equipment; and transmitting information indicating a set of transmission time intervals to the network node, wherein the set of transmission time intervals corresponds to the second user equipment monitoring or receiving sidelink control information in the sidelink resource pool via a second beam associated with the first user equipment.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application Nos. 63 / 527,295, 63 / 527,312, 63 / 527,314, 63 / 527,319, and 63 / 527,324, filed on July 17, 2023, which are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates generally to wireless communication networks, and more particularly, to a method and apparatus for sidelink transmissions utilizing beamforming in a wireless communication system. 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 with Internet Protocol (IP) data packet communications, which 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 evolve and complete the 3GPP standards. Summary of the invention

[0006] The present invention provides methods, systems and devices for sidelink transmission using beamforming in a wireless communication system, wherein the method of a first user equipment (UE) includes: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE; and transmitting information indicating a set of transmission time intervals (TTIs) to a network node, wherein the TTI set corresponds to the second UE monitoring or receiving sidelink control information (SCI) in a sidelink resource pool via a second beam associated with the first UE.

[0007] In various embodiments, a method for a first UE to perform sidelink transmission in a sidelink resource pool includes: performing one or more unicast sidelink transmissions with one or more destinations, wherein the first UE determines to apply a transmitted beam for sidelink transmission to each of the one or more destinations; receiving one or more messages from the one or more destinations, wherein each of the one or more messages indicates a listening mode associated with the one transmitted beam, and information of a TTI in which one of the one or more destinations listens to the sidelink transmission via a received beam associated with the one transmitted beam; having available sidelink data associated with a subset of the one or more destinations; receiving a sidelink grant for scheduling one or more sidelink resources from a network node in one or more TTIs; and selecting or determining a destination from the subset of the one or more destinations, wherein the first UE selects or determines the destination based at least on one or more messages received by the destination in a TTI among the one or more TTIs in which the destination listens via a received beam associated with the one transmitted beam. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 The drawings show a wireless communication system according to an embodiment of the present invention.

[0009] 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.

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

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

[0012] Figure 5 It is from 3GPP 38.321v17.4.0(2023-03) Figure 6 .1.3.47-1: Unified TCI state activation / deactivation of MAC CE reproduction.

[0013] Figure 6 It is from 3GPP TS 38.321V17.4.0(2023-03) Figure 6 .1.3.33-1: Reproduction of SL-BSR and truncated SL-BSR MAC control elements.

[0014] Figure 7is an example diagram showing that TX UE communicates with RX UE1 using SL resources scheduled by a network node (e.g., which may be a gNB or a future release network node) according to an embodiment of the present invention.

[0015] Figure 8 This is an example diagram showing, according to an embodiment of the present invention, considering SL granting to indicate TTI n+9 to the TX UE, the TX UE determines the destination UE as RX UE1, and the TX UE determines the TX beam for sidelink transmission based on the currently used / indicated beam (pair), wherein the currently used / indicated beam is beam Y (on the TX UE side) or a TX beam corresponding to the RX beam of RX UE1 (for example, beam B).

[0016] Fig. 9 It is a flowchart of a method for a first UE according to an embodiment of the present invention, the method comprising: performing one or more unicast side link transmissions with one or more destinations including a second destination associated with a second UE; transmitting information associated with a TTI set to a network node, wherein, preferably in some embodiments, the TTI set corresponds to an SCI in a side link resource pool monitored / received by the second UE via a paired beam associated with the first UE; having available side link data associated with the second UE; transmitting a BSR including the side link data to the network node; and receiving a side link grant for scheduling one or more side link resources from the network node.

[0017] Fig.10 is a flowchart of a method for a first UE according to an embodiment of the present invention, the method comprising: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE; having available sidelink data associated with the second UE; transmitting a BSR including the sidelink data to a network node; and receiving a sidelink grant for scheduling one or more sidelink resources from the network node.

[0018] Fig.11 It is a flowchart of a method of a first UE according to an embodiment of the present invention, the method comprising: having available side link data associated with a second UE and a third UE; determining whether to trigger an SR or BSR including side link data available for other UEs based on whether there is a beam problem between the links of the first UE and other UEs; when there is a beam problem between the first UE and the second UE, the first UE does not trigger an SR or BSR including available side link data associated with the second UE; and receiving a side link grant for one or more side link resources in a scheduling TTI from a network node.

[0019] Fig.12It is a flowchart of a method for a first UE according to an embodiment of the present invention, the method comprising: performing one or more unicast side link transmissions with one or more destinations including a second destination associated with a second UE and preferably a third destination associated with a third UE in some embodiments; preferably receiving (exchanging with) information from one or more destinations in some embodiments; and performing unicast side link transmissions to a second UE via a TX beam.

[0020] Fig.13 It is a flowchart of a method for a first UE according to an embodiment of the present invention, the method comprising: transmitting an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam; and preferably in some embodiments, determining whether to perform a sidelink transmission on reserved resources in a second TTI via a second TX beam different from the first TX beam based on the first UE performing a sidelink transmission in a sidelink resource allocation mode.

[0021] Fig.14 It is a flowchart of a method for a first UE according to an embodiment of the present invention, the method comprising: transmitting an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam; receiving a configuration associated with an SL CG (with periodicity) from a network node; and performing a side link transmission on a side link resource associated with the SL CG.

[0022] Fig.15 is a flow chart of a method of a first UE according to an embodiment of the present invention, the method comprising transmitting an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam.

[0023] Fig.16 is a flowchart of a method for a first UE according to an embodiment of the present invention, the method comprising: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE; and transmitting information indicating a TTI set to a network node.

[0024] Fig.17 It is a flowchart of a method of a first UE according to an embodiment of the present invention, the method comprising: performing one or more unicast sidelink transmissions with one or more destinations; receiving one or more messages from one or more destinations; having available sidelink data associated with a subset of one or more destinations; receiving a sidelink grant for scheduling one or more sidelink resources from a network node in one or more TTIs; and selecting or determining a destination from a subset of one or more destinations. DETAILED DESCRIPTION

[0025] 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 primarily described in the context of the 3GPP architecture reference model. However, it should be understood that with the disclosed information, those skilled in the art can easily make adjustments to use and implement aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

[0026] 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 can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) wireless access, 3GPP Long Term Evolution Advanced (LTE-A) wireless access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0027] Specifically, the exemplary wireless communication system device described below can be designed to support one or more standards, such as standards provided by an association named "3rd Generation Partnership Project" (referred to as 3GPP in this article), including: [1] RP-221798, OPPO; [2] 3GPP TS 38.213 V17.6.0 (2023-06) Third Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Layer Procedures for Control (Release 17); [3] 3GPP TS 38.214 V17.6.0 (2023-06) Third Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Layer Procedures for Data (Release 17); [4] 3GPP TS 38.331 V17.0.0 (2022-03) Third Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) Protocol Specification (Release 17); [5] 3GPP TS 38.212 V17.5.0 (2023-06) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and Channel Coding (Release 17); and [6] 3GPP TS 38.321 V17.4.0 (2022-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) Protocol Specification (Release 17). The standards and documents listed above are expressly and entirely incorporated by reference in their entirety.

[0028] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is shown. An access network 100 (AN) 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 1 , only two antennas are shown for each antenna group, but 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.

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

[0030] In communicating via 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. Also, an access network's use of beamforming to transmit to access terminals randomly dispersed throughout the coverage area of ​​the access network generally results in less interference to access terminals in neighboring cells than if the access network transmitted to all of its access terminals via a single antenna.

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

[0032] 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.

[0033] In one embodiment, each data stream is transmitted via a respective 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.

[0034] 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 are 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 the processor 230. The memory 232 is coupled to the processor 230.

[0035] 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). The TX MIMO processor 220 then converts the N T The modulation symbol stream is 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.

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

[0037] 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 provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

[0038] RX data processor 260 then extracts the N R The receiver 254 receives and processes N R receive symbol streams to provide N T The 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 processor 260 is complementary to that performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0039] 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.

[0040] The reverse link message may include various types of information related to 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.

[0041] 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 reverse 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.

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

[0043] Steering Figure 3 , this figure 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 1 UE (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 the input device 302 (for example, a keyboard or a keypad), and can output images and sounds through the output device 304 (for example, a display or a speaker). The transceiver 314 is used to receive and transmit wireless signals to pass the received signal to the control circuit 306 and wirelessly output the signal generated by the control circuit 306.

[0044] Figure 4 According to one embodiment of the present invention Figure 34. 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 generally performs radio resource control. Layer 2 portion 404 generally performs link control. Layer 1 portion 406 generally performs physical connectivity.

[0045] 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.

[0046] Any two or more of the following paragraphs, (sub)bullets, points, actions or claims described in each invention paragraph or clause may be logically, reasonably and appropriately combined to form a specific method.

[0047] Any sentence, paragraph, (sub) bullet point, key point, action or claim described in each invention paragraph or clause below can be implemented independently and individually to form a specific method or device. The dependency in the following invention disclosure (e.g., "based on", "more specifically", "example", etc.) is only a possible embodiment that does not limit a specific method or device.

[0048] In [1] RP-221798, OPPO, the adjustments and goals for sidelink evolution in Rel-18 are cited below.

[0049] 4. Goals

[0050] …

[0051] Study and specify enhanced sidelink operation on FR2 licensed spectrum [RAN1, RAN2, RAN4] (this part of work is on hold until further examination in RAN#97)

[0052] Updated evaluation methodology for commercial deployment scenarios

[0053] The work is limited to supporting sidelink beam management (including initial beam pairing, beam maintenance, and beam failure recovery, etc.) by reusing the existing sidelink CSI framework where possible and reusing the Uu beam management concept.

[0054] Beam management in FR2 licensed spectrum only considers sidelink unicast communications.

[0055] In [2] 3GPP TS 38.213 V17.6.0 (2023-06), the procedures related to the side link are referenced below.

[0056] 16.3 UE procedures for reporting and obtaining control information in PSFCH

[0057] The control information provided by the PSFCH transmission includes HARQ-ACK information or contention information.

[0058] 16.3.0 UE Procedure for Transmitting PSFCH with Control Information

[0059] The UE may be instructed by the SCI format that schedules PSSCH reception to transmit a PSFCH with HARQ-ACK information in response to PSSCH reception. The UE provides HARQ-ACK information including ACK or NACK or only NACK.

[0060] The number of slots in the resource pool within the period of the PSFCH transmission occasion resource may be provided to the UE by sl-PSFCH-Period. If the number is zero, PSFCH transmission from the UE in the resource pool is disabled.

[0061] The UE may be enabled by sl-InterUE-CoordinationScheme2 to transmit PSFCH with conflict information in a resource pool. The UE may determine a resource set including one or more time slots and resource blocks reserved for PSSCH transmission based on the indication of SCI format 1-A. If the UE determines a conflict of reserved resources for PSSCH transmission, the UE provides the conflict information in the PSFCH.

[0062] UE expects Case time slot There are PSFCH transmission occasion resources, among which Defined in [6, TS 38.214], and T′ max is the number of time slots belonging to the resource pool within 10240 ms according to [6, TS 38.214], and Provided by sl-PSFCH-Period.

[0063] The UE may be instructed by higher layers not to transmit a PSFCH containing HARQ-ACK information in response to PSSCH reception [11, TS 38.321].

[0064] If the UE receives PSSCH in a resource pool and the HARQ feedback enable / disable indicator field in the associated SCI format 2-A / 2-B / 2-C has a value of 1 [5, TS 38.212], the UE provides HARQ-ACK information in the PSFCH transmission in the resource pool.

[0065] 16.3.1 UE Procedure for Receiving PSFCH with Control Information

[0066] …

[0067] If the UE receives a PSFCH with conflicting information corresponding to the reserved resources indicated in SCI format 1-A, the UE receives the PSFCH in the resource pool in the time slot determined based on sl-PSFCH-Occasion.

[0068] - If sl-PSFCH-Occasion = '0', the UE receives PSFCH in the first slot containing PSFCH resources and being the number of slots of the resource pool provided by sl-MinTimeGapPSFCH after the slot providing PSCCH transmission of SCI format 1-A. The PSFCH resources are in a slot at least T3 slots before the resources associated with the collision information [6, TS 38.214]; otherwise, the UE does not receive PSFCH with collision information

[0069] - If sl-PSFCH-Occasion = '1', the UE receives PSFCH in the latest slot that contains PSFCH resources and is at least T3 slots before the slot of the resource pool with the resources associated with the collision information. The PSFCH resources are in a slot that is at least sl-MinTimeGapPSFCH slots after the slot providing the PSCCH transmission of SCI format 1-A; otherwise, the UE does not receive PSFCH with collision information

[0070] 16.4 UE Procedure for Transmitting PSCCH

[0071] For PSCCH transmission with SCI format 1-A, several symbols from a resource pool starting from the second symbol available for SL transmission in the time slot may be provided to the UE via sl-TimeResourcePSCCH, and several PRBs from a resource pool starting from the lowest PRB of the lowest subchannel of the associated PSSCH may be provided to the UE via sl-FreqResourcePSCCH.

[0072] UE transmitting PSCCH with SCI format 1-A using sidelink resource allocation mode 2 [6, TS 38.214]

[0073] - Set the "Resource Reservation Period" to the index in the sl-ResourceReservePeriodList corresponding to the reservation period provided by higher layers [11, TS 38.321], provided that the UE is provided with sl-MultiReserveResource

[0074] - The values of the frequency resource allocation field and the time resource allocation field indicate N resources from a resource set {R as described in [6, TS 38.214] and selected by the higher layers as described in [11, TS 38.321], where the N smallest time slot indices y y} are such that for 0 ≤ i ≤ N - 1, y0 < y1 < … < yN-1 ≤ y0 + 31, where: i - N = min(N

[0075] , N 所选择 , N max_reserve ), where N 所选择 is the number of resources in the set {R y}, and the time slot indices y i , 0 ≤ j ≤ N 所选择 - 1, are such that and N max_reserve is provided by sl-MaxNumPerReserve

[0076] - Each resource from the resource set {R y} corresponds to L subCH consecutive subchannels and a set of time slots in , where L subCH is the number of subchannels available for PSSCH / PSCCH transmission in a time slot

[0077] - is the set of time slots in the sidelink resource pool [6, TS 38.214]

[0078] - y0 is the index of the time slot in which the PSCCH with SCI format 1-A is transmitted.

[0079] UE settings for transmitting PSCCH with SCI format 1-A using sidelink resource allocation mode 1 [6, TS 38.214]

[0080] - The values of the frequency resource allocation field and the time resource allocation field for SCI format 1-A transmitted in the mth resource for PSCCH / PSSCH transmission provided by a dynamic grant or by an SL configured grant, where m = {1,..., M} and M is the total number of resources for PSCCH / PSSCH transmission provided by a dynamic grant or the number of resources for PSCCH / PSSCH transmission in a period provided by an SL configured grant type 1 or an SL configured grant type 2, are as follows:

[0081] - The frequency resource allocation field and the time resource allocation field indicate the mth to the Mth resources, as described in [6, TS 38.214].

[0082] For decoding of SCI format 1-A, the UE may assume that the number of bits provided by sl-NumReservedBits may have any value as described in [4, TS 38.212].

[0083] 16.5 UE Procedure for Reporting HARQ-ACK on Uplink

[0084] A PUCCH resource or a PUSCH resource [12, TS 38.331] may be provided to the UE to report HARQ-ACK information generated by the UE based on HARQ-ACK information obtained by the UE from PSFCH reception or from the absence of PSFCH reception. The UE reports HARQ-ACK information for the primary cell of the PUCCH group of the cell, as described in clause 9, where the UE monitors the PDCCH for detection of DCI format 3_0.

[0085] For SL configured granted Type 1 or Type 2 PSSCH transmissions by the UE during the time period provided by sl-PeriodCG, the UE generates a HARQ-ACK information bit in response to PSFCH reception for multiplexing in the PUCCH transmission occasion after the last resource in the time resource set.

[0086] For PSSCH transmissions scheduled by DCI format 3_0, the UE generates HARQ-ACK information in response to PSFCH reception for multiplexing in PUCCH transmission occasions that are after the last time resource in the set of time resources provided by DCI format 3_0.

[0087] Based on the number of PSFCH reception occasions, the UE generates HARQ-ACK information to report in the PUCCH or PUSCH transmission. When applicable, the UE may be instructed by the SCI format to perform one of the following and the UE uses the HARQ-ACK information to construct the HARQ-ACK codeword

[0088] - For one or more PSFCH reception occasions associated with SCI format 2-A with a broadcast type indicator field value of "10"

[0089] - Generate HARQ-ACK information having the same value as the value of the HARQ-ACK information determined by the UE based on the number of PSFCH reception occasions corresponding to the PSSCH transmission receiving the last PSFCH, or generate NACK if the UE determines that the PSFCH was not received in the last PSFCH reception occasion and ACK was not received in any of the previous PSFCH reception occasions

[0090] …

[0091] - For one or more PSFCH reception occasions associated with SCI format 2-B or SCI format 2-A with a broadcast type indicator field value of "11"

[0092] - An ACK is generated when the UE determines from the number of PSFCH reception occasions corresponding to the PSSCH transmission that there is no PSFCH reception for the last PSFCH reception occasion; otherwise, a NACK is generated

[0093] After the UE transmits PSSCH in the corresponding PSFCH resource occasion and receives PSFCH, the priority value of the HARQ-ACK information is the same as the priority value of the PSSCH transmission, and the priority value of the PSSCH transmission is associated with the PSFCH reception occasion providing the HARQ-ACK information.

[0094] When a NACK is generated due to prioritization, as described in clause 16.2.4, the UE is not in any PSFCH reception occasion associated with a PSSCH transmission in resources provided by DCI format 3_0, or is not receiving PSFCH in resources provided in a single cycle for which a configured grant is provided, and for which the UE provides PUCCH resources to report HARQ-ACK information. The priority value of the NACK is the same as the priority value of the PSSCH transmission.

[0095] When the UE does not transmit PSSCH in any resource provided by DCI format 3_0, or in any resource provided in a single cycle for a configured grant, due to priority sorting as described in clause 16.2.4, the UE generates a NACK, and the UE provides PUCCH resources for it to report HARQ-ACK information. The priority value of the NACK is the same as the priority value of the PSSCH that was not transmitted due to priority sorting.

[0096] If the UE does not transmit a PSCCH with SCI format 1-A that schedules PSSCH in any resource provided by a configured grant in a single period, the UE generates an ACK for which the UE provides PUCCH resources to report HARQ-ACK information. The priority value of the ACK is the same as the maximum priority value among the possible priority values ​​for the configured grant.

[0097] If the UE does not transmit a PSCCH with SCI format 1-A scheduling PSSCH in any resource provided by DCI format 3_0, the UE generates an ACK for which the UE provides PUCCH resources to report HARQ-ACK information. The priority value of the ACK is the same as the maximum priority value among the possible priority values ​​for dynamic grants.

[0098] In order to report HARQ-ACK information corresponding to one or more PSSCH transmissions on the uplink in the corresponding SCI format, where the field 'HARQ feedback enable / disable indicator' is set to disabled, the UE generates HARQ-ACK information with the content indicated by the higher layer. The priority value of the HARQ-ACK information is the same as the priority value of the PSSCH transmission.

[0099] In [3] 3GPP TS 38.214 V17.6.0 (2023-06), the following details are provided.

[0100] 5.1.5 Quasi-co-location of antenna ports

[0101] The UE may be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode the PDSCH based on a detected PDCCH with DCI intended for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for configuring a quasi-co-location relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS ports of the PDCCH, or the CSI-RS ports of the CSI-RS resources. The quasi-co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS and the higher layer parameter qcl-Type2 for the second DL RS (if configured). In the case of two DL RSs, the QCL type will be different, regardless of whether the reference is to the same DL RS or different DL RSs. The quasi-co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can take one of the following values:

[0102] - 'Type A': {Doppler shift, Doppler spread, average delay, delay spread}

[0103] - 'Type B': {Doppler shift, Doppler spread}

[0104] - 'Type C': {Doppler shift, average delay}

[0105] - 'Type D': {Spatial Rx Parameters}

[0106] The UE may be configured with a list of up to 128 TCI-State configurations within the higher layer parameter dl-OrJointTCI-StateList in PDSCH-Config for providing quasi-co-located reference signals for the DM-RS of the PDSCH and the DM-RS of the PDCCH in a CC, for CSI-RS, and, where applicable, for determining the UL TX spatial filter for PUSCH and PUCCH resources and SRS in the CC based on dynamic grants and configured grants.

[0107] If the TCI-State or TCI-UL-State configuration does not exist in the BWP of the CC, the UE may apply the TCI-State or TCI-UL-State configuration from the reference BWP of the reference CC. If the UE is configured with dl-OrJointTCI-StateList or UL-TCIState in any CC in the band, the UE is not expected to be configured with TCI-State, SpatialRelationInfo or PUCCH-SpatialRelationInfo in CCs in the same band, except SpatialRelationInfoPos. The UE may assume that when the UE is configured with TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16 or simultaneousSpatial-UpdatedList2-r16, the UE is not configured with DLorJointTCIState or ul-TCI-StateList in any CC in the same band in the CC list.

[0108] …

[0109] 5.1.5 Quasi-co-location of antenna ports

[0110] The UE may be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode the PDSCH based on a detected PDCCH with DCI intended for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for configuring a quasi-co-location relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS ports of the PDCCH, or the CSI-RS ports of the CSI-RS resources. The quasi-co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS and the higher layer parameter qcl-Type2 for the second DL RS (if configured). In the case of two DL RSs, the QCL type will be different, regardless of whether the reference is to the same DL RS or different DL RSs. The quasi-co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can take one of the following values:

[0111] - 'Type A': {Doppler shift, Doppler spread, average delay, delay spread}

[0112] - 'Type B': {Doppler shift, Doppler spread}

[0113] - 'Type C': {Doppler shift, average delay}

[0114] - 'Type D': {Spatial Rx Parameters}

[0115] The UE may be configured with a list of up to 128 TCI-State configurations within the higher layer parameter dl-OrJointTCI-StateList in PDSCH-Config for providing quasi-co-located reference signals for the DM-RS of the PDSCH and the DM-RS of the PDCCH in a CC, for CSI-RS, and, where applicable, for determining the UL TX spatial filter for PUSCH and PUCCH resources and SRS in the CC based on dynamic grants and configured grants.

[0116] If the TCI-State or TCI-UL-State configuration does not exist in the BWP of the CC, the UE may apply the TCI-State or TCI-UL-State configuration from the reference BWP of the reference CC. If the UE is configured with dl-OrJointTCI-StateList or UL-TCIState in any CC in the band, the UE is not expected to be configured with TCI-State, SpatialRelationInfo or PUCCH-SpatialRelationInfo in CCs in the same band, except SpatialRelationInfoPos. The UE may assume that when the UE is configured with TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16 or simultaneousSpatial-UpdatedList2-r16, the UE is not configured with DLorJointTCIState or ul-TCI-StateList in any CC in the same band in the CC list.

[0117] …

[0118] If the UE receives a higher layer configuration of dl-OrJointTCI-StateList with a single TCI-State that can be used as the indicated TCI state, the UE obtains the QCL assumption from the configured TCI states for the DM-RS for the PDSCH and the DM-RS for the PDCCH, and the CSI-RS to which the indicated TCI state is applied.

[0119] If the UE receives a higher layer configuration of a dl-OrJointTCI-StateList with a single TCI-State or a ul-TCI-StateList with a single TCI-UL-State that can be used as the indicated TCI state, the UE determines the ULTX spatial filter (if applicable) from the configured TCI states of PUSCH and PUCCH based on the dynamic grant and configured grant, and the SRS to which the indicated TCI state is applied.

[0120] When a UE configured with dl-OrJointTCI-StateList is to transmit a PUCCH with positive HARQ-ACK or a PUSCH with positive HARQ-ACK corresponding to a DCI carrying a TCI state indication and without DL assignment or corresponding to a PDSCH scheduled by a DCI carrying a TCI state indication, and if the indicated TCI state is different from the previously indicated one, the indicated TCI-State and / or TCI-UL-State shall apply starting from the first slot of at least the beamAppTime symbol after the last symbol of the PUCCH or PUSCH. Both the first slot and the beamAppTime symbol are determined on the active BWP, where the minimum SCS among the BWPs from the CC applies the indicated TCI-State or TCI-UL-State active at the end of the PUCCH or PUSCH carrying positive HARQ-ACK.

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

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

[0123] 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.

[0124] …

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

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

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

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

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

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

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

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

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

[0134] …

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

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

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

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

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

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

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

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

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

[0144] - If the 'offer / request indicator' indicates that SCI format 2-C is used to deliver an explicit request for inter-UE coordination information, then:

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

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

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

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

[0149] - 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.

[0150] - If the 'offer / request indicator' indicates that SCI format 2-C is used to deliver inter-UE coordination information, then:

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

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

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

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

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

[0156] 8.1.2 Resource Allocation

[0157] In sidelink resource allocation mode 1:

[0158] - 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.

[0159] 8.1.2.1 Resource Allocation in the Time Domain

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

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

[0162] In sidelink resource allocation mode 1:

[0163] -For sidelink dynamic grant, PSSCH transmission is scheduled by DCI format 3_0.

[0164] - For sidelink configured grant type 2, the configured grant is activated by DCI format 3_0.

[0165] - For Sidelink Dynamic Grant and Sidelink Configured Grant Type 2:

[0166] - The "Time Slot" field value m of DCI format 3_0 provides index m+1 into the slot offset table. The table is given by the higher layer parameter sl-DCI-ToSL-Trans, and the table value at index m+1 will be referred to as the slot offset K SL .

[0167] - The time slot of the first sidelink transmission scheduled by DCI is the first SL time slot of the corresponding resource pool, which starts no earlier than Where TDL is the start time of the downlink time slot carrying the corresponding DCI, T TA is the timing advance value of the TAG corresponding to the serving cell on which the DCI is received, K SL is the time slot offset between the time slot of the DCI and the first side link transmission scheduled by the DCI, and T 时隙 is the SL time slot duration.

[0168] - The "Configuration Index" field of DCI format 3_0 (if provided and non-reserved) indicates the index of the sidelink configured type 2.

[0169] - For sidelink configured grant type 1:

[0170] - The time slots of the first sidelink transmission follow the higher layer configuration according to [10, TS 38.321].

[0171] 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

[0172] In resource allocation mode 2, higher layers may request the UE to determine the resource subset 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:

[0173] - the resource pool from which the resource will be reported;

[0174] -L1 priority, prio TX ;

[0175] - Remaining packet delay budget;

[0176] - The number of subchannels to be used for PSSCH / PSCCH transmission in a slot, L subCH ;

[0177] - Optionally, a resource reservation interval, P rsvD_TX , in milliseconds.

[0178] …

[0179] - Optionally, instructions from a resource selection authority.

[0180] The following higher-level parameters affect this procedure:

[0181] -sl-SelectionWindowList: internal parameter T 2min is set to the given value prio TX The corresponding value from the higher-layer parameter sl-SelectionWindowList.

[0182] -sl-Thres-RSRP-List: This higher layer parameter is for each combination (p i , p j ) provides the RSRP threshold, where p i is the value of the priority field in the received SCI format 1A, and p j is the priority of the UE's transmission for selecting resources; for a given invocation of this procedure, p j =prio TX .

[0183] - If the UE uses PSSCH-RSRP or PSCCH-RSRP measurement, then sl-RS-ForSensing is selected as defined in clause 8.4.2.1.

[0184] -sl-ResourceReservePeriodList

[0185] -sl-SensingWindow: The internal parameter T0 is defined as the number of time slots corresponding to the sl-SensingWindow in milliseconds

[0186] -sl-TxPercentageList: for a given prio TX The internal parameter X is defined as sl-TxPercentageList(prio) which converts from percentage to ratio. TX )

[0187] Resource reservation interval P rsvp_TX (if provided) Convert from milliseconds to logical slots, yielding P′ according to clause 8.1.7 rsvp_TX .

[0188] When the resource pool is (pre-)configured with sl-AllowedResourceSelectionConfig including full sensing and full sensing is configured in the UE by higher layers, the UE performs full sensing.

[0189] When periodic reservation for another TB (sl-MultiReserveResource) is enabled for a resource pool, the resource pool is (pre-)configured with an allowedResourceSelectionConfig including partial sensing, and partial sensing is configured by higher layers, the UE performs periodic based partial sensing, unless other conditions state otherwise in the specification.

[0190] annotation:

[0191] Represents the set of time slots belonging to the sidelink resource pool and defined in clause 8.

[0192] Use the following steps:

[0193] 1) Candidate single-slot resources R for PSSCH transmission x，y Defined as L subCH A set of consecutive subchannels, where subchannel x+j is in time slot where j = 0, ..., L subCH -1. The UE shall assume that any L subCH When the Y consecutive subchannel sets are included in the corresponding resource pool in the time interval [n+T1, n+T2], it corresponds to a candidate single time slot resource for the UE to perform full sensing. When the Y consecutive subchannel sets are included in the corresponding resource pool in the time interval [n+T1, n+T2], it corresponds to a candidate single time slot resource for the UE to perform periodic partial sensing and continuous partial sensing and resource (re)selection triggered by periodic transmission (P rsvp_TX ≠0), or a candidate single-slot resource (P) in a set of Y′ candidate time slots within the time interval [n+T1, n+T2] corresponding to a resource (re)selection for which the UE performs at least continuous partial sensing and is triggered by aperiodic transmission rsvp_TX =0), where

[0194] -The choice of T1 depends on the UE The implementation of The time slots are defined in Table 8.1.4-2, where μS L It is the SCS configuration of SL BWP;

[0195] -If T 2min shorter than the remaining packet delay budget (in time slots), then T2 depends on the UE’s 2min ≤ T2 ≤ Remaining Packet Delay Budget (in time slots); otherwise T2 is set to the Remaining Packet Delay Budget (in time slots).

[0196] …

[0197] The total number of candidate single-slot resources is denoted as M total

[0198] 2) The sensing window consists of the time slot range when the UE performs full sensing Definition, where T0 is defined above, and The time slots are defined in Table 8.1.4-1, where μ SLis the SCS configuration of the SL BWP. The UE shall monitor the slots belonging to the sidelink resource pool within the sensing window, except for the slots in which its own transmission occurs. The UE shall perform the actions in the subsequent steps based on the decoded PSCCH and the measured RSRP in these slots.

[0199] …

[0200] If (pre)configured, then P 预留 The value of corresponds to sl-PBPS-OccasionReservePeriodList, otherwise, the value corresponds to all periodicities from sl-ResourceReservePeriodList.

[0201] …

[0202] 3) Internal parameter Th(p i , p i ) is set to the corresponding value of the RSRP threshold indicated by the i-th field in sl-Thres-RSRP-List, where i=p i +(p j -1)*8.

[0203] 4) Set S A is initialized to the set of all candidate single-slot resources.

[0204] 5) If the UE meets all of the following conditions, the UE will exclude the UE from the set S A Any candidate single-slot resource R x，y :

[0205] - In step 2, the UE has not yet monitored the time slot

[0206] - Any periodicity value allowed for the higher layer parameter sl-ResourceReservePeriodList and in the time slot The hypothetical SCI format 1-A received in , in which the 'resource reservation period' field is set to the periodicity value and indicates that all sub-channels of the resource pool in this time slot will satisfy condition c in step 6.

[0207] 5a) If the set S A The remaining candidate single-slot resources R x，y The number is less than X·M 总 , then the set S A Initialized to the set of all candidate single-slot resources as in step 4.

[0208] 6) If the UE meets all of the following conditions, the UE will exclude the UE from the set S A Any candidate single-slot resource Rx，y :

[0209] a)UE in time slot The SCI format 1-A is received in the received SCI format 1-A, and according to clause 16.4 in [6, TS 38.213], the 'resource reservation period' field (if present) and the 'priority' field in the received SCI format 1-A indicate the value P respectively. rsvp_RX and prio RX ;

[0210] b) According to clause 8.4.2.1, the RSRP measurement performed for the received SCI format 1-A is higher than Th(prio RX , prio TX );

[0211] c) In time slot or if and only if the 'Resource Reservation Period' field is present in the received SCI format 1-A, it is assumed that the resource reservation period is in the time slot The same SCI format received in the received SCI format determines the resource block set and its overlapping time slots according to clause 8.1.5, where for q=1, 2, ..., Q and j=0, 1, ..., C resel -1, Here, P′ rsvp_RX According to the terms

[0212] 8.1.7 is converted into P in logical time slots rsvp_RX , if P rsvp_RX <T scal And n′-m≤P′ rsvp_RX ,but Wherein, in the case where the UE is configured with full sensing via its higher layers, if time slot n belongs to the set but Otherwise the time slot For time slot n, it belongs to the set The first time slot after; ... If the UE is configured with full sensing through its higher layers, then T scal is set to convert the selected window size T2 into milliseconds...

[0213] 6a) This step is only performed if the procedure in clause 8.1.4A is triggered.

[0214] 6b) This step is only performed if the procedure in clause 8.1.4C is triggered.

[0215] 7) If the set S A The number of candidate single-slot resources remaining in 总 , then for each priority value Th(pi , p j ), Th(p i , p j ) is increased by 3dB, and the procedure continues with step 4.

[0216] …

[0217] The UE shall report the set S to higher layers A .

[0218] …

[0219] …

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

[0221] 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 allocation', 'Time resource allocation' of the associated SCI format 1-A, as described below.

[0222] The 'Time Resource Assignment' carries a logical slot offset indication of N=1 or 2 actual resources when sl-MaxNumPerReserve is 2, and carries a logical slot offset indication of N=1 or 2 or 3 actual resources when sl-MaxNumPerReserve is 3, in the form of a Time RIV (TRIV) field, determined as follows:

[0223] If N = 1

[0224] TRIV=0

[0225] Otherwise if N=2

[0226] TRIV=t1

[0227] otherwise

[0228] If (t2-t1-1)≤15

[0229] TRIV=30(t2-t1-1)+t1+31

[0230] otherwise

[0231] TRIV=30(31-t2+t1)+62-t1

[0232] End the if loop

[0233] End the if loop

[0234] The first resource is in the time slot where SCI format 1-A is received, and t iIndicates the i-th resource time offset relative to the first resource in the logical time slot of the resource pool, where for N = 2, 1 ≤ t1 ≤ 31; and for N = 3, 1 ≤ t1 ≤ 30, t1 < t2 ≤ 31.

[0235] Determine the starting subchannel of the first resource according to Clause 8.1.2.2 For the number L of consecutive allocated subchannels for each of the N resources subCH ≥ 1 and the starting subchannel index of the resources indicated by the received SCI format 1-A (except for the resources in the time slot where SCI format 1-A is received) are determined by the "Frequency Resource Assignment" equal to the frequency RIV (FRIV), where

[0236] If sl-MaxNumPerReserve is 2, then

[0237]

[0238] If sl-MaxNumPerReserve is 3, then

[0239]

[0240] Where

[0241] - Indicates the starting subchannel index of the second resource

[0242] - Indicates the starting subchannel index of the third resource

[0243] - Is the number of subchannels in the resource pool provided according to the higher layer parameter sl-NumSubchannel

[0244] If the TRIV indicates N < sl-MaxNumPerReserve, the starting subchannel indices corresponding to the last sl-MaxNumPerReserve minus N resources are not used.

[0245] The number of time slots in a time and frequency resource set of the transmission opportunity of the PSSCH is given by C resel Given, where C resel = 10 * SL_RESOURCE-RESELECTION_COUNTER[10, TS 38.321] (if configured), otherwise C resel Is set to 1.

[0246] If the time slot The subchannel set in is determined as the time and frequency resources corresponding to the PSSCH transmission of the selected sidelink grant (described in [10, TS38.321]), then the time slot The same subchannel set in is also determined for PSSCH transmission corresponding to the same sidelink grant, where j=1, 2, ..., C resel -1, according to clause 8.1.7, P rsvp_TX (if provided) Convert from milliseconds to logical time slots, yielding P' rsvp_TX ,and Determined by clause 8. Here, P rsvp_TX is the resource reservation interval indicated by higher layers.

[0247] …

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

[0249] For sidelink resource allocation mode 1, after detecting SCI format 1-A on PSCCH, the UE can 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.

[0250] For sidelink resource allocation mode 2, after detecting SCI format 1-A on PSCCH, the UE can 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.

[0251] 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.

[0252] In [4] 3GPP TS 38.331 V17.0.0 (2022-03), parameters related to the side link are referenced below.

[0253] 6.3.5 Sidelink Information Elements

[0254] -SL-BWP-Config

[0255] IESL-BWP-Config is used to configure UE-specific NR sidelink communication on a specific sidelink bandwidth portion.

[0256] SL-BWP-Config Information Elements

[0257]

[0258]

[0259]

[0260]

[0261] -SL-BWP-PoolConfig

[0262] IE SL-BWP-PoolConfig is used to configure the NR side link communication resource pool.

[0263] SL-BWP-PoolConfig Information Element

[0264]

[0265]

[0266]

[0267] -SL-ConfigDedicatedNR

[0268] IE SL-ConfigDedicatedNR specifies dedicated configuration information for NR side link communication.

[0269] SL-ConfigDedicatedNR Information Element

[0270]

[0271]

[0272]

[0273]

[0274] -SL-ConfiguredGrantConfig

[0275] IESL-ConfiguredGrantConfig specifies the configured grant configuration information for NR sidelink communication.

[0276] SL-ConfiguredGrantConfig Information Element

[0277]

[0278]

[0279]

[0280] IE SL-LogicalChannelConfig is used to configure the side link logical channel parameters.

[0281] SL-LogicalChannelConfig Information Element

[0282]

[0283]

[0284]

[0285] In [5] 3GPP TS 38.212 V17.5.0 (2023-06), the following details are provided.

[0286] 7.3.1.4 DCI format for scheduling sidelink

[0287] 7.3.1.4.1 Format 3_0

[0288] DCI format 3_0 is used for scheduling NR PSCCH and NR PSSCH in one cell.

[0289] The following information is transmitted by means of DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI:

[0290] - Resource pool index bits, where I is the total number of resource pools used for transmission as configured by higher layer parameters sl-TxPoolScheduling (if configured) and sl-DiscTxPoolScheduling (if configured).

[0291] - Time gap - 3 bits determined by the higher layer parameter sl-DCI-ToSL-Trans, as defined in clause 8.1.2.1 of [6, TS 38.214]

[0292] -HARQ process number - 4 bits.

[0293] - New data indicator - 1 bit.

[0294] - The latest index of the subchannel assigned to the initial transmission - as defined in [6, TS 38.214] clause 8.1.2.2 Bit

[0295] - SCI Format 1-A field according to clause 8.3.1.1:

[0296] - Frequency resource assignment.

[0297] -Time resource allocation.

[0298] -PSFCH to HARQ feedback timing indicator bits, where N fb_timing is the number of entries in the higher layer parameter sl-PSFCH-ToPUCCH as defined in clause 16.5 of [5, TS 38.213]

[0299] - PUCCH resource indicator - 3 bits, as defined in clause 16.5 of [5, TS 38.213].

[0300] - Configuration Index - 0 bit if the UE is not configured to listen to DCI format 3_0 with CRC scrambled by SL-CS-RNTI, otherwise 3 bits as defined in clause 8.1.2 of [6, TS 38.214]. If the UE is configured to listen to DCI format 3_0 with CRC scrambled by SL-CS-RNTI, this field is reserved for DCI format 3_0 with CRC scrambled by SL-RNTI.

[0301] - Reverse Side Link Allocation Index - 2 bits

[0302] - 2 bits if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic, as defined in clause 16.5.2 of [5, TS38.213]

[0303] - 2 bits if the UE is configured to use pdsch-HARQ-ACK-Codebook = semi-static, as defined in clause 16.5.1 of [5, TS38.213]

[0304] - Filling positions (if necessary)

[0305] …

[0306] 8.3 Sidelink Control Information on PSCCH

[0307] The SCI carried on the PSCCH is a level 1 SCI, which conveys sidelink scheduling information.

[0308] 8.3.1.1 SCI Format 1-A

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

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

[0311] - 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.

[0312] - Frequency Resource Allocation - bit, then the value of the higher layer parameter sl-MaxNumPerReserve is configured as 2; otherwise, the frequency resource allocation - bit, in which case the value of the higher layer parameter sl-MaxNumPerReserve is configured to be 3, as defined in clause 8.1.5 of [6, TS 38.214].

[0313] - 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].

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

[0315] …

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

[0317] …

[0318] -Conflict message receiver flag - 0 or 1 bit

[0319] - 1 bit if the higher layer parameter sl-IndicationUE-B is configured to 'enabled', where a bit value of 0 indicates that the UE cannot be a UE that receives conflicting information and a bit value of 1 indicates that the UE can be a UE that receives conflicting information, as defined in clause 16.3.0 of [5, TS 38.213];

[0320] -Otherwise 0 bit.

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

[0322]

[0323] Table 8.3.1.1-2: Mapping of Beta_offset indicator values ​​to indices in Table 9.3-2 of [5, TS38.213]

[0324]

[0325] …

[0326] 8.4.1.1 SCI Format 2-A

[0327] 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.

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

[0329] -HARQ process number - 4 bits.

[0330] - New data indicator - 1 bit.

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

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

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

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

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

[0336] - 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].

[0337] Table 8.4.1.1-1: Broadcast type indicator

[0338]

[0339] In [6] 3GPP TS 38.321 V17.4.0 (2023-03), the following details are provided.

[0340] 5.18.23 Unified TCI status activation / deactivation of MAC CE

[0341] The network may activate and deactivate the configured unified TCI state of a serving cell or a serving cell set configured in simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4 by sending a unified TCI state activation / deactivation MAC CE described in clause 6.1.3.47. The configured unified TCI state is first deactivated when (re)configured by upper layers and after reconfiguration with synchronization.

[0342] The MAC entity will:

[0343] 1> If the MAC entity receives a unified TCI state activation / deactivation MAC CE on the serving cell:

[0344] 2> Indicates information about unified TCI state activation / deactivation MAC CE to lower layers.

[0345] …

[0346] 6.1.3.47 Unified TCI status activation / deactivation of MAC CE

[0347] The Unified TCI State Activation / Deactivation MAC CE is identified by a MAC subheader with the eLCID as specified in Table 6.2.1-1b. It has a variable size and consists of the following fields:

[0348] - Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells in the set simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4, respectively;

[0349] -DL BWP ID: This field indicates the DL BWP used by the MAC CE as the code point for the DCI Bandwidth Part Indicator field, as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits;

[0350] -UL BWP ID: This field indicates the UL BWP used by the MAC CE as the code point of the DCI bandwidth part indicator field, as specified in TS 38.212 [9]. If the value of the unifiedTCI-StateType of the serving cell indicated by the serving cell ID is unified, this field is considered reserved. The length of the BWP ID field is 2 bits;

[0351] -P i : This field indicates whether each TCI code point has multiple TCI states or a single TCI state. i The P field is set to 1, which indicates that the ith TCI code point contains both DL TCI status and UL TCI status. i If the field is set to 0, it indicates that the i-th TCI code point contains only DL / Joint TCI state or UL TCI state. The code point of the mapped TCI state is determined by its ordinal position among all TCI state ID fields;

[0352] - D / U: This field indicates whether the TCI State ID in the same octet is for the joint / downlink or uplink TCI state. If this field is set to 1, the TCI State ID in the same octet is for the joint / downlink. If this field is set to 0, the TCI State ID in the same octet is for the uplink;

[0353] -TCI State ID: This field indicates the TCI state identified by TCI-StateId as specified in TS 38.331 [5]. If D / U is set to 1, the 7-bit length TCI State ID, i.e., TCI-StateId, as specified in TS 38.331 [5] is used. If D / U is set to 0, the most significant bit of the TCI State ID is considered as a reserved bit, and the remaining 6 bits indicate the TCI-UL-State-Id as specified in TS 38.331 [5]. The maximum number of activated TCI states is 16;

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

[0355] Figure 5 It is from 3GPP 38.321v17.4.0(2023-03) Figure 6.1.3.47-1: Unified TCI state activation / deactivation of MAC CE reproduction.

[0356] …

[0357] 6.1.3.33 Sidelink Buffer Status Report MAC CE

[0358] The Sidelink Buffer Status Report (SL-BSR) MAC CE consists of either:

[0359] -SL-BSR format (variable size); or

[0360] - Truncated SL-BSR format (variable size).

[0361] The SL-BSR and Truncated SL-BSR MAC control elements consist of one Destination Index field, one LCG ID field and a corresponding buffer size field per reporting target group.

[0362] The SL-BSR format is identified by a MAC subheader with an LCID as specified in Table 6.2.1-2.

[0363] The fields in the SL-BSR MAC CE are defined as follows:

[0364] - Destination Index: The Destination Index field identifies the destination. This field is 5 bits in length. The value is set to an index corresponding to the SL Destination Identity associated to the same destination reported in sl-TxResourceReqList, sl-TxResourceReqListDisc and sl-TxResourceReqListCommRelay (if present). The values ​​are indexed sequentially from 0 in the same ascending order of the SL Destination Identity in sl-TxResourceReqList, sl-TxResourceReqListDisc and sl-TxResourceReqListCommRelay, as specified in TS 38.331 [5]. When multiple lists are reported, the values ​​are indexed sequentially across all lists in the same order as presented in the SidelinkUEInformaitonNR message;

[0365] -LCG ID: The Logical Channel Group ID field identifies the group of logical channels for which the SL buffer status is being reported. The length of the field is 3 bits;

[0366] - Buffer Size: The Buffer Size field identifies the total amount of data available for all logical channels of the destination's logical channel group after the MAC PDU has been constructed (i.e., after the logical channel prioritization procedure, which may result in the value of the Buffer Size field being zero) according to the data amount calculation procedure in TS 38.322 [3] and 38.323 [4]. The amount of data is indicated in number of bytes. The size of the RLC header and MAC sub-header is not considered in the buffer size calculation. The length of this field is 8 bits. The values ​​of the Buffer Size field are shown in Table 6.1.3.1-2, respectively. For the truncated SL-BSR format, the number of included Buffer Size fields is maximized without exceeding the number of padding bits.

[0367] The buffer sizes of the LCGs are contained in descending order of highest priority of the sidelink logical channels that have data available for transmission in each of the LCGs, regardless of the value of the Destination Index field.

[0368] Note: empty.

[0369] Figure 6 It is from 3GPP TS 38.321V17.4.0(2023-03) Figure 6 .1.3.33-1: Reproduction of SL-BSR and truncated SL-BSR MAC control elements.

[0370] …

[0371] 5.22SL-SCH data transmission

[0372] 5.22.1 SL-SCH data transmission

[0373] 5.22.1.1 SL Grant Receipt and SCI Transmission

[0374] The sidelink grant is received dynamically on the PDCCH, semi-statically configured by the RRC or autonomously selected by the MAC entity. The MAC entity will have the sidelink grant on the active SL BWP to determine the set of PSSCH durations in which transmissions of the SCI occur, and the set of PSSCH durations in which transmissions of the SL-SCH associated with the SCI occur. A sidelink grant addressed to a SLCS-RNTI with NDI=1 is considered a dynamic sidelink grant.

[0375] If the MAC entity has been configured to use sidelink resource allocation mode 1, as indicated in TS 38.331 [5], then the MAC entity shall, for each PDCCH occasion and for each grant received for this PDCCH occasion:

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

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

[0378] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration for one or more retransmissions of a single MAC PDU for the corresponding sidelink process according to clause 8.1.2 of TS 38.214 [7].

[0379] 2> Otherwise:

[0380] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration for initial transmission and (if applicable) retransmission of a single MAC PDU according to clause 8.1.2 of TS 38.214 [7].

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

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

[0383] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration for one or more retransmissions of a single MAC PDU according to clause 8.1.2 of TS 38.214 [7].

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

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

[0386] 2> else if the PDCCH content indicates a configured grant type 2 activation for a configured sidelink grant:

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

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

[0389] 3> Initialize or reinitialize the configured sidelink grant to determine the PSCCH duration set and the PSSCH duration set for transmission of multiple MAC PDUs according to clause 8.1.2 of TS 38.214 [7].

[0390] 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:

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

[0392] If the MAC entity has been configured with sidelink resource allocation mode 2 to transmit using a resource pool in a 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, the MAC entity shall for each sidelink process:

[0393] …

[0394] 1> If the MAC entity has been selected to create a selected sidelink grant corresponding to the transmission of multiple MAC PDUs, and SL data is available in the logical channel:

[0395] 2> If the MAC entity has not yet selected a resource pool to allow for the logical channel:

[0396] …

[0397] 3> Otherwise if sl-HARQ-FeedbackEnabled is set to enabled for the logical channel:

[0398] 4> If configured, select any resource pool configured with PSFCH resources among the resource pools, except the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

[0399] 3> Otherwise:

[0400] 4> If configured, select any resource pool among the resource pools, except the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

[0401] 2> Perform TX resource (re)selection check on the selected resource pool as specified in clause 5.22.1.2;

[0402] …

[0403] 3> with equal probability in interval [5, 15] for resource reservation intervals above or equal to 100 ms or in interval [5, 15] for resource reservation intervals below 100 ms A random integer value is selected from and SL_RESOURCE_RESELECTION_COUNTER is set to the selected value;

[0404] 3> The number of HARQ retransmissions is selected from the allowed number in sl-MaxTxTransNumPSSCH contained in sl-PSSCH-TxConfigList (if configured by RRC), and if configured by RRC, the allowed number overlaps in sl-MaxTxTransNumPSSCH indicated in sl-CBR-PriorityTxConfigList for the highest priority logical channel allowed on the carrier and the CBR measured according to clause 5.1.27 of TS 38.215

[24] (if CBR measurement results are available) or the corresponding sl-defaultTxConfigIndex configured by RRC (if CBR measurement results are not available);

[0405] 3> select an amount of frequency resources that is within the range configured by RRC between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH contained in sl-PSSCH-TxConfigList and, if configured by RRC, overlaps between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH indicated in sl-CBR-PriorityTxConfigList for the highest priority of the allowed logical channel(s) on the carrier and the CBR measured by the lower layers according to clause 5.1.27 of TS 38.215

[24] (if CBR measurement results are available) or the corresponding sl-defaultTxConfigIndex configured by RRC (if CBR measurement results are not available);

[0406] 3> If sl-InterUE-CoordinationScheme1 that enables reception / transmission of preferred resource sets and non-preferred resource sets is not configured by RRC:

[0407] 4> If the upper layer configuration is based on random selection transmission:

[0408] 5> Randomly select the time and frequency resources for a transmission opportunity from a resource pool occurring within the SL DRX active time of the destination UE as specified in clause 5.28.2, based on the amount of selected frequency resources and the remaining PDBs of SL data available in the logical channels allowed on the carrier, and the destination UE is selected to indicate the above-mentioned SL DRX active time to the physical layer.

[0409] 4> Otherwise:

[0410] 5> Randomly select the time and frequency resources for a transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] occurring within the SL DRX action time of the destination UE as specified in clause 5.28.2, based on the amount of frequency resources selected and the remaining PDBs of SL data available in the logical channels allowed on the carrier, the destination UE being selected to indicate the above-mentioned SL DRX action time to the physical layer.

[0411] 3> If sl-InterUE-CoordinationScheme1 enabling reception / transmission of preferred resource sets and non-preferred resource sets is configured by RRC and the preferred resource set is not received from the UE:

[0412] 4> If the upper layer configuration is based on random selection transmission:

[0413] 5> Randomly select the time and frequency resources for one transmission opportunity from the resource pool based on the amount of selected frequency resources and the remaining PDB of SL data available in the allowed logical channels on the carrier.

[0414] 4> Otherwise:

[0415] 5> Randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] based on the amount of selected frequency resources and the remaining PDBs of SL data available in the allowed logical channels on the carrier.

[0416] 3> If sl-InterUE-CoordinationScheme1 enabling reception / transmission of preferred resource sets and non-preferred resource sets is configured via RRC, and when the UE does not have its own sensing results as specified in clause 8.1.4 of TS 38.214 [7], and if a preferred resource set is received from the UE:

[0417] 4> Based on the amount of selected frequency resources and the remaining PDB of SL data available in the logical channels allowed on the carrier, randomly select the time and frequency resources for a transmission opportunity from the resources belonging to the received preferred resource set, and the resources are used for the SL-SCH data to be transmitted to the UE providing the preferred resource set.

[0418] 3> If sl-InterUE-CoordinationScheme1 enabling reception / transmission of preferred resource sets and non-preferred resource sets is configured via RRC, and when the UE has its own sensing results as specified in clause 8.1.4 of clause TS 38.214 [7], and if a preferred resource set is received from the UE:

[0419] 4> Randomly select a time and frequency resource for a transmission opportunity within the intersection of the received preferred resource set and the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], based on the amount of selected frequency resources and the remaining PDB of SL data available in the allowed logical channels on the carrier, wherein the resources indicated by the physical layer are used for the SL-SCH data to be transmitted to the UE providing the preferred resource set.

[0420] 4> If, based on the amount of selected frequency resources and the remaining PDB of SL data available in the logical channels allowed on the carrier, there are no resources within the intersection area that can be selected as time and frequency resources for the one transmission opportunity.

[0421] 5> Randomly select time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] based on the amount of selected frequency resources available in the allowed (multiple) logical channels on the carrier and the remaining PDB for SL data.

[0422] 3> Use randomly selected resources to select a set of periodic resources separated by a resource reservation interval for transmission of PSCCH and PSSCH corresponding to the number of transmission opportunities of the MAC PDU determined in TS 38.214 [7].

[0423] 3> If one or more HARQ retransmissions are selected:

[0424] 4> If sl-InterUE-CoordinationScheme1 that enables reception / transmission of preferred resource sets and non-preferred resource sets is not configured by RRC:

[0425] 5> if transmission based on full sensing or partial sensing is configured by upper layers and leaves available resources for more transmission opportunities in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7]; or

[0426] 5> If random selection based transmission is configured by upper layers and leaves available resources in the resource pool for more transmission opportunities:

[0427] 6> Based on the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channels allowed on the carrier, randomly select from the available resources the time and frequency resources for one or more transmission opportunities occurring within the SL DRX active time as specified in clause 5.28.2 of the destination UE, which is selected to indicate the above-mentioned SL DRX active time to the physical layer, by ensuring a minimum time gap between any two selected resources when the PSFCH is configured for this resource pool and the retransmission resources can be indicated by the time resource assignment of the previous SCI according to clause 8.3.1.1 of TS38.212[9].

[0428] 4> If sl-InterUE-CoordinationScheme1 enabling reception / transmission of preferred resource sets and non-preferred resource sets is configured by RRC and the preferred resource set is not received from the UE:

[0429] 5> if transmission based on full sensing or partial sensing is configured by upper layers and leaves available resources for more transmission opportunities in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7]; or

[0430] 5> If random selection based transmission is configured by upper layers and leaves available resources in the resource pool for more transmission opportunities:

[0431] 6> Based on the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channels allowed on the carrier, time and frequency resources for one or more transmission opportunities are randomly selected from the available resources by ensuring a minimum time gap between any two selected resources when the PSFCH is configured for this resource pool and the retransmission resources are indicated by the time resource assignment of the previous SCI according to clause 8.3.1.1 of TS38.212[9].

[0432] 4> If sl-InterUE-CoordinationScheme1 enabling reception / transmission of preferred resource sets and non-preferred resource sets is configured via RRC, when the UE has its own sensing results as specified in clause 8.1.4 of TS 38.214 [7], and if a preferred resource set is received from the UE:

[0433] 5> If there are available resources for more transmission opportunities in the intersection of the received preferred resource set and the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7]:

[0434] 6> Based on the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channels allowed on the carrier, randomly select time and frequency resources for one or more transmission opportunities from the available resources within the intersection area, the available resources being used for SL-SCH data to be transmitted to the UE providing the preferred resource set, by ensuring a minimum time gap between any two selected resources when the PSFCH is configured for this resource pool and the retransmission resources are indicated by the time resource assignment of the previous SCI according to clause 8.3.1.1 of TS38.212[9].

[0435] 5> If the number of time and frequency resources maximally selected for one or more transmission opportunities from the available resources within the intersection region is less than the selected number of HARQ retransmissions, and there are available resources left for more transmission opportunities in the resources indicated by the physical layer:

[0436] 6> Based on the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channels allowed on the carrier, time and frequency resources for the remaining transmission opportunities are randomly selected from the available resources outside the intersection region but remaining in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7], excluding the selected resources within the intersection region, by ensuring a minimum time gap between any two selected resources when the PSFCH is configured for this resource pool and the retransmission resources are indicated by the time resource assignment of the previous SCI according to clause 8.3.1.1 of TS38.212 [9].

[0437] 4> if sl-InterUE-CoordinationScheme1 enabling reception / transmission of preferred resource sets and non-preferred resource sets is configured via RRC, and when the UE does not have its own sensing results as specified in clause 8.1.4 of TS 38.214 [7], and if a preferred resource set is received from the UE; and

[0438] 4> If there are available resources for more transmission opportunities in the received preferred resource set:

[0439] 5> Based on the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channels allowed on the carrier, randomly select time and frequency resources for one or more transmission opportunities from the available resources belonging to the received preferred resource set, wherein the available resources are used for SL-SCH data to be transmitted to the UE providing the preferred resource set, by ensuring a minimum time gap between any two selected resources when the PSFCH is configured for this resource pool and the retransmission resources are indicated by the time resource assignment of the previous SCI according to clause 8.3.1.1 of TS38.212[9].

[0440] 4> Use randomly selected resources to select a set of periodic resources separated by a resource reservation interval for transmission of PSCCH and PSSCH corresponding to the number of retransmission opportunities of the MAC PDU determined in TS 38.214 [7];

[0441] 4> The first transmission opportunity set is regarded as the initial transmission opportunity, and the other transmission opportunity set is regarded as the retransmission opportunity;

[0442] 4> Consider the set of initial transmit opportunities and retransmit opportunities as the selected sidelink grant.

[0443] 3> Otherwise:

[0444] 4> Treat the set as the selected sidelink grant.

[0445] 3> Determine a set of PSCCH durations and a set of PSSCH durations using the selected sidelink grant according to TS 38.214 [7].

[0446] 2> Otherwise if SL_RESOURCE_RESELECTION_COUNTER = 0, and when SL_RESOURCE_RESELECTION_COUNTER is equal to 1, a MAC entity is randomly selected with equal probability, the probability being a value in the interval [0, 1] and less than or equal to the probability configured by RRC in sl-ProbResourceKeep;

[0447] 3> Clear the selected sidelink grant if applicable;

[0448] 3> with equal probability in interval [5, 15] for resource reservation intervals above or equal to 100 ms or in interval [5, 15] for resource reservation intervals below 100 ms A random integer value is selected from and SL_RESOURCE_RESELECTION_COUNTER is set to the selected value;

[0449] 3> Reuse the previously selected sidelink grant for the number of transmissions of the MAC PDU and the resource reservation interval determined in TS 38.214 [7] to determine the PSCCH duration set and the PSSCH duration set according to TS 38.214 [7].

[0450] …

[0451] …

[0452] 1> If the selected sidelink grant is available for retransmission of a positively acknowledged MAC PDU, as specified in clause 5.22.1.3.3:

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

[0454] 5.22.1.3 Sidelink HARQ Operation

[0455] 5.22.1.3.1 Sidelink HARQ Entity

[0456] …for each sidelink grant, the sidelink HARQ entity shall:

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

[0458] 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

[0459] 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 the PSSCH of the previous sidelink grant are not in the SL DRX active time as specified in clause 5.28.3 of the destination with data to be sent:

[0460] Note 1: Empty.

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

[0462] 2> If all PSCCH durations and PSSCH durations for initial transmission of a dynamic sidelink grant or a MAC PDU for said 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:

[0463] 3> Ignore sidelink grant.

[0464] 2> Otherwise:

[0465] 3> Obtain MAC PDU for transmission from the multiplexing and combining entity (if any);

[0466] 3> If a MAC PDU has been obtained for transmission:

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

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

[0469] 5.22.1.4 Reuse and Assembly

[0470] 5.22.1.4.0 Overview

[0471] For a PDU associated with one SCI, the MAC shall consider only the logical channel with the same source layer 2ID - destination layer 2ID pair for one of unicast, multicast and broadcast associated with the pair.Multiple transmissions for different sidelink processes are allowed to be performed independently in different PSSCH durations.

[0472] 5.22.1.4.1 Logical channel priority sorting

[0473] 5.22.1.4.1.1 Overview

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

[0475] RRC controls the scheduling of sidelink data by transmitting for each logical channel:

[0476] -sl-priority, where increasing priority values ​​indicate lower priority;

[0477] -sl-PrioritisedBitRate, which sets the sidelink prioritized bit rate (sPBR);

[0478] -sl-BucketSizeDuration, which sets the sidelink bucket size duration (sBSD).

[0479] The RRC additionally controls the LCP procedure by configuring mapping restrictions for each logical channel:

[0480] -sl-configuredGrantType1Allowed, which sets whether configured grant type 1 can be used for sidelink transmissions;

[0481] -sl-AllowedCG-List which sets the allowed configured grants for sidelink transmission;

[0482] -sl-HARQ-FeedbackEnabled, which sets whether the logical channel is allowed to be multiplexed with the logical channel if sl-HARQ-FeedbackEnabled is set to enabled or disabled.

[0483] …

[0484] 5.22.1.4.1.2 Selection of logical channels

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

[0486] …2> select a destination associated to one of unicast, multicast and broadcast, which has at least one of a MAC CE and a logical channel with the highest priority in the SL action time for SL transmission occasions when SL DRX is applied to the destination and a MAC CE for SL grant associated to the SCI (if any) that satisfies all of the following conditions:

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

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

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

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

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

[0492] …

[0493] 1> Select a logical channel that satisfies all of the following conditions among the logical channels belonging to the selected destination:

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

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

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

[0497] 2>sl-HARQ-FeedbackEnabled is set to a value that satisfies the following conditions:

[0498] 3> If PSFCH is configured for sidelink grant associated with SCI and the UE is capable of PSFCH reception:

[0499] 4> If sl-HARQ-FeedbackEnabled is set to enabled for the highest priority logical channel that meets the above conditions, then sl-HARQ-FeedbackEnabled is set to enabled; or

[0500] 4> If sl-HARQ-FeedbackEnabled is set to disabled for the highest priority logical channel that meets the above conditions, sl-HARQ-FeedbackEnabled is set to disabled.

[0501] 3> Otherwise:

[0502] 4>sl-HARQ-FeedbackEnabled is set to disabled.

[0503] …

[0504] Logical channels shall be prioritized according to the following order (highest priority first):

[0505] - Data from SCCH;

[0506] -Sidelink CSI reporting MAC CE;

[0507] - Sidelink inter-UE coordination request MAC CE and sidelink inter-UE coordination information MAC CE;

[0508] -Sidelink DRX Command MAC CE;

[0509] - Data from any STCH.

[0510] …

[0511] 5.22.1.4.2 Multiplexing of MAC Control Elements and MAC SDUs

[0512] The MAC entity shall multiplex MAC CE and MAC SDU in the MAC PDU according to clauses 5.22.1.4.1 and 6.1.6.

[0513] 5.22.1.5 Scheduling Request

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

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

[0516] Each sidelink logical channel can be mapped to zero or one SR configuration, which is configured by RRC. If the SL-CSI reporting procedure is enabled by RRC, the SL-CSI report is mapped to one SR configuration for all PC5-RRC connections. The SR configuration of the SL-CSI report triggered according to 5.22.1.7 is regarded as the corresponding SR configuration for the triggered SR (clause 5.4.4). The value of the priority of the triggered SR triggered by the SL-CSI report corresponds to the value of the priority of the sidelink CSI report MAC CE. The SR configuration of the SL-CSI report is regarded as the corresponding SR configuration for the triggered SR indicated by the SL-DRX command triggered according to 5.28.3. The value of the priority of the triggered SR triggered by the SL-DRX command indication corresponds to the value of the priority of the sidelink DRX command MAC CE.

[0517] All pending SRs triggered according to the Sidelink BSR procedure (clause 5.22.1.6) before the MAC PDU set shall be cancelled and each corresponding sr-ProhibitTimer shall be stopped when a MAC PDU is transmitted and this PDU contains a SL-BSR MAC CE containing the buffer status up to and including the last event that triggered a Sidelink BSR (see clause 5.22.1.4) before the MAC PDU set.

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

[0519] When the SL grants an adaptive sidelink CSI report MAC CE, when the SL-CSI report has been triggered and not cancelled, or when the triggered SL-CSI report is cancelled due to the delay specified in 5.22.1.7 not being achieved, the pending SRs triggered by the SL-CSI report for the destination will be cancelled and each corresponding sr-ProhibitTimer will be stopped. When the SL grants an adaptive sidelink DRX command MAC CE, when the SL-DRX command indication has been triggered but not cancelled, the pending SRs triggered by the SL-DRX command for the destination will be cancelled and each corresponding sr-ProhibitTimer will be stopped. When the RRC configures sidelink resource allocation mode 2, all pending SRs triggered by sidelink BSR or sidelink CSI report or sidelink DRX command indication will be cancelled.

[0520] 5.22.1.6 Buffer Status Report

[0521] The Sidelink Buffer Status Report (SL-BSR) procedure is used to provide the serving gNB with information about the amount of SL data in the MAC entity.

[0522] RRC configures the following parameters to control SL-BSR:

[0523] -sl-periodicBSR-Timer, configured by periodicBSR-Timer in sl-bsr-Config;

[0524] -sl-retxBSR-Timer, configured by retxBSR-Timer in sl-bsr-Config;

[0525] -sl-logicalChannelSR-DelayTimerApplied;

[0526] -sl-logicalChannelSR-DelayTimer, configured by logicalChannelSR-Delay Timer in sl-bsr-Config;

[0527] -sl-logicalChannelGroup.

[0528] Each logical channel belonging to a destination is assigned to an LCG as specified in TS 38.331 [5]. The maximum number of LCGs is eight.

[0529] The MAC entity determines the amount of SL data available for the logical channel according to the data amount calculation procedure in TS 38.322 [3] and 38.323 [4].

[0530] If any of the following events occurs, the SL-BSR will be triggered:

[0531] 1> If the MAC entity has been configured with sidelink resource allocation mode 1:

[0532] 2> SL data for logical channels belonging to the destination LCG becomes available to the MAC entity; and

[0533] 3> This SL data belongs to a logical channel with a higher priority than any logical channel containing available SL data belonging to any LCG, which belongs to the same destination; or

[0534] 3> None of the logical channels belonging to the LCG contains any available SL data, and the LCGs belong to the same destination.

[0535] In this case, the SL-BSR is hereinafter referred to as 'conventional SL-BSR';

[0536] 2> UL resources are allocated and the number of padding bits remaining after the padding BSR has been triggered is equal to or greater than the size of the SL-BSR MAC CE plus its subheader, in which case the SL-BSR is hereinafter referred to as a 'padding SL-BSR';

[0537] 2>sl-retxBSR-Timer expires and at least one of the logical channels belonging to the LCG contains SL data, in which case the SL-BSR is referred to as 'normal SL-BSR' below;

[0538] 2>sl-periodicBSR-Timer expires. In this case, the SL-BSR is referred to as 'regular SL-BSR' below.

[0539] 1> Otherwise:

[0540] 2> Sidelink resource allocation mode 1 is configured by RRC and SL data can be used for transmission in the RLC entity or PDCP entity, in which case the sidelink BSR is referred to as 'normal SL-BSR' hereinafter.

[0541] For a regular SL-BSR, the MAC entity shall:

[0542] 1> If SL-BSR is triggered for a logical channel configured by RRC with sl-logicalChannelSR-DelayTimerApplied with value true:

[0543] 2>Start or restart sl-logicalChannelSR-DelayTimer.

[0544] 1> Otherwise:

[0545] 2>Stop sl-logicalChannelSR-DelayTimer if it is running.

[0546] For regular and periodic SL-BSR, the MAC entity shall:

[0547] 1> if sl-PrioritizationThres is configured and the value of the highest priority of a logical channel belonging to any LCG and containing SL data for any destination is less than sl-PrioritizationThres; and

[0548] 1> If ul-PrioritizationThres is configured and the value of the highest priority of a logical channel belonging to any LCG and containing UL data is equal to or higher than ul-PrioritizationThres according to clause 5.4.5:

[0549] 2> Prioritize the LCGs of the destination.

[0550] 1> If the Buffer Status Reporting procedure determines that at least one BSR has been triggered and not cancelled according to clause 5.4.5, and according to clause 5.4.3.1.3, the UL grant cannot accommodate a SL-BSR MAC CE plus a sub-header of the SL-BSR, wherein the SL-BSR MAC CE contains the buffer status only for all prioritized LCGs that have data available for transmission, then in the case where the SL-BSR is considered to be non-prioritized:

[0551] 2> Prioritize the SL-BSR used for logical channel prioritization as specified in clause 5.4.3.1;

[0552] 2> Report a truncated SL-BSR containing the buffer status for as many prioritized LCGs as possible that have data available for transmission, taking into account the number of bits in the UL grant.

[0553] 1> Otherwise, if according to clause 5.4.3.1.3, the number of bits in the UL grant is expected to be equal to or greater than the size of the SL-BSR plus the sub-header of the SL-BSR containing the buffer status for all LCGs that have data available for transmission:

[0554] 2> Report the SL-BSR containing the buffer status for all LCGs that have data available for transmission.

[0555] 1> Otherwise:

[0556] 2> Report a truncated SL-BSR containing the buffer status for as many LCGs as possible that have data available for transmission, taking into account the number of bits in the UL grant.

[0557] For filling SL-BSR:

[0558] 1> If the number of padding bits remaining after a Padding BSR has been triggered is equal to or greater than the size of the SL-BSR plus its sub-header, the SL-BSR containing the buffer status for all LCGs that have data available for transmission, then:

[0559] 2> Report the SL-BSR containing the buffer status for all LCGs that have data available for transmission;

[0560] 1> Otherwise:

[0561] 2> Report a truncated SL-BSR containing the buffer status for as many LCGs as possible that have data available for transmission, taking into account the number of bits in the UL grant.

[0562] For a SL-BSR triggered by expiration of the retxBSR-Timer, the MAC entity considers that the logical channel triggering the SL-BSR is the highest priority logical channel having data available for transmission when the SL-BSR is triggered.

[0563] The MAC entity will:

[0564] 1> If the Sidelink Buffer Status Reporter determines that at least one SL-BSR has been triggered and not canceled:

[0565] 2> If, due to logical channel prioritization according to clause 5.4.3.1, UL-SCH resources are available for new transmissions and the UL-SCH resources can accommodate the SL-BSR MAC CE plus its subheader:

[0566] 3> Indicates the multiplexing and combining procedures in clause 5.4.3 to generate SL-BSR MAC CE;

[0567] 3> Start or restart the sl-periodicBSR-Timer, except when all generated SL-BSRs are truncated SL-BSRs;

[0568] 3> Start or restart sl-retxBSR-Timer.

[0569] 2> If the regular SL-BSR has been triggered and the sl-logicalChannelSR-DelayTimer is not running:

[0570] 3> if there are no UL-SCH resources available for new transmission; or

[0571] 3> if due to logical channel prioritization according to clause 5.4.3.1, UL-SCH resources are available for new transmissions and the UL-SCH resources cannot accommodate the SL-BSR MAC CE plus its subheader; or

[0572] 3> If the subcarrier spacing index value set in the sl-allowedSCS-List configured for the logical channel that triggers the SL-BSR does not include a subcarrier spacing index associated with a UL-SCH resource available for new transmission; or

[0573] 3> If the sl-MaxPUSCH-Duration configured for the logical channel that triggered the SL-BSR is less than the PUSCH transmission duration associated with the UL-SCH resources available for new transmissions:

[0574] 4>Trigger scheduling request.

[0575] Even when multiple events have triggered the SL-BSR, the MAC PDU shall contain at most one SL-BSR MAC CE. Regular SL-BSR and periodic SL-BSR shall have priority over padding SL-BSR.

[0576] The MAC entity shall restart the sl-retxBSR-Timer after receiving a SL grant for transmission of new data on any SL-SCH.

[0577] When the SL grant can accommodate all pending data available for transmission, all triggered SL-BSRs may be cancelled. When a MAC PDU is transmitted and this PDU contains a SL-BSR MAC CE, all BSRs triggered before the MAC PDU combination shall be cancelled, wherein the SL-BSR MAC CE contains the buffer status up to (and including) the last event that triggered the SL-BSR before the MAC PDU combination. When RRC configures sidelink resource allocation mode 2, all triggered SL-BSRs shall be cancelled and the sl-retx-BSR-Timer and sl-periodic-BSR-Timer shall be stopped.

[0578] …

[0579] Some or all of the following terms and assumptions may be used in this document. A base station (BS) is a network central unit or network node in New Radio (NR) that is used to control one or more transmission / reception points (TRPs) associated with one or more cells. Communication between the BS and the TRP is via fronthaul. The BS may be referred to as a central unit (CU), an evolved node B (eNB), a next generation node B (gNB), or a NodeB. A TRP is a transmission reception point that provides network coverage and communicates directly with a user equipment (UE). A TRP may be referred to as a distributed unit (DU) or a network node. A cell is a cell consisting of one or more associated TRPs, that is, the coverage of a cell consists of the coverage of all associated TRPs. A cell is controlled by one BS. A cell may be referred to as a TRP Group (TRPG).

[0580] NR Rel-16 is the first version of NR sidelink, and the sidelink transmission between device / UE and device / UE is at a carrier frequency in FR1 (e.g., 450MHz~6000MHz). The NR sidelink in NR Rel-17 targets power saving functions, and there is no motivation to change the Rel-16 carrier frequency in FR1. However, due to use cases such as video sharing and more and more sensing results need to be shared between devices, it may be considered in NR Rel-18 how to improve the throughput of sidelink transmission. Possible techniques can be considered, including carrier aggregation for sidelink transmission, using unlicensed spectrum, using carrier frequencies in FR2 (e.g., 24250MHz~52600MHz). Preferably, in some embodiments, carrier aggregation does not always seem to be available to improve throughput because there may not be multiple carriers to achieve the throughput requirements. Preferably, in some embodiments, for unlicensed spectrum, some delay issues may occur in addition because the unavailability of unlicensed spectrum may be suffered due to Listen-Before-Talk (LBT) results. Preferably, in certain embodiments, for carrier frequencies in FR2, how to manage beams for sidelink transmissions to account for degraded attenuation may require further design.

[0581] In Rel-18, the current goal may be to focus on unicast sidelink transmission. For unicast sidelink transmission between a pair of transmitting (TX) UE and receiving (RX) UE, unicast sidelink transmission may be deployed with beamforming. In the future, multicast sidelink transmission and / or broadcast sidelink transmission may also be deployed with beamforming.

[0582] Figure 7 A problem is illustrated in FIG. 1 , where a TX UE communicates with a RX UE1 using side link (SL) resources scheduled by a network node (e.g., which may be a gNB or a future version network node). Since RX UE1 may have unicast links and / or other broadcast types via other beams, RX UE1 may perform beam scanning for monitoring SL resources via different beams (e.g., corresponding to a monitoring mode of annular beam A and beam B). In this example, the TX UE has established a unicast link with RX UE1 and has a consistent understanding of using beam A. From the perspective of RX UE1, RX UE1 expects to receive the transmission of the TX UE via the monitoring occasion of beam A. When there is a beam change between the TX UE and RX UE1, there may be some issues that need to be addressed because the SL resources used by the TX UE for transmission are based on network node scheduling, for example, in mode 1. Assuming that the SL resources (e.g., associated with SL grants) correspond to t1, t2, t3, once the TX UE and RX UE1 change beams (e.g., in mode 1), the SL resources used by the TX UE for transmission are based on network node scheduling, for example. Figure 7 t1, t2, t3) and SL data of the TX UE in a logical channel with a higher / highest priority, and / or a SL medium access control (MAC) control element (CE) with a higher / highest priority is associated with RX UE1 for SL transmission using the SL resources associated with the SL grant, RX UE1 still uses beam A for monitoring at those timings t1, t2, t3, and the SL resources at those timings are not applicable to this paired link.

[0583] In another example, when there is no beam change between TX UE and RX UE1 (especially between tj and any one of t1 / t2 / t3), the network node may schedule SL resources to TX UE, but TX UE may select a destination associated with a logical channel and / or MAC CE with a higher / highest priority, where those scheduled resources may have a beam mismatch problem for the communication between TX UE and the destination. For example, the network node schedules SL resources for TX UE on beam A, while the communication between TX UE and the destination is via beam B.

[0584] The first UE transmits or reports to the network node association information between a destination and a beam listening mode associated with the destination. Preferably and / or alternatively, the first UE transmits or reports to the network node association information between a destination and a beam for the destination. Preferably, in some embodiments, the association information may include more than one association for more than one destination. Alternatively, the association information includes one or more associations associated with the destination, the one or more associations being that the first UE has sidelink data available on logical channels associated with those destinations. Alternatively, the association information includes one or more associations associated with the destination, the one or more associations being reported by the first UE in a buffer status report (BSR) (for SL). The first UE reports the BSR (for SL) to the network node. For example, when the BSR includes a first destination and a corresponding amount of SL data and a second destination and a corresponding amount of SL data, the association information may provide associations for the first and second destinations (rather than paired destinations of all first UEs, nor destinations of all first UEs with available sidelink data).

[0585] In response to a new destination being added or a new link being established, the association information is transmitted. In response to a destination being removed, the association information is transmitted. In response to a beam listening mode change, the association information is transmitted. In response to the first UE receiving a message from a second UE (e.g., the second UE is a destination of a sidelink communication of the first UE) indicating that the beam listening mode is changed, the association information is transmitted. In response to a beam change for a destination, the association information is transmitted. In response to the first UE receiving a message indicating that a beam for a destination or a second UE is changed, the association information is transmitted. Preferably, in some embodiments, the message is not sidelink control information (SCI) (e.g., not level 1 SCI, nor level 2 SCI). Preferably, in some embodiments, the message is PC5 radio resource control (RRC) signaling or SL MAC CE. In response to the first UE receiving a request from a network node, the association information is transmitted. In response to the first UE changing a currently used / indicated beam(pair) for the second UE, the association information is transmitted. In response to the first UE receiving a message from the second UE indicating a change / update of a currently used / indicated beam(pair), the association information is transmitted. In response to the first UE transmitting a message indicating a change / update of a currently used / indicated beam(pair) to the second UE, the associated information is transmitted.

[0586] When the first UE and / or the second UE does not change the currently used or indicated beam (between the first UE and the second UE), the first UE does not provide the association information. Alternatively, when the first UE and / or the second UE does not change the currently used or indicated beam (between the first UE and the second UE), the first UE may provide the association information based on a timer or periodically. Alternatively, the first UE transmits a BSR including the association information (regardless of whether the currently used / indicated beam changes). In addition and / or alternatively, the first UE may trigger a SL BSR (associated with the second UE), or may trigger an association information report (associated with the second UE) in response to a beam change between the first UE and the second UE. The SL BSR triggered by the beam change may contain fields or information different from the SL BSR triggered in response to the expiration of a timer or the arrival of data. The SL BSR reported / triggered / generated due to a beam change may be referred to as a beam change SL BSR. Alternatively, the SL BSR triggered in response to a beam change with a destination change may be referred to as a conventional SL-BSR. Additionally and / or alternatively, the SL-BSR triggered by a beam change with a destination may indicate the destination and / or one or more destinations associated with the beam change since the latest SL BSR has been transmitted.

[0587] The first UE transmits or reports information associated with one or more opportunities at which the first UE determines to perform sidelink transmission to the network node. The information will assist the network node in scheduling SL resources in the aligned / expected opportunities for the first UE to perform sidelink transmission to the destination with a beam having the highest / highest priority logical channel and / or SLMAC CE. The information may be part of the BSR, and / or the BSR may include information associated with one or more opportunities. When the BSR includes an amount of data associated with more than one destination, the first UE reports corresponding information for each destination associated with the amount of data in the BSR, or the first UE reports information associated with one destination, the logical channel with available sidelink data of which has a higher / highest priority. The information is different from the BSR. The BSR here corresponds to a sidelink BSR to be reported to the network node. Information may be transmitted via a scheduling request (SR). Information is transmitted earlier than the opportunity for transmitting the BSR. Information associated with one or more opportunities will be indicated by periodicity and / or offset. Information is relayed to the network node via the first UE based on the exchanged information between the first UE and the second UE. One or more opportunities refer to the time when the UE transmits information, or to the system frame number 0, or to the direct frame number 0, or to the time slot 0 of the sidelink resource pool, or to a configured or indicated opportunity. One or more opportunities are associated with a destination among multiple destinations with available sidelink data. Based on multiple destinations with available sidelink data, the first UE reports to the network node a BSR including the amount of sidelink data associated with a subset or all of the multiple destinations. The multiple destinations include the second UE and / or the second UE as the destination UE. The destination corresponds to the highest / higher priority of the logical channel with available sidelink data among the multiple destinations. One or more opportunities may correspond to a transmission time interval (TTI) associated with the second UE performing reception via at least one currently used / indicated beam or beam pair (for example, the second UE is a paired UE that communicates with the first UE using a paired beam pair). The first UE determines one or more opportunities based on the exchange information from the second UE. The exchange information indicates the TTI or one or more opportunities for the second UE to receive / listen to the sidelink using the currently used / indicated beam. In one example, the exchange information may indicate a periodicity and / or offset in a logical time slot or a physical time slot for indicating a beam listening / receiving mode associated with the second UE. Based on the exchange information, the first UE determines which TTIs to use for transmission to the second UE when sidelink data is available for a logical channel associated with the second UE. The first UE reports information associated with one or more opportunities to the network node regardless of whether there is a currently used / indicated beam or a beam pair change / update (between links).On the other hand, when the currently used / indicated beam and / or beam pair (between the first UE and the second UE) does not change or update, the first UE does not perform sidelink transmission with the destination set to the second UE on the TTI, except for the TTI in which the second UE performs sidelink reception based on the currently used / indicated beam pair. After the first UE transmits the BSR and / or information associated with one or more opportunities, the first UE receives a SL grant from the network node. The SL grant indicates up to a certain number of SL resources (which are in different TTIs, for example. Figure 7t1, t2, t3 in ). The first UE selects a destination based on a logical channel prioritization (LCP) procedure. The LCP procedure may consider whether the first UE uses / utilizes paired beams for monitoring / reception for at least one of the number of SL resources of the destination that have logical channels with available sidelink data (or at least one TTI corresponding to the number of SL resources). Alternatively, the LCP procedure does not consider whether the first UE uses / utilizes paired beams for monitoring / reception for at least one of the number of SL resources of the destination that have logical channels with available sidelink data (or at least one TTI corresponding to the number of SL resources). The LCP procedure includes the first UE determining that a destination (for which the destination is the first UE) has a logical channel with available sidelink data (regardless of whether the destination uses / utilizes paired beams for the first UE at a TTI corresponding to the number of SL resources). More specifically, the TTIs corresponding to the number of SL resources are denoted as t1, t2, t3. The first UE determines the destination based on the LCP procedure. Alternatively, the first UE determines the destination based on whether the destination uses / utilizes the paired beam for the first UE to monitor / receive at the earliest TTI corresponding to the number of SL resources (e.g., whether the destination is ready for monitoring / receiving or uses / utilizes the paired beam (associated with the first UE) to monitor / receive at least at the earliest TTI, such as t1). When one destination does not use / utilize the paired beam (associated with the first UE) to monitor / receive at TTI t1, the first UE does not select the one destination as the destination (when performing sidelink transmission according to SL grant). When another destination uses / utilizes the paired beam (associated with the first UE) to monitor / receive at TTI t1, the first UE may select the other destination as the destination (once the other destination is associated with a logical channel with available sidelink data, the logical channel is associated with the highest / higher priority among the logical channels with available sidelink data). In another example, the first UE may determine a destination for the first UE to monitor / receive at least one TTI using / utilizing the paired beam. In this example, when the second destination listens / receives for the first UE using paired beams on at least TTI t2, t3, the first UE may determine the destination based on the second destination. Preferably, in some embodiments, one UE corresponds to one destination. Preferably, in some embodiments, one destination corresponds to an L1 or L2 destination ID. Preferably, in some embodiments, the L1 destination ID is part of the L2 destination ID.

[0588] Preferably, in some embodiments, the first UE changes / updates the beam pair currently used / indicated (for the second UE). Preferably, in some embodiments, the applied change / update time corresponds to a specific opportunity. Preferably, in some embodiments, the specific opportunity may be a first time slot or symbol, which is at least a duration later than receiving or transmitting a signal indicating a paired beam change. Preferably, in some embodiments, the signal may be transmitted via the first UE or received by the first UE (from the second UE). Preferably, in some embodiments, the signal may correspond to an SL BFR response (transmitted by the first UE or received by the first UE). Preferably, in some embodiments, before the specific opportunity, the first UE determines the beam pair currently used / indicated for the second UE based on the original beam pair, or determines that the beam pair currently used / indicated is the original beam pair. Preferably, in some embodiments, after the specific opportunity, the first UE determines the beam pair currently used / indicated for the second UE based on the signal (indicating a paired beam change), or determines that the beam pair currently used / indicated is an updated / changed beam pair. Preferably, in some embodiments, the signal may be an SCI and / or a MAC CE. Preferably, in some embodiments, a signal associated with a pair of first UE and second UE includes a bit field indicating beam-related information between the first UE and the second UE. More specifically, the beam-related information may correspond to which TX beam is the currently used / indicated beam. For example, a signal transmitted via the second UE indicates the TX beam used by the second UE. When in the future / later opportunity, the second UE transmits a second signal indicating another used TX beam (which is different from the currently used / indicated TX beam) or a beam change / update, the first UE will determine that the beam pair of the link between the first UE and the second UE changes. Preferably, in some embodiments, the signal may be transmitted in a TTI without scheduling a physical sidelink shared channel (PSSCH) or requiring scheduling of the PSSCH. For the same TTI, the signal and the scheduled PSSCH are associated with the same beam pair. For a PSSCH scheduled in another TTI later than a specific opportunity (and a PSSCH transmitted in another TTI via the first UE), the first UE transmits the PSSCH via the currently used / indicated TX beam (based on the signal). Preferably, in some embodiments, a specific opportunity is associated with a signal. Preferably, in some embodiments, the specific timing is an applied timing based on the signal. Preferably, in some embodiments, the first UE and the second UE have the same understanding of the specific timing. Preferably, in some embodiments, based on the signal (and also after the specific timing), the second UE (or UE performing sidelink reception) expects to receive a SL transmission from the first UE in the TTI via the (new) used / indicated beam monitoring / reception. Preferably, in some embodiments, in response to the signal, the second UE transmits its beam monitoring mode associated with the (new) beam pair to the first UE according to the signal.Preferably, in some embodiments, in response to the signal, the second UE transmits its beam listening mode associated with the (new) beam pair to the network node according to the signal, or exchanges the beam listening mode with the network node. Alternatively, before the first UE or the second UE transmits the signal, the first UE or the second UE receives one or more beam reports from its paired UE. Preferably, in some embodiments, the beam report includes one or more beam information, such as beam identification (ID), reference signal (RS) ID, quality. Preferably, in some embodiments, based on the beam report, the first UE or the second UE determines whether to transmit a signal to indicate a beam change for this link. Preferably, in some embodiments, when the UE receives the signal, the UE may transmit a rejection to the paired UE to not apply the newly indicated beam pair. Preferably, in some embodiments, the UE may transmit the recommended beam pair to the paired UE.

[0589] Preferably, in some embodiments, the SL grant does not include information associated with which transmit beam of the first UE to use. Preferably, in some embodiments, instead, the first UE determines which TX beam to use based on the paired beam associated with the destination of the sidelink transmission on the TTI according to the SL grant. For example, in Figure 8 In the figure, considering the SL grant indicating TTI n+9 for the TX UE, the TX UE determines that the destination UE is RX UE1, and the TX UE determines the TX beam used for side link transmission or which TX beam corresponds to the RX beam of RX UE1 (e.g., beam B) based on the currently used / indicated beam (pair) for beam Y (TX UE side).

[0590] Preferably, in certain embodiments, the first UE may perform sidelink transmission on the TTI according to the SL grant based on the TX beam as a result of the LCP procedure of the first UE. Preferably, in certain embodiments, in other words, the SL grant does not provide or restrict the use of SL resources on the TTI via a specific TX beam. Preferably, in certain embodiments, alternatively, the SL grant will occupy or indicate that the SL resources on the TTI will be transmitted via a beam regardless of the LCP result of the first UE. Preferably, in certain embodiments, the SL grant does not restrict the LCP procedure of the first UE. In addition and / or alternatively, the first UE may select a destination in the SL active time (e.g., listening to the SCI) of the SL transmission occasion of the SL grant, and listen to the Tx beam of the first UE or listen to the beam associated with the Tx beam.

[0591] Preferably, in some embodiments, SL resources on TTIs granted according to one SL are used to transmit the same TB or MAC PDU. Preferably, in some embodiments, the later TTI is a retransmission of one TB. Preferably, in some embodiments, the earliest TTI is a new transmission of one TB.

[0592] Preferably, in some embodiments, the first UE and / or the second UE performs sidelink communication based on its receive beam in a carrier associated with a higher frequency application sidelink (e.g., SL FR2) performing (partial) sensing. Preferably, in some embodiments, the exchanged information is related to the TTI of the receiving UE performing the RX beam based on the (partial) sensing.

[0593] When the first UE determines that the destination has a higher / highest priority for sidelink transmission according to the SL grant, and the destination uses / utilizes another beam different from the paired beam for the first UE for monitoring / reception on each of the following

[0594] SL resources on all TTIs granted by the SL, or

[0595] According to the SL resources on the earliest TTI of the SL grant (considering that the SL grant is for a new transmission, or there is no another earlier SL grant with the same hybrid automatic repeat request (HARQ) process and unswitched new data indicator (NDI),

[0596] The first UE then transmits a report to the network node indicating information associated with a preferred SL beam or preferred timing for SL grant or HARQ process.

[0597] Preferably, in certain embodiments, the report is transmitted to the network node simultaneously with the HARQ information for SL grant. Alternatively, the report may be transmitted to the network node at a different timing than the HARQ information for SL grant. In one example, the first UE may transmit an SR for requesting uplink (UL) resources for transmitting a report indicating information associated with a preferred SL beam or preferred timing for SL grant or HARQ process or for retransmission or for a destination.

[0598] The first UE transmits a physical uplink control channel (PUCCH) including a HARQ codebook associated with a SL grant, wherein the PUCCH includes a report indicating information associated with a preferred SL beam or preferred timing for SL grant or HARQ process or for retransmission or for a destination. In addition and / or alternatively, the PUCCH may be associated with a PUCCH resource. The PUCCH resource may be (implicitly) associated with a SL beam and / or preferred timing for retransmission of a destination. For example, the time and / or frequency range of the PUCCH resource may be mapped to / associated with a SL beam and / or preferred timing for retransmission of an associated destination (e.g., via configuration). The UE may select a PUCCH resource to transmit the PUCCH based on the preferred SL beam or preferred timing.

[0599] based on the determined / selected destination not listening / receiving SL resources at all TTIs according to the SL grant, and / or the determined / selected destination not listening / receiving SL resources at the earliest TTI according to the SL grant,

[0600] The first UE triggers transmission of a report to the network node, and / or

[0601] The first UE sets or determines a NACK in a HARQ codebook including HARQ information associated with one or more SL transmissions including the SL transmission according to the SL grant.

[0602] For sidelink resource allocation model-1, when the first UE determines a destination with beam pairing problem using SL resources on all TTIs or earliest TTI according to SL grant, the first UE shall report the suggested TTI to the network node.

[0603] The first UE reports to the network node a TTI for future SL grant scheduling retransmissions. The suggested TTI corresponds to the determined / selected destination for performing sidelink reception / listening via the paired RX beam.

[0604] The second issue is how to handle the situation when the TX UE is in SL beam failure associated with one RX UE (e.g., one destination) to avoid selecting one RX UE as the destination for sidelink transmission on SL resources scheduled by one or more gNBs, but the TX UE has an unresolved SL beam failure with one RX UE.

[0605] A TX UE (e.g., a first UE) has one or more logical channels with available sidelink data associated with one or more destinations. The first UE may have beam issues with one or more links (associated with a subset of the one or more destinations). When the first UE reports a BSR to a network node, the first UE does not include the amount of data associated with the destinations having the beam issues. Before / before a specific opportunity for applying a new beam pair for a link (between the first UE and the destinations having the beam issues), the first UE reports the BSR to the network node without including the amount of data associated with the destinations.

[0606] Alternatively, the first UE reports a specific code point (associated with the destination) of the amount of data in the BSR to the network node.Preferably, in certain embodiments, the specific code point (associated with the destination) of the amount of data indicates that the first UE has a beam problem associated with the destination.

[0607] Alternatively, the first UE reports a BSR including a beam listening mode or a recommended TTI associated with each destination. In this case, the first UE reports a specific beam listening mode or the first UE does not provide a recommended TTI associated with a destination with a beam problem. The specific beam listening mode may explicitly or implicitly indicate a beam problem with an associated destination.

[0608] Alternatively, the first UE reports a BSR including beam related information or beam failure related information associated with each destination. In this case, the first UE reports a BSR indicating whether a destination has a beam problem and which destinations have a beam problem.

[0609] When the network node receives the BSR from the first UE, the network node may know which destination(s) have beam issues. The network may not schedule SL resources for destinations with beam issues, even if a logical channel with available data associated with the destination has a higher priority.

[0610] Preferably, in some embodiments, a beam problem is determined when the first UE determines that a link may have reduced quality via a currently used / indicated beam pair. Preferably, in some embodiments, the determination of reduced quality may correspond to the number of times the quality of the link is less than a threshold. Preferably, in some embodiments, the beam problem may correspond to the first UE encountering a beam failure. Preferably, in some embodiments, the beam problem may correspond to the first UE triggering a beam change for a destination. Preferably, in some embodiments, the beam problem may correspond to the first UE receiving a signal indicating a beam change (and before a specific timing for applying the newly indicated beam pair). Preferably, in some embodiments, the first UE reports a BSR of a destination with a beam problem before the beam problem is resolved in a different manner than the first UE reports a BSR of the destination with a beam problem after the beam problem is resolved. Preferably, in some embodiments, the first UE reports a BSR of a destination with a beam problem in a different manner (e.g., before the beam problem is resolved) than the first UE reports a BSR of a destination without a beam problem (e.g., after the beam problem is resolved or no beam problem continues to exist).

[0611] The TX UE (e.g., the first UE) receives a SL grant or has a selected grant or a SL configured grant. One or more side link resources are indicated by the SL grant or the selected grant or the SL configured grant. When the first UE performs an LCP procedure (for selecting a destination), the first UE selects / determines a destination based on a link between the first UE and a destination that does not face a beam problem. When the first UE performs an LCP procedure (for selecting a destination), the first UE (should) select / determine a destination that does not have a beam problem (between the first UE and the destination). Preferably, in certain embodiments, the first UE excludes one or more destinations, wherein the link between each of the one or more destinations and the first UE faces a beam problem. When the first UE receives a signal indicating a beam change from a second UE or transmits a signal to a second UE, the determined / selected destination does not correspond to the second UE. The first UE excludes the second UE as the determined / selected destination. For a TTI within a time interval having a beam problem associated with the second UE, the first UE excludes the second UE as the determined / determined destination in the TTI. The time interval is from when the first UE receives or transmits a signal indicating a beam change to the specific time when the first UE applies a new beam. Simply put, when the first UE has an unresolved beam problem with the second UE, the LCP procedure does not consider the second UE. Preferably, in some embodiments, the first UE will determine or consider that the second UE is not available for sidelink reception via the old used / indicated beam pair. Preferably, in some embodiments, the first UE will check whether the destination having a logical channel with available sidelink data is in a beam problem. Preferably, in some embodiments, when the destination is in a beam problem associated with the first UE, the first UE determines that there is no available sidelink data associated with the destination. Preferably, in some embodiments, when the destination is in a beam problem associated with the first UE, the first UE determines that the priority of the logical channel associated with the destination is the lowest priority.

[0612] Preferably and / or alternatively, when the first UE receives a signal from a second UE / destination or transmits a signal indicating a beam change to the second UE / destination, the first UE may apply the new beam at a specific timing and / or after a time interval of receiving or transmitting a signal indicating a beam change from the first UE. When the first UE selects a second UE / destination in the LCP procedure, the first UE may select a sidelink resource for sidelink transmission to the second UE / destination at a specific timing or after a time interval. Preferably, in some embodiments, the first UE may select a sidelink resource by excluding candidate resources before a specific timing or within a time interval. Preferably, in some embodiments, in order to select a sidelink resource for sidelink transmission to the second UE / destination, a resource selection window may be restricted at the beginning or after a specific timing or after a time interval.

[0613] Preferably and / or alternatively, when the first UE detects a beam failure for the second UE / destination, the first UE (should) exclude the second UE / destination from selection in the LCP procedure. Preferably and / or alternatively, when the first UE performs the LCP procedure (for selecting a destination), the first UE (should) select / determine a destination that does not have a beam failure issue (between the first UE and the destination).

[0614] The TX UE (e.g., the first UE) discards the entire SL grant (or the entire SL configured grant or when the grant is selected) or discards each SL transmission associated with the SL grant (or the SL configured grant or the selected grant). Preferably, in some embodiments, the SL grant indicates the SL resources in TTI a, b, c. When the first UE determines or selects a destination (which is associated with the highest priority of the logical channel with available sidelink data), where the destination does not monitor / receive TTI a, b and / or c via the paired beam associated with the first UE, the first UE discards the entire SL grant or discards the sidelink transmission associated with the sidelink resources in any of TTIs a, b and c where the destination does not monitor / receive via the paired beam associated with the first UE. For TTI a, b or c where the destination monitors / receives via the paired beam associated with the first UE, the first UE transmits to the destination via the paired beam on the corresponding TTI. The discard mechanism may further consider whether the destination monitors at least the earliest TTI among TTIs, a, b, c. Based on the earliest TTI being monitored / received by the destination via the paired beam, the first UE may transmit via the paired link at TTIs, a, b and c (considering that the SCI in TTI a may indicate the destination to change the listening beam for the later (indicated) TTI). Based on the earlier TTI (e.g., TTI a or TTI b) being monitored / received by the destination via the paired beam, the first UE may transmit via the paired link at the later (indicated) TTI. Preferably, in certain embodiments, when the determined / selected destination is not monitoring / receiving at the earlier TTI, the first UE discards the entire SL grant. Alternatively and / or preferably in certain embodiments, when the determined / selected destination has an unresolved beam problem associated with the first UE (or the first UE determines that there is an unresolved beam problem associated with the determined / selected destination), the first UE discards the entire SL grant. Preferably, in certain embodiments, when the determined / selected destination has an unresolved beam problem associated with the first UE (or the first UE determines that there is an unresolved beam problem associated with the determined / selected destination), the first UE discards the sidelink transmission or sidelink resources in the TTI before the beam problem is resolved. In one example, when TTI c is after the timing of beam problem resolution, the first UE performs sidelink transmission to the determined / selected destination on resources on TTI c. In another example, when TTI a, TTI b are before the timing of beam problem resolution, the first UE discards the sidelink transmission or discards the sidelink resources on TTI a and TTI b.In one example, when the first UE receives a SL grant indicating a side link resource at TTI a, b, c, wherein the determined destination does not monitor any of TTI a, b, c via paired beams, the first UE switches to using a special pool to transmit updated information of the monitoring beams of TTI b, TTI c. Preferably, in some embodiments, the first UE transmits via using a special pool based on whether there is at least a physical side link feedback channel (PSFCH) occasion before TTI c, so that the first UE can receive a HARQ from the destination, wherein the HARQ indicates a confirmation of changing the monitoring beams of TTI b and / or TTI c.

[0615] The third question is whether the mode-2 reservation or mode-1 periodic resources associated with the SL configured grant are valid when the paired beam changes. According to the NR side link, periodic reservation for multiple MAC packet data units (PDUs) / transport blocks (TBs) is applied to adapt to or serve periodic characteristics. The SCI includes a reservation period field to indicate future reservations. The SCI schedules unicast side link transmissions to a second UE or a paired receiving UE. Preferably, in some embodiments, future reservations correspond to occasions for the same or different MAC PDU / TB transmissions (depending on whether the SL counter decreases). The time of the future reservation is based on the timing of the SCI, and the frequency resources of the future reservations are based on the same frequency resources as the frequency resources scheduled by the SCI (e.g., for the PSSCH scheduled by the SCI in the current time slot for the SCI / PSSCH and for the same subchannel for future reservations). In SL FR2, the SCI can be transmitted and / or received via a beam pair (e.g., a paired transmitting UE uses a first TX beam and a paired receiving UE uses a first RX beam). From the perspective of the receiving UE, if the SCI is received via the first RX beam with a future reservation (for example, the future reserved occasion is reserved by the paired transmitting UE that transmits the SCI), the receiving UE considers or determines that the future reservation is associated with the first RX beam. However, when the beam pair of the link changes or is updated, it is possible to use the first RX beam on the future reserved occasion for reception. In addition, whether the paired transmitting UE transmits on the occasion via the first TX beam and the manner, and whether the paired receiving UE considers the reservation condition on the occasion and the manner may require further design and research. Preferably, in some embodiments, different treatments may be designed for different side link resource allocation modes. Preferably, in some embodiments, different treatments may be designed for different periodicities. In one example, for the case where the periodicity of the reservation period is greater than a threshold, it is determined that the reserved resources are associated with the TX beam used in the TTI in which the transmitting UE transmits the SCI indicating the reservation. When the periodicity of the reservation period is less than a threshold, the reserved resources may be changed to a new TX beam (different from the resources used to transmit the SCI indicating the reservation). Alternatively, for a case where the periodicity of the reservation period is greater than a threshold, the reserved resources may be changed to a new TX beam (different from the resources used to transmit the SCI indicating reservation). When the periodicity of the reservation period is less than the threshold, it is determined that the reserved resources are associated with the TX beam used in the TTI in which the transmitting UE transmits the SCI indicating reservation. The TX UE may determine whether to change the TX beam for the reserved resources based on the periodicity of the reservation period and / or the sidelink resource allocation pattern.

[0616] The first UE transmits the SCI to the second UE via the first TX beam in the first TTI. The second UE receives the SCI in the first TTI via the first RX beam. The SCI indicates the reserved resources in the second TTI based on the Time Resource Indication Value (TRIV) field. The SCI indicates the second reserved resources in the third TTI based on the Reservation Period field. Preferably, in some embodiments, the second TTI is later than a specific opportunity. Preferably, in some embodiments, the third TTI is later than a specific opportunity. Preferably, in some embodiments, the first TTI is earlier than a specific opportunity. Preferably, in some embodiments, the specific opportunity corresponds to a new / updated beam applicable opportunity. Preferably, in some embodiments, the currently used / indicated beam for the link between the first UE and the second UE is changed or updated from the first TX beam (of the first UE) to the second TX beam, and is changed or updated from the first RX beam (of the second UE) to the second RX beam.

[0617] When there is a currently used / indicated beam change / update between the links of the first UE and the second UE (and after a specific timing):

[0618] The first UE discards, clears or releases the reserved resources on the second / third TTI, and / or

[0619] The first UE does not transmit on the reserved resources on the second / third TTI, and / or

[0620] The first UE performs sidelink transmission on the reserved resources on the second / third TTI via the previously used / indicated beam, and / or

[0621] The first UE performs sidelink transmission on the reserved resources on the second / third TTI via the updated used / indicated beam, and / or

[0622] The first UE triggers resource reselection for reserved resources on the second / third TTI, and / or

[0623] The first UE requests the second UE to transmit inter-UE coordination information regarding preferred resources or preferred TTIs associated with one or more RX beams (of the second UE).

[0624] When there is a currently used / indicated beam change / update between the links of the first UE and the second UE (and after a specific timing):

[0625] The second UE monitors / listens to the reserved resources on the second / third TTI via the newly used / indicated RX beam (e.g., the second RX beam), and / or

[0626] The second UE monitors / receives the reserved resources on the second / third TTI via the previously used / indicated RX beam (eg, the first RX beam).

[0627] Based on the sidelink transmission on the reserved resources in the TTI being associated with a new transmission or a retransmission (or based on reservation by a TRIV field or a reservation period field), the first UE determines which TX beam to use for transmission on the reserved resources on the second / third TTI. In one instance, when the reserved resources on the second TTI are associated with a retransmission (e.g., associated with the second UE using a new beam pair), the first UE discards or clears the reserved resources on the second TTI. In one instance, when the reserved resources on the third TTI are associated with a new transmission, the first UE uses the first TX beam to perform a sidelink transmission on the reserved resources on the third TTI and / or determines / selects a destination, which is monitored via a paired beam on the third TTI. Preferably, in certain embodiments, the first UE has the flexibility to determine / select a destination based on monitoring / receiving at the destination on the third TTI using / via a third RX beam, which is associated with the first TX beam of the link between the destination and the first UE.

[0628] Alternatively and / or preferably, based on the first UE being in sidelink resource allocation mode-1 or mode-2, or based on the first UE using sidelink resources selected by itself or scheduled / configured by the network node, the first UE determines which TX beam to use to transmit on the reserved resources on the second / third TTI. For sidelink resource allocation mode-1, the first UE may transmit on the reserved resources via the updated / changed beam (e.g., the second TX beam). For sidelink resource allocation mode-2, the first UE performs sidelink transmission on the reserved resources via the previously used / indicated beam (e.g., the first TX beam). For sidelink resource allocation mode-1, the first UE may perform sidelink transmission on the reserved resources on the second / third TTI using the currently used / indicated beam. For sidelink resource allocation mode-2, since the selected grant or sidelink resource is determined based on the sensing result associated with the first TX beam (when the first UE uses the first TX beam to determine the sensing result for determining the sidelink resource in the first TTI, the second TTI and / or the third TTI), changing / updating to transmit on the reserved resources using the second TX beam may cause interference to other UEs. Therefore, for sidelink resource allocation mode-2, it is preferred to transmit on the reserved resources on the second / third TTI using the old beam (e.g., the first TX beam).

[0629] Preferably, in some embodiments, in response to the beam change between links, the first UE triggers resource reselection of one or more reserved resources in the TTI based on the newly indicated beam. Preferably, in some embodiments, once the first UE can change the destination from the second UE to a third UE with a beam pair using the previously used / indicated beam (e.g., which is used for a new transmission rather than a retransmission), the UE does not perform resource reselection.

[0630] Preferably, in some embodiments, an enhanced LCP method is that when the transmitter UE selects or determines the destination for at least one TTI associated with a TX beam, the transmitter UE preferentially selects the destination of at least the TTI monitored using the RX beam, and the RX beam corresponds to a TX beam. Preferably, in some embodiments, this method is used at least when the transmitter UE has at least determined that the TTI is associated with a TX beam. In other words, the transmitter UE does not change the beam used for transmission in a TTI. Alternatively, when the transmitter UE does not reserve for future TTIs, the transmitter UE selects the destination based on at least the destination with available side link data, and the available side link data has the highest priority of the logical channel among all logical channels containing available side link data associated with different destinations. Preferably, in some embodiments, the transmitter UE uses the currently used / indicated beam to perform the sensing and resource selection procedure. Preferably, in some embodiments, the transmitter UE determines the side link resource set in the TTI set as the selected side link grant. Preferably, in some embodiments, the transmitter UE determines the TTI set based on one or more candidate resources in multiple TTIs. Preferably, in some embodiments, the plurality of TTIs are within the selection window. Preferably, in some embodiments, the plurality of TTIs are associated with sensing results associated with (partial) sensing by the transmitter UE using a currently used / indicated beam (associated with a destination). Preferably, in some embodiments, the set of TTIs is determined to be a TTI when the selected destination performs listening / reception via a paired beam associated with the transmitter UE.

[0631] Preferably, in some embodiments, based on a sensing and resource selection procedure associated with one beam of the first UE (e.g., a first TX beam also used for sensing and resource selection), the first UE determines that one or more resources are associated with a beam. Preferably, in some embodiments, based on the sensing results associated with one beam, reserved resources in one or more TTIs are associated with one beam. Preferably, in some embodiments, the first UE may change the destination using a paired beam monitored in one or more TTIs associated with one beam. Preferably, in some embodiments, once the first UE receives inter-UE coordination (IUC) indicating information related to the reserved TTI, the first UE changes the transmit beam used for the already reserved TTI. For example, in Figure 8 In the embodiment of the present invention, based on the sensing result associated with beam X, the TX UE (e.g., the first UE) may transmit the SCI in TTI n using beam X, and the TX UE will select RX UE1 (e.g., the second UE) as the destination. The SCI may reserve the side link resources in TTI n+8. When the first UE reserves the side link resources in TTI n+8 using the sensing result associated with beam X, the first UE is limited to using beam X to perform the side link transmission in TTI n+8. Unless the first UE has the sensing result or receives an IUC indicating the sensing result associated with TTI n+8 from another / other UE, the first UE cannot change the transmission beam used for the reserved side link resources in TTI n+8. When the beam pair used for the link between the first UE and the second UE changes from (X, A) to (Y, B), the first UE cannot change the transmission beam used for the reserved side link resources in TTI n+8. In one example, the first UE selects a destination for sidelink transmission on reserved resources in TTI n+8 based on which destination monitors TTI n+8 using an RX beam paired with the first UE's transmit beam X. In this example, the first UE will select RX UE2 based on RX UE2 monitoring TTI n+8 based on a paired beam (e.g., beam C) (since the beam pair between the first UE and RX UE2 corresponds to beam X and beam C).

[0632] Preferably, in certain embodiments, based on one SL configured grant (CG) configuration (with or without downlink control information (DCI) activation), the first UE determines which destination the reserved resources in the second / third TTI are associated with and / or which TX beam to use based on the beam pair associated with the destination (with the highest priority). Alternatively, the SL CG configuration is associated with one TX beam of the first UE. When the reserved resources based on the SL CG configuration are associated with one TX beam, the first UE uses the RX beam paired with one TX beam of the first UE to determine or select the destination based on at least the destination listening / receiving on the TTI associated with the SL CG configuration. In other words, the destination is a candidate destination selected based on the destination listening / receiving TTI via the RX beam paired with one TX beam.

[0633] Preferably, in some embodiments, based on the exchange information regarding which TTI, the receiving UE performs monitoring / reception via the beam pair associated with the transmitter UE. Preferably, in some embodiments, the transmitter UE determines the TTI set based on the exchange information. For example, when the destination associated with the highest priority of the logical channel with available sidelink data corresponds to the second UE, the first UE determines the TTI set based on the exchange information from the second UE. Preferably, in some embodiments, based on the TTIs that the second UE monitors / receives via the beam associated with the first UE, the first UE determines the TTI set. Preferably, in some embodiments, for sidelink transmission / reception associated with the second UE, the first UE does not include / utilize sidelink resources in TTIs that the second UE does not perform monitoring via paired beams. Preferably, in some embodiments, for sidelink transmission / reception associated with the second UE, the first UE excludes sidelink resources in TTIs that the second UE does not perform monitoring via paired beams.

[0634] Preferably, in some embodiments, the reserved resources in the second TTI correspond to the SL CG configuration (which may be type-1 or type-2).

[0635] Preferably, in some embodiments, the reserved resources in the third TTI correspond to the SL CG configuration (which may be type-1 or type-2).

[0636] Preferably, in some embodiments, the reserved resources in the second TTI correspond to the periodic reserved resources in the sidelink resource allocation mode-2.

[0637] Preferably, in some embodiments, the reserved resources in the third TTI correspond to the periodic reserved resources in the sidelink resource allocation mode-2.

[0638] Preferably, in some embodiments, considering that a pair of UEs includes a first UE and a second UE, the beam pair change may be a TX beam change and / or a RX beam change.

[0639] The first UE performs sidelink transmission with the second UE. The first UE performs sidelink transmission with the third UE. Preferably, in some embodiments, the first UE has a unicast sidelink link with the second UE, and has a second unicast sidelink link with the third UE. Preferably, in some embodiments, the first UE has an initial beam pair with the second UE. Preferably, in some embodiments, the first UE has an initial beam pair with the third UE. Preferably, in some embodiments, the first UE performs sidelink transmission with the second UE via the first beam. Preferably, in some embodiments, the first UE and the second UE exchange listening occasions associated with the initial beam pair. For example, when the initial beam pair between the first UE and the second UE is beam X of beam "X, Y, Z, W" from the first UE and beam A of beam "A, B, C, D" from the second UE, the first UE provides at least information associated with beam X. Preferably, in some embodiments, information associated with one beam may be a listening occasion associated with one beam. Preferably, in some embodiments, the information may be in the form of a whitelist that the first UE determines to receive or listen to based on a beam (e.g., beam X). Preferably, in some embodiments, when the first UE uses beam X to perform sidelink transmission may depend on the associated available data of one or more paired beams associated with beam X and logical channels associated with one or more destinations. For example, in Figure 8In the embodiment, the TX UE performs sidelink transmission with RX UE1 and preferably with RX UE2 and preferably with RX UE3. The TX UE has beam X and beam Y (for sidelink transmission). RX UE1 has beam A and beam B (for sidelink reception). RX UE2 has beam C and beam D (for sidelink reception). RX UE3 has beam E and beam F (for sidelink reception). It is assumed that the beam pair between the TX UE and RX UE1 is (X, A), and preferably the beam pair between the TX UE and RX UE2 is (X, C), and preferably the beam pair between the TX UE and RX UE3 is (Y, F). There may be information between each pair. Based on the exchanged information, the TX UE may determine that the RX UE1 will use or utilize or determine the listening occasions for monitoring / receiving (and preferably and / or additionally monitoring occasions RX UE2). Preferably, in some embodiments, the information may notify more than one listening occasion (used by the RX UE) of a beam other than a paired beam. In this example, the TX UE determines each opportunity or time occasion (e.g., TTI n, n+1, n+2, n+3, n+4...n+9) at which each paired RX UE determines to perform side link reception / listening. Preferably, in some embodiments, before the beam change opportunity tc (for a pair of TX UE and RX UE1), the TX UE determines that RX UE1 will listen to TTI n, n+2 via the use of a paired beam (e.g., beam A). The TX UE determines that RX UE1 will listen to TTI n, n+2 via the use of a paired beam (e.g., beam A). Based on the exchanged information and destination associated with the highest logical channel with data available for transmission or MAC CE, the TX UE may determine which beam to use for side link transmission for a given TTI. In this example, based on the exchanged information, time slot n corresponds to beam X and beam Y of the TX UE. When SL data and / or MAC CE are to be transmitted to three UEs, the determination of using beam X or beam Y is based on the highest priority logical channel associated with the SL data and / or MAC CE. In another example, when both TX UE and RX UE1 determine to use beam Y and beam B after timing tc, RX UE1 provides another exchange information related to beam B to TX UE. Preferably, in some embodiments, TX UE provides another change information related to beam Y to RX UE1. Preferably, in some embodiments, the information related to its beam listening occasion can be a semi-static mode. Preferably, in some embodiments, unless one UE changes or updates its beam listening mode, the UE will not provide the updated / changed information to the paired UE. Preferably, in some embodiments, the reservation of SCI (e.g., through the time domain assignment field, TRIV or through the reservation period field) can be used as a dynamic indication.Preferably, in some embodiments, based on such indication, the RX UE will update the listening beam based on the currently used / indicated beam pair between the TX UE and the RX UE. Preferably, in some embodiments, regardless of / regardless of the (semi-static) beam listening mode of the RX UE, the RX UE may not change its (semi-static) beam listening mode based on the dynamic indication. In other words, the dynamic indication is used to dynamically update the listening beam. Preferably, in some embodiments, in one example,. Figure 8 The time at which the resources granted by the SL are used for the TX UE corresponds to TTI n, n+4, n+8, and the selected destination may correspond to RX UE1 (based on the priority of the highest MAC CE and / or logical channel with available data). RX UE1 receives the SCI in TTI n (wherein the L1-source ID is set to be associated with the TX UE and the L1-destination ID is set to be associated with RX UE1) (using beam A). Preferably, in some embodiments, the TX UE indicates a beam change to the paired RX UE1, or the RX UE1 indicates a beam change to the paired TX UE for a unicast link between the TX UE and RX UE1. Preferably, in some embodiments, before time tc, the used / indicated beam pair for the TX UE and RX UE1 corresponds to beam X and beam A. Preferably, in some embodiments, after time tc, the used / indicated beam pair for the TX UE and RX UE1 corresponds to beam Y and beam B. Preferably, in some embodiments, based on the SCI received in TTI n indicating TTI n+4 and TTI n+8..., the RX UE determines the beam used for monitoring / receiving in TTI n+4 (and n+8) via the currently used / indicated beam. In this instance, the currently used / indicated beam for TTI n+4 (and n+8) is beam B (from the perspective of RX UE1). Preferably, in some embodiments, for TTI n+6, RX UE1 receives / monitors SL resources based on beam A. Preferably, in some embodiments, when there is no beam change between the TTI indicating the reception of the reserved SCI and the TTI of the reservation opportunity, RX UE1 does not change the beam used for monitoring / receiving in TTI n+6. For another example, the RX UE does not provide exchange information in response to the dynamic indication. Alternatively, once the dynamic indication indicates resource reservation, and there is a beam change between one resource with the reservation indicated by the SCI and another resource indicated by the SCI, the dynamic indication may trigger the RX UE to provide the exchange information to the paired UE. Preferably, in some embodiments, for example, Figure 8 If RX UE1 and TX UE2 (not in Figure 8) has another unicast link, then RX UE1 transmits beam change information of TTI n+4 and TTI n+8 in response to receiving SCI in TTI n, and there is a beam (pair) change between TTI n and TTI n+4. In another example, when the RX UE does not change the beam used for monitoring / reception (and / or keeps using the currently used / indicated beam), the RX UE does not dynamically change or update the beam monitoring mode. In this example, RX UE2 may receive SCI indicating the reservation in TTI n+6 in TTI n+2, and RX UE2 receives SL resources in TTI n+6 based on beam C. Preferably, in some embodiments, the TX UE has two panels associated with a number of antenna elements. Preferably, in some embodiments, beam X and beam Y of the TX UE may correspond to different UE panels. Preferably, in some embodiments, for the first panel generating beam X, the TX UE may transmit beams X1, X2, X3, ... based on the antenna elements (in the first panel). Preferably, in some embodiments, for the second panel generating beam Y, the TX UE may transmit beams Y1, Y2, Y3, ... based on the antenna elements (in the second panel).

[0640] The RX UE will update the listening beam based on the currently used / indicated beam pair between the TX UE and the RX UE.The listening beam of the TTI based on the beam listening mode may be the same or different based on the currently used / indicated beam pair between the TX UE and the RX UE.

[0641] Preferably, in some embodiments, the exchange information transmitted to the first UE via the second UE indicates a beam listening mode (one or more than one beam). Preferably, in some embodiments, the beam listening mode is associated with a TTI for listening to SCI. Preferably, in some embodiments, the beam listening mode is associated with a TTI for listening to PSSCH. Preferably, in some embodiments, the beam listening mode is associated with a TTI for listening to PSFCH. Alternatively, the beam listening mode excludes occasions for PSFCH. Preferably, in some embodiments, the beam listening mode is associated with a TTI for listening to SL synchronization signal blocks (SSBs). Preferably, in some embodiments, the beam listening mode is associated with a TTI for listening to CSI-RS for beam management. For example, the sidelink resource pool is configured with a PSFCH periodicity X slots, and slots 0, X-1, 2X-1, 3X-1 in the sidelink resource pool include PSFCH. When the second UE transmits (exchanges) information indicating time slots 0, 2X-1, 4x-1 to the first UE, this means that the second UE monitors SCI via an RX beam associated with the beam pair between the first UE and the second UE. Preferably, in some embodiments, the second UE monitors / receives SCI in time slots 0, 2X-1, 4X-1 via an RX beam associated with the first UE. Preferably, in some embodiments, when time slots 0, 2X-1, 4X-1 include PSFCH occasions in the side link resource pool, the second UE determines the TX / RX beam used to transmit or monitor the PSFCH occasions, wherein the TX / RX beam used to transmit or monitor the PSFCH occasions may be the same as or different from the RX beam used to receive SCI in the transmitted exchange information. Preferably, in some embodiments, unless the second UE receives another dynamic signal indicating a change in the beam used to monitor / receive in one of the time slots 0, 2X-1, 4X-1, the second UE monitors / receives SCI via the RX beam associated with the first UE.

[0642] Preferably, in certain embodiments, exchanging information may mean that the second UE will not only transmit information to the first UE, but also receive information from the first UE.

[0643] Preferably, in some embodiments, the exchange information may indicate a beam listening mode associated with a specific RX beam associated with a beam pair of the first UE.

[0644] Preferably, in certain embodiments, the specific RX beam is from the second UE to receive or listen to the sidelink transmission from at least the first UE.

[0645] Preferably, in certain embodiments, the exchange information may indicate a beam listening mode associated with all RX beams.

[0646] Preferably, in certain embodiments, the exchange information may indicate a beam listening mode associated with a subset of RX beams, wherein the subset of RX beams includes a specific RX beam associated with a beam pair of the first UE.

[0647] Preferably, in some embodiments, the UE monitors / receives SL resources based on one beam in one TTI.

[0648] Preferably, in certain embodiments, through the present disclosure, beams may be replaced by spatial relationships, spatial filters, TCI states, source RS and / or (Type-D) QCL assumptions.

[0649] Preferably, in some embodiments, the UE monitors / receives SL resources based on more than one beam in one TTI.

[0650] Preferably, in certain embodiments, the number of more than one beams is based on the capabilities of the UE.

[0651] Preferably, in certain embodiments, the number of more than one beams may be based on the number of panels of the UE.

[0652] Preferably, in some embodiments, the number of more than one beams may be up to the number of panels of the UE.

[0653] Preferably, in certain embodiments, for a beam change / update situation, the first UE may perform the above behavior / embodiment / method or take into account that a beam problem occurs after or in response to the first UE receiving a SL HARQ ACK in response to transmitting a signal indicating a beam change. Preferably, in certain embodiments, for a beam change / update situation, the first UE may perform the above behavior / embodiment / method or take into account that a beam problem occurs after or in response to the first UE transmitting a SL HARQ ACK in response to receiving a signal indicating a beam change.

[0654] Preferably and / or alternatively, for a beam change / update situation, the first UE may perform the above behavior / embodiment / method or take into account that a beam problem occurs after or in response to the first UE receiving a signal indicating a beam change. Preferably and / or alternatively, for a beam change / update situation, the first UE may perform the above behavior / embodiment / method or take into account that a beam problem occurs after or in response to the first UE transmitting a signal indicating a beam change.

[0655] Exemplary embodiments of the present invention are described below.

[0656] refer to Fig. 9, through this and other concepts, systems and methods of the present invention, a method 1000 for a first UE (associated with a first destination) to perform a sidelink transmission in a sidelink resource pool includes: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE (step 1002); transmitting information associated with a TTI set to a network node, wherein, preferably in some embodiments, the TTI set corresponds to the second UE monitoring / receiving an SCI in the sidelink resource pool via a paired beam associated with the first UE, and alternatively in some embodiments, the information associated with the TTI set corresponds to a preferred TTI provided by the first UE to the network node (step 1004); having available sidelink data associated with the second UE (step 1006); transmitting a BSR including the sidelink data to the network node (step 1008); and receiving a sidelink grant for scheduling one or more sidelink resources from the network node (step 1010).

[0657] Preferably, in some embodiments, the first UE determines information associated with the TTI set (to be reported to the network node) based on at least one UE monitoring the SCI in the side link resource pool in the TTI set via an RX beam associated with the first UE.

[0658] Preferably, in certain embodiments, the first UE determines information associated with the TTI set (to be reported to the network node) such that a later received SL grant (from the network node) schedules at least one TTI in the TTI set.

[0659] Preferably, in certain embodiments, the first UE determines information associated with a set of TTIs (to be reported to the network node) based on at least one destination having available sidelink data and monitoring SCI in the set of TTIs in the sidelink resource pool.

[0660] Preferably, in certain embodiments, the first UE determines information associated with a set of TTIs (to be reported to the network node) based on the destination having the highest priority of available sidelink data and the destination listening to the SCI in the set of TTIs in the sidelink resource pool.

[0661] Preferably, in certain embodiments, a transmitted BSR (including sidelink data for one or more destinations) is associated with a set of TTIs based on the destination having the highest priority of available sidelink data (eg, a many-to-one mapping).

[0662] Preferably, in certain embodiments, the transmitted BSR (including sidelink data for one or more destinations) is associated with one or more TTI sets (eg, one-to-one mapping).

[0663] Preferably, in some embodiments, the first UE receives information associated with the TTI set from the second UE.

[0664] Preferably, in certain embodiments, the first UE expects the one or more sidelink resources to be in a TTI within the TTI set.

[0665] Preferably, in certain embodiments, the first UE performs sidelink transmission to the second UE via the first TX beam.

[0666] Preferably, in certain embodiments, once the first UE receives information associated with the second TTI set from the second UE: the first UE transmits the information associated with the second TTI set to the network node, and / or the transmission will update the beam monitoring mode associated with the second UE, and / or the transmission may include information associated with the second TTI set and the L1 / L2 destination of the second UE.

[0667] Preferably, in certain embodiments, when or in response to receiving a signal indicating a beam change from a second UE or transmitting a signal to a second UE, the first UE transmits information associated with an updated TTI set, wherein the second UE monitors / receives the SCI in the side link resource pool via the new beam.

[0668] Preferably, in some embodiments, the TTI set corresponds to a beam listening mode.

[0669] Preferably, in certain embodiments, the TTI set corresponds to or indicates an opportunity or time slot / symbol in which the second UE monitors or receives the SCI in the sidelink resource pool via a beam (e.g., a beam pair) associated with the first UE.

[0670] Preferably, in certain embodiments, the set of TTIs corresponds to the second UE waking up for listening to the SCI via the RX beam associated with the beam pair used for the link between the first UE and the second UE.

[0671] Preferably, in certain embodiments, when the first UE establishes a new unicast link to a third UE, the first UE transmits information associated with a third TTI set to the network node, wherein the third TTI set corresponds to the SCI in the side link resource pool monitored / received by the third UE via a paired beam associated with the first UE.

[0672] Preferably, in certain embodiments, information associated with a set of TTIs is transmitted to the network node, and transmitting the BSR corresponds to the same message or on the same TTI.

[0673] Preferably, in certain embodiments, information associated with a set of TTIs is transmitted to a network node, and transmitting BSRs is performed in different TTIs.

[0674] Preferably, in certain embodiments, the transmitted BSR includes information associated with a TTI set.

[0675] Preferably, in some embodiments, the transmitted BSR and the information associated with the TTI set correspond to different MAC CEs.

[0676] Preferably, in certain embodiments, the transmitted BSR includes sidelink data associated with a subset of one or more destinations, the subset having available sidelink data.

[0677] Preferably, in certain embodiments, each destination / UE of a subset of one or more destinations is associated with information of one TTI set.

[0678] Preferably, in certain embodiments, the information of a set of TTIs (associated with one destination / UE via one RX beam) corresponds to a periodicity, offset and / or activity duration, and / or a bitmap indicating a periodic TTI of one destination / UE listening to the SCI in the sidelink resource pool via one RX beam (associated with the first UE), and, for example, a bitmap having an X-bit position indicating one TTI that can be indicated by the bitmap, TTIs "y+kX" to "y+(k+1)X-1", where y corresponds to a reference TTI and k represents a periodic TTI.

[0679] Preferably, in some embodiments, a TTI corresponds to a time slot, a subframe, a subslot, one or more symbols.

[0680] Preferably, in certain embodiments, the first UE has available sidelink data associated with a subset of the one or more destinations.

[0681] Return to reference Figure 3 and 4In one or more embodiments from the perspective of a first UE (associated with a first destination) performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 can execute the program code 312 to: (i) perform one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE; (ii) transmit information associated with a set of TTIs to a network node, wherein, preferably in some embodiments, the set of TTIs corresponds to an SCI in a sidelink resource pool that the second UE listens to / receives via a paired beam associated with the first UE, and alternatively in some embodiments, the information associated with the set of TTIs corresponds to a preferred TTI provided to the network node by the first UE; (iii) have available sidelink data associated with the second UE; (iv) transmit a BSR including the sidelink data to the network node; and (v) receive a sidelink grant from the network node scheduling one or more sidelink resources. In addition, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

[0682] refer to Fig.10 , through this and other concepts, systems and methods of the present invention, a method 1020 for a first UE (associated with a first destination) to perform a sidelink transmission in a sidelink resource pool includes: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE (step 1022); having available sidelink data associated with the second UE (step 1024); transmitting a BSR including the sidelink data to a network node (step 1026); and receiving a sidelink grant for scheduling one or more sidelink resources from the network node (step 1028).

[0683] Preferably, in certain embodiments, the first UE has available sidelink data associated with a subset of the one or more destinations.

[0684] Preferably, in some embodiments, the first UE determines the destination based on the highest priority of the logical channel associated destination among the subset of destinations.

[0685] Preferably, in certain embodiments, the first UE does not perform or skips or cancels or revokes sidelink transmission using sidelink resources in accordance with SL grant in a TTI that is not within a TTI in which the SCI is monitored at the determined destination via an RX beam associated with the first UE.

[0686] Preferably, in certain embodiments, when all sidelink resources according to the SL grant are in a TTI within a TTI in which the SCI is monitored via an RX beam associated with the first UE at a determined destination, the first UE discards the entire SL grant.

[0687] Preferably, in some embodiments, the SL grant indicates sidelink resources in TTI t1, t2 (if present), t3 (if present), and / or the timing order is TTI t1 earlier than TTI t2, and TTI t2 earlier than TTI t3.

[0688] Preferably, in certain embodiments, when TTI t1 is within a TTI in which the determined destination monitors SCI via an RX beam associated with the first UE, the first UE performs sidelink transmission via a TX beam associated with the beam pair of the destination in TTI t1.

[0689] Preferably, in certain embodiments, based on whether the first UE receiving the determined / selected destination indicates support for dynamically changing beam listening mode from the determined / selected destination, it is determined whether to perform sidelink transmission via a new beam (associated with the first UE) in a future TTI according to SL grant.

[0690] Preferably, in certain embodiments, when the determined destination is unable to change the beam listening mode, the first UE performs sidelink transmission on a future TTI via the original beam according to the SL grant.

[0691] Preferably, in certain embodiments, when the determined destination is unable to change the beam listening mode, the first UE drops the sidelink transmission on the future TTI according to the SL grant, and the determined destination does not listen to the SCI via the new beam (associated with the first UE).

[0692] Preferably, in some embodiments, the first UE expects TTIs t1, t2, t3 to be within a set of TTIs reported by the first UE to the network node.

[0693] Preferably, in some embodiments, TTIs t1, t2, and t3 may correspond to one beam listening mode of the same destination.

[0694] Preferably, in some embodiments, TTIs t1, t2, t3 may correspond to one beam listening mode for more than one destination.

[0695] Preferably, in certain embodiments, when / once the first UE changes beam pair between TTI t1 and TTI t2 (which means that even TTI t1 and TTI t2 are within a TTI for monitoring SCI via one RX beam, disadvantageously, one RX beam is now not functioning properly), or TTI t1 and TTI t2 are associated with monitoring timings of different beams for one destination, or TTI t1 is within a TTI for monitoring SCI via one RX beam at the determined destination and TTI t2 is not within a TTI for monitoring SCI via another RX beam at the determined destination, the first UE performs sidelink transmission at TTI t2 or t3 via the current or updated / used / indicated beam at TTI t2 or t3 according to SL grant.

[0696] Preferably, in certain embodiments, when there is an SCI indicating TTI t2 transmitted via the first UE in TTI t1 and / or indicating t3 via the TRIV field, the first UE may perform sidelink transmission at TTI t2 or t3 via the current or updated / used / indicated beam at TTI t2 or t3 according to SL grant.

[0697] Preferably, in some embodiments, a specific timing is used to apply a new beam, and TTI t1 is earlier than the specific timing, and TTI t2 and TTI t3 are later than the specific timing.

[0698] Preferably, in certain embodiments, the same TB or the same MAC PDU transmission is associated with a SL grant.

[0699] Preferably, in certain embodiments, when TTI t1 is not within the TTI of the determined destination via the RX beam associated with the first UE monitoring SCI, the first UE discards the entire SL grant and / or (trigger) transmission of information associated with a fourth TTI set of the determined destination via the RX beam associated with the first UE monitoring SCI (especially scheduling retransmission on a matching TTI for a later received SL grant).

[0700] Preferably, in certain embodiments, when TTI t1 is not within a TTI in which the determined destination monitors SCI via an RX beam associated with the first UE, the first UE drops the sidelink transmission at TTI t1 according to the SL grant.

[0701] Preferably, in some embodiments, when the first UE discards the sidelink transmission at TTI t1, the first UE may perform the sidelink transmission at a future TTI according to the SL grant.

[0702] Return to reference Figure 3 and 4, in one or more embodiments from the perspective of a first UE (associated with a first destination) performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) perform one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE; (ii) have available sidelink data associated with the second UE; (iii) transmit a BSR including the sidelink data to a network node; and (iv) receive a sidelink grant from the network node scheduling one or more sidelink resources. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0703] refer to Fig.11 , through this and other concepts, systems and methods of the present invention, a method 1030 for a first UE (associated with a first destination) to perform sidelink transmission in a sidelink resource pool includes: having available sidelink data associated with a second UE and a third UE (step 1032); determining whether to trigger an SR or BSR including sidelink data available for other UEs based on whether there is a beam problem between the links of the first UE and the other UEs (step 1034); when the first UE has a beam problem with the second UE, the first UE does not trigger an SR or BSR including available sidelink data associated with the second UE (step 1036); and receiving a sidelink grant for one or more sidelink resources in a scheduling TTI from a network node (step 1038).

[0704] Preferably, in some embodiments, when the first UE has no beam problem with the third UE, the first UE triggers an SR or a BSR including the sidelink data associated with the third UE.

[0705] Preferably, in certain embodiments, the first UE transmits an SR or BSR including available sidelink data associated with the third UE to the network node.

[0706] Preferably, in certain embodiments, when the first UE transmits the BSR to the network node, the BSR does not include available sidelink data associated with the second UE.

[0707] Preferably, in certain embodiments, beam problems may occur at time intervals or during intervals.

[0708] Preferably, in some embodiments, the beam problem corresponds to the number of times the first UE determines that the quality of the link via the currently used or indicated beam (pair) is lower than a threshold and / or the number of times the quality of the link via the candidate beam (pair) is higher than a second threshold.

[0709] Preferably, in certain embodiments, the beam problem is determined in response to transmitting a signal to the second UE or receiving a signal from the second UE indicating a beam change.

[0710] Preferably, in certain embodiments, beam issues are determined to be unresolved prior to a specific opportunity for applying a newly indicated / used beam(s).

[0711] Preferably, in certain embodiments, the first UE determines not to transmit a BSR including available sidelink data associated with the second UE before a specific opportunity.

[0712] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a first UE (associated with a first destination) performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) have available sidelink data associated with a second UE and a third UE; (ii) determine whether to trigger an SR or BSR including sidelink data available for other UEs based on whether there is a beam problem between the first UE and the other UEs' links; (iii) when the first UE has a beam problem with the second UE, the first UE does not trigger an SR or BSR including available sidelink data associated with the second UE; and (iv) receive a sidelink grant from a network node scheduling one or more sidelink resources in a TTI. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

[0713] refer to Fig.12 , through this and other concepts, systems and methods of the present invention, a method 1040 for a first UE (associated with a first destination) to perform a sidelink transmission in a sidelink resource pool includes: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE and preferably in some embodiments a third destination associated with a third UE, wherein the first UE uses one TX beam for each unicast sidelink transmission with one destination (step 1042); preferably in some embodiments, receiving (exchanging with) information from one or more destinations (step 1044); and performing a unicast sidelink transmission to a second UE via one TX beam, wherein one TX beam is associated with a beam pair for a link between the first UE and the second UE (step 1046).

[0714] Preferably, in certain embodiments, the first UE maintains a beam pair with each of the one or more destinations.

[0715] Preferably, in certain embodiments, the (exchange) information indicates one or more TTIs in which the source destination transmits the (exchange) information, wherein the source destination transmits the (exchange) information via an RX beam monitoring / receiving SCI in a side link resource pool, and wherein preferably, the RX beam is associated with a currently used / indicated beam pair for a link between the first UE and the source destination.

[0716] Preferably, in certain embodiments, based on the (exchanged) information, the first UE determines a TTI, wherein each of the one or more destinations monitors / receives a SCI in a side link resource pool via an RX beam associated with a beam pair corresponding to the first UE.

[0717] Preferably, in certain embodiments, when the beam pair used for a link between a first UE and a second UE does not change, the first UE determines or selects one or more SL resources in a TTI associated with or within one or more TTIs, wherein the second UE monitors / receives the SCI in the side link resource pool via the corresponding RX beam.

[0718] Preferably, in certain embodiments, the first UE changes or updates a currently used / indicated or currently maintained TX beam associated with a beam pair used for a link between the first UE and the second UE.

[0719] Preferably, in certain embodiments, when the first UE determines or identifies via the TX beam that the quality of the link is poor, the first UE changes or updates the currently used / indicated or currently maintained TX beam of the link.

[0720] Preferably, in certain embodiments, when the first UE determines or identifies that the quality of the link via the TX beam is poor, the first UE indicates a change / update of the currently used / indicated TX beam of the beam link.

[0721] Preferably, in certain embodiments, the first UE or a paired UE / destination for a link may transmit signals indicating beam changing information to each other.

[0722] Preferably, in certain embodiments, in response to receiving the signal, the first UE or paired UE / destination changes or updates the currently used / indicated or currently maintained TX beam and / or RX beam for the link.

[0723] Preferably, in some embodiments, the specific timing for applying the new indication / use / maintaining the beam pair is based on a duration / interval that is later than the timing of receiving the signal or the timing at which the PSFCH includes a HARQ associated with the signal, and preferably in some embodiments, the HARQ associated with the signal is ACK, or preferably ACK or NACK.

[0724] Preferably, in certain embodiments, in response to receiving a signal from a paired UE of the link, the first UE or paired UE / destination transmits a HARQ associated with the signal to the paired UE of the link.

[0725] Preferably, in some embodiments, the specific timing for applying the new indicated / used / maintained beam pair is based on the timing when the PSFCH includes the HARQ associated with the signal.

[0726] Preferably, in certain embodiments, both the first UE and the paired UE / destination apply the new beam pair for the link from or after a specific occasion.

[0727] Preferably, in certain embodiments, the signal may be associated with a PSSCH transmission in the same TTI (used to transmit the signal).

[0728] Preferably, in some embodiments, the signal corresponds to level 1 SCI, level 2 SCI and / or MAC CE in PSSCH.

[0729] Preferably, in some embodiments the signal indicates a beam different from the currently used / indicated beam.

[0730] Preferably, in certain embodiments, the signal is a beam report or is in response to a beam report from a paired UE for the link.

[0731] Preferably, in some embodiments, the signal indicates that the quality of the currently used / indicated beam for the link is below a threshold, and / or that the quality of the candidate beams for the link is above a threshold.

[0732] Preferably, in certain embodiments, signaling a beam different from a currently used / indicated beam means or corresponds to signaling a change of beam for the link.

[0733] Preferably, in certain embodiments, based on (an indication of) the signal or based on the presence of a signal, the first UE updates the TX beam used for the link.

[0734] Preferably, in certain embodiments, the first UE determines the indication of which pair the signal is for based on the L1 or L2 source identity / ID transmitting the signal.

[0735] Preferably, in certain embodiments, when the first UE is the UE transmitting the signal, the paired UEs determine an indication of which pair the signal is for based on the L1 or L2 source identity / ID.

[0736] Preferably, in certain embodiments, the signal may include (exchange) information associated with the new beam.

[0737] Preferably, in certain embodiments, the signal may indicate to the receiving UE (ie, which is transmitting the signal) which TTI of its TTI to use for receiving / listening to the SCI via the new RX beam (for the new beam pair according to the signal).

[0738] Preferably, in certain embodiments, the (exchanged) information includes a number of RX beams used by the receiving UE to monitor / receive the SCI in the sidelink resource pool and / or each TTI associated with each of the number of RX beams.

[0739] Preferably, in certain embodiments, the (exchanged) information may provide more than one RX beam and each corresponding TTI for the receiving UE to monitor / receive the SCI in the side link resource pool via each (provided) RX beam.

[0740] Preferably, in some embodiments, the (exchanged) information includes one or more periodicities and one or more offsets associated with one or more RX beams, wherein based on a periodicity and an offset associated with an RX beam, a beam monitoring mode or TTI for a receiving UE to receive / monitor an SCI in a side link resource pool via an RX beam is determined.

[0741] Preferably, in certain embodiments, the signal comprises a bitmap indicating which RX beam the receiving UE (which transmits the signal) uses for listening / receiving the SCI with respect to its TTI, and preferably each bit position in the bitmap corresponds to one RX beam of the receiving UE.

[0742] Preferably, in certain embodiments, the signal includes a field indicating which RX beam or TTI is associated with the new beam pair for the link.

[0743] Preferably, in some embodiments, the code point of the field indicates an RX beam.

[0744] Preferably, in certain embodiments, the code point of the field indicates which TTIs are associated with the new beam pair for the link.

[0745] Preferably, in certain embodiments, the first UE determines one or more TTI sets (based on PC5RRC signaling or information between the link of the first UE and the second UE or based on exchanged information), wherein each TTI set is associated with an RX beam (associated with the second UE).

[0746] Preferably, in certain embodiments, the first UE transmits a unicast sidelink transmission to the second UE based on a first set of TTIs, wherein the first set of TTIs is associated with a currently used / indicated beam pair.

[0747] Preferably, in certain embodiments, the signal indicates a set of TTIs that is different from a previous set of TTIs.

[0748] Preferably, in certain embodiments, based on the signal, the first UE changes the timing of unicast sidelink transmission to the second UE from a first TTI set to a second TTI set, wherein the second TTI set is associated with a currently used / indicated beam pair.

[0749] Preferably, in certain embodiments, when or after a (unicast) link is established between the first UE and the second UE, the first UE may know or determine or identify or obtain one or more TTI sets from the second UE.

[0750] Preferably, in certain embodiments, when or after a (unicast) link is established between the first UE and the second UE, the first UE may know or determine or identify or obtain at least one TTI set from the second UE.

[0751] Preferably, in some embodiments, at least one TTI set is associated with a beam pair used for a link (including a TX beam of a first UE and / or an RX beam of a second UE currently used / indicated), or at least one TTI set is associated with an RX beam of a second UE used for receiving / listening to an SCI in a side link resource pool (the SCI is transmitted at least from the first UE).

[0752] Preferably, in certain embodiments, in response to receiving the signal, the first UE or the paired UEs transmit (exchange) information associated with the new beam (e.g., RX beam).

[0753] Preferably, in certain embodiments, the (exchanged) information may disclose or indicate the TTIs at which the receiving UE monitors / receives the SCI via the new RX beam in the sidelink resource pool (which is associated with the new beam pair for the link).

[0754] Preferably, in some embodiments, the specific opportunity is a time interval or duration later than an opportunity to transmit (exchange) information.

[0755] Preferably, in some embodiments, the specific occasion is an occasion for receiving / transmitting (exchanging) information.

[0756] Preferably, in some embodiments, the exchange information transmitted to the first UE via the second UE indicates a beam listening mode (one or more than one beam).

[0757] Preferably, in some embodiments, the beam listening mode is associated with a TTI for listening to the SCI.

[0758] Preferably, in some embodiments, the beam listening mode is associated with a TTI for monitoring the PSSCH.

[0759] Preferably, in some embodiments, the beam listening mode excludes the occasions for PSFCH.

[0760] Preferably, in certain embodiments, exchanging information may mean that the second UE will not only transmit information to the first UE, but also receive information from the first UE.

[0761] Preferably, in some embodiments, the exchange information may indicate a beam listening mode associated with a specific RX beam associated with a beam pair of the first UE.

[0762] Preferably, in certain embodiments, the specific RX beam is from the second UE to receive or listen to the sidelink transmission from at least the first UE.

[0763] Preferably, in certain embodiments, the exchange information may indicate a beam listening mode associated with all RX beams.

[0764] Preferably, in certain embodiments, the exchange information may indicate a beam listening mode associated with a subset of RX beams, wherein the subset of RX beams includes a specific RX beam associated with a beam pair of the first UE.

[0765] Preferably, in some embodiments, once the first UE or the second UE changes its beam listening mode associated with one RX beam, the first UE or the second UE will need to notify the paired UE that the first UE or the second UE uses the RX beam for listening.

[0766] Preferably, in some embodiments, when the second UE changes the beam listening mode associated with the RX beam from the first TTI set to the second TTI set, the second UE information at least notifies the first UE that the beam listening mode associated with the RX beam is changed to the second TTI set.

[0767] Preferably, in certain embodiments, a transmitter UE (eg, a first UE) may transmit a request to a receiving UE (eg, a second UE) to request one or more beam listening modes (not just a specific RX beam associated with the beam pair of the first UE).

[0768] Preferably, in certain embodiments, in response to receiving the request to request a (beam) listening pattern, the second UE transmits one or more listening patterns to the first UE.

[0769] Preferably, in certain embodiments, determining or identifying the quality of a link or a link of a beam pair via a TX beam or an RX beam may be based on one or more criteria.

[0770] Preferably, in some embodiments, one or more criteria are based on any one or any combination of: the number of times the quality of the RX beam of the first UE associated with the TX beam is below a threshold, and / or a request from a second UE indicating a beam change, and / or a beam report from the second UE, and / or a second number of times the quality of a candidate RX beam associated with a candidate TX beam for the link is above a second threshold, and / or the absence of the current TX beam in the beam report from the second UE, and / or the indication of the current TX beam in a blacklist, and / or the indication of the candidate TX beam in a whitelist.

[0771] Preferably, in certain embodiments, based on exchanged information from one or more UE / destinations, the first UE determines the beam listening mode for each UE / destination associated with the first UE, or the first UE determines which TTIs are active (for each UE / destination to listen to SCI) based on the currently used / indicated beam pairs for the link between the first UE and each UE / destination.

[0772] Preferably, in certain embodiments, the first UE determines or selects the destination based on whether the destination is active for a link between the first UE at any of TTIs t1, t2, t3 according to the SL grant.

[0773] Preferably, in certain embodiments, the first UE determines or selects the destination based on whether the destination monitors the SCI in the side link resource pool via a beam pair associated with the first UE at any one of TTIs t1, t2, t3 according to the SL grant.

[0774] Preferably, in certain embodiments, the first UE determines or selects the destination based on whether the destination is active for a link between the first UE at TTI t1 according to the SL grant.

[0775] Preferably, in certain embodiments, the first UE determines or selects the destination based on whether the destination monitors the SCI in the sidelink resource pool via a beam pair associated with the first UE at TTI t1 according to the SL grant.

[0776] Preferably, in certain embodiments, the determined / selected destination is associated with a logical channel having available sidelink data, and the logical channel has the highest priority among multiple logical channels associated with one or more destinations having available sidelink data.

[0777] Preferably, in some embodiments, the first UE determines that the third UE is inactive at TTI t1 when TTI t1 is not within a TTI in which the third UE monitors SCI via an RX beam associated with the first UE or when the exchange information from the third UE does not include TTI t1.

[0778] Preferably, in certain embodiments, the first UE determines that the second UE is active at TTI t1 when TTI t1 is within a TTI in which the second UE monitors SCI via an RX beam associated with the first UE or when exchange information from the second UE includes TTI t1.

[0779] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a first UE (associated with a first destination) performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes program code 312 stored in a memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) perform one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE and preferably, in some embodiments, a third destination associated with a third UE, wherein the first UE uses one TX beam for each unicast sidelink transmission with one destination; (ii) preferably, in some embodiments, receive (exchange) information from one or more destinations; and (iii) perform a unicast sidelink transmission to a second UE via one TX beam, wherein one TX beam is associated with a beam pair for a link between the first UE and the second UE. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0780] refer to Fig.13 , through this and other concepts, systems and methods of the present invention, a method 1050 for a first UE (associated with a first destination) to perform a sidelink transmission in a sidelink resource pool includes: transmitting an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam, wherein the SCI indicates reserved resources in a second TTI (step 1052); and preferably in some embodiments, based on the first UE performing a sidelink transmission in a sidelink resource allocation mode, determining whether to perform a sidelink transmission on the reserved resources in the second TTI via a second TX beam different from the first TX beam (step 1054).

[0781] Preferably, in some embodiments, when the first UE is configured with sidelink resource allocation mode-1, the first UE may perform sidelink transmission on the reserved resources in the second TTI via the second TX beam.

[0782] Preferably, in certain embodiments, when the first UE is configured with sidelink resource allocation mode-2, the first UE may perform sidelink transmission on the reserved resources in the second TTI via the first TX beam (of the first UE).

[0783] Preferably, in certain embodiments, the first UE determines or selects a second destination associated with a second TX beam (of the first UE) (for sidelink transmission on the reserved resources in the second TTI).

[0784] Preferably, in certain embodiments, the first UE is not allowed to determine or select a second destination (for sidelink transmission on the reserved resources in the second TTI) that is not associated with the first TX beam (of the first UE).

[0785] Preferably, in certain embodiments, if the first UE determines or selects a second destination (for sidelink transmission on reserved resources in a second TTI) that is not associated with the first TX beam (of the first UE) (based on the highest priority of logical channels with available sidelink data), the first UE triggers resource reselection for sidelink transmission to the second destination.

[0786] Preferably, in certain embodiments, the first UE triggers resource reselection for sidelink transmission based on a TTI in which the second destination is active or via paired beam monitoring SCI.

[0787] Preferably, in certain embodiments, (based on the highest priority of logical channels with available sidelink data) if the first UE determines or selects a second destination that is not associated with the first TX beam (of the first UE) (for sidelink transmission on reserved resources in the second TTI), the first UE transmits a signal to the second destination to indicate a change of the RX beam on the second TTI, or the first UE transmits a second SCI on a third TTI where the second destination is active, wherein the second SCI on the third TTI reserves the second TTI.

[0788] Preferably, in certain embodiments, based on the signal indicating to change the RX beam on the second TTI, the second destination monitors the second TTI via the paired RX beam associated with the first UE (and if the second destination has reported the ability to dynamically change the beam listening mode).

[0789] Preferably, in certain embodiments, when a second destination (e.g., a second UE) receives more than one SCI (including a first SCI) indicating a reservation for a second TTI, the second destination determines to monitor the SCI via a beam on the second TTI based on the priority indicated by the more than one SCI and / or a new transmission or retransmission on the second TTI.

[0790] Preferably, in some embodiments, the second destination determines to listen to the SCI on the second TTI based on at least one SCI having the highest priority among the more than one SCIs.

[0791] Preferably, in some embodiments, the second destination determines to listen to the SCI at the second TTI based at least on the retransmission at the second TTI.

[0792] Preferably, in some embodiments, the second destination determines to listen to the SCI at the second TTI based at least on the new transmission at the second TTI.

[0793] Preferably, in certain embodiments, when determining that the second TTI is associated with the first TX beam, the first UE selects or determines the second destination based on the second destination by monitoring the SCI via the paired RX beam associated with the first UE at the second TTI.

[0794] Preferably, in certain embodiments, when the first UE is unable to select or determine a third destination (for sidelink transmission via the first TX beam on the second TTI), or when there is no paired destination for monitoring SCI via the paired RX beam associated with the first UE on the second TTI, the first UE triggers resource reselection and / or the first UE discards reserved resources on the second TTI.

[0795] Preferably, in certain embodiments, when the first UE is in sidelink resource allocation mode-1, the first UE may perform sidelink transmission via the second TX beam on the second TTI when the beam pair used for the link between the first UE and the second UE changes (e.g., from the first TX beam to the second TX beam).

[0796] Preferably, in certain embodiments, when the first UE is in sidelink resource allocation mode-1, the first UE is not allowed to perform sidelink transmission via the second TX beam on the second TTI when the beam pair used for the link between the first UE and the second UE changes (e.g., from the first TX beam to the second TX beam).

[0797] Preferably, in certain embodiments, for sidelink resource allocation mode-1, the first UE determines whether to perform sidelink transmission on the second TTI via the second TX beam based on reserved resources on the second TTI associated with a (dynamic) SL grant or a SL configured grant.

[0798] Preferably, in certain embodiments, for the SL configured grant, the first UE is not allowed to perform sidelink transmission on the second TTI via the second TX beam (if the SL configured grant is associated with the first TX beam).

[0799] Preferably, in certain embodiments, for a SL configured grant, the first UE may perform a sidelink transmission on a second TTI via the second TX beam (in the event that the SL configured grant is not associated with the first TX beam).

[0800] Preferably, in certain embodiments, the SL is configured to grant association with one or more TX beams.

[0801] Preferably, in certain embodiments, if the second TX beam is one of the one or more TX beams associated with the SL configured grant, the first UE may perform sidelink transmission on the second TTI via the second TX beam.

[0802] Preferably, in certain embodiments, the SL is configured to grant association with any TX beam.

[0803] Preferably, in certain embodiments, for (dynamic) SL grant, the first UE may perform sidelink transmission on the second TTI via the second TX beam.

[0804] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a first UE (associated with a first destination) performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) transmit an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam, wherein the SCI indicates reserved resources in a second TTI; and (ii) preferably in certain embodiments, based on the first UE performing a sidelink transmission in a sidelink resource allocation mode, determine whether to perform a sidelink transmission on the reserved resources in the second TTI via a second TX beam different from the first TX beam. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0805] refer to Fig.14 Through this and other concepts, systems and methods of the present invention, a method 1060 for a first UE (associated with a first destination) to perform a sidelink transmission in a sidelink resource pool includes: transmitting an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam (step 1062); receiving a configuration associated with an SL CG (with periodicity) from a network node (step 1064); and performing a sidelink transmission on the sidelink resources associated with the SL CG (step 1066).

[0806] Preferably, in some embodiments, the first TTI and the second TTI are associated with the SL CG.

[0807] Preferably, in certain embodiments, the first TTI and the second TTI are spaced or separated by a periodicity associated with the SL CG.

[0808] Preferably, in some embodiments, the sidelink resources on the first TTI and on the second TTI are associated with the same frequency resources (eg, the same set of subchannels).

[0809] Preferably, in certain embodiments, the sidelink resources on the first TTI and on the second TTI are candidate resources for transmissions associated with different MAC PDUs or different TBs.

[0810] Preferably, in certain embodiments, the SL CG may be activated by DCI to be associated with one TX beam of the first UE.

[0811] Preferably, in certain embodiments, the SL CG may be configured to be associated with a TX beam of the first UE.

[0812] Preferably, in certain embodiments, based on characteristics of the SL CG associated with a TX beam, the first UE selects or determines a destination for sidelink transmission on the first TTI or the second TTI based on which destination uses a paired RX beam associated with a TX beam on the first TTI or the second TTI.

[0813] Preferably, in certain embodiments, based on characteristics of the SL CG associated with a TX beam, the first UE does not select or determine another destination for sidelink transmission on the first TTI, wherein the other destination does not use a paired RX beam associated with a TX beam on the first TTI.

[0814] Preferably, in certain embodiments, (if / when the SL CG is not associated with a TX beam), the first UE selects or determines a destination for sidelink transmission on the first TTI or the second TTI based on the LCP procedure (the destination is selected or determined based on the highest logical channel with sidelink data arriving).

[0815] Preferably, in certain embodiments, the LCP procedure may further consider whether one or more (paired) destinations listen / receive SCI (using a paired RX beam associated with the first UE) on the first TTI.

[0816] Preferably, in certain embodiments, the LCP procedure may further consider whether one or more (paired) destinations listen / receive SCI (using the paired RX beam associated with the first UE) on the second TTI.

[0817] Preferably, in certain embodiments, the first UE performs an LCP procedure for sidelink transmission on the first TTI and the second TTI, respectively.

[0818] Preferably, in certain embodiments, based on a destination determined / determined according to an LCP procedure (for sidelink transmission on a first TTI), the first UE determines a first TX beam associated with an RX beam of the determined / determined destination.

[0819] Preferably, in certain embodiments, the determined / selected destination listens to the SCI on a first TTI using the RX beam, and the determined / selected destination is associated with a logical channel with the highest priority of available sidelink data.

[0820] Preferably, in certain embodiments, based on a destination determined / determined according to the LCP procedure (for sidelink transmission on the second TTI), the first UE determines a second TX beam associated with a second RX beam of the determined / determined destination.

[0821] Preferably, in certain embodiments, the determined / selected destination monitors the SCI on the second TTI using the second RX beam, and the determined / selected destination is associated with the highest priority logical channel having available sidelink data.

[0822] Preferably, in some embodiments, the determined / selected destinations for the first TTI, the second TTI may be different or the same.

[0823] Preferably, in some embodiments, the corresponding TX beams used for sidelink transmission on the first TTI and the second TTI may be different or the same.

[0824] Preferably, in some embodiments, when the first TTI and the second TTI are associated with one SL CG, the first UE performs sidelink transmission on the first and second TTIs based on different or the same TX beams.

[0825] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a first UE (associated with a first destination) performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes a program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) transmit an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam; (ii) receive a configuration associated with an SL CG (with periodicity) from a network node; and (iii) perform a sidelink transmission on a sidelink resource associated with the SL CG. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0826] refer to Fig.15, through this and other concepts, systems and methods of the present invention, a method 1070 for a first UE (associated with a first destination) to perform a sidelink transmission in a sidelink resource pool includes: transmitting an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam, wherein the SCI indicates reserved resources in a second TTI (step 1072).

[0827] Preferably, in certain embodiments, the first UE determines the sidelink resources (for transmitting at least the SCS and / or the scheduled PSSCH) in the first TTI based on the sensing results associated with the first TX beam of the first UE.

[0828] Preferably, in certain embodiments, when the first UE determines the side link resources and their periodic reservation in the first TTI, the first UE determines them based on a sensing result associated with a first TX beam of the first UE.

[0829] Preferably, in some embodiments, the sidelink resources on the first TTI and the second TTI may have different or the same subchannels.

[0830] Preferably, in certain embodiments, the first TTI and the second TTI are associated with the same selected SL grant.

[0831] Preferably, in certain embodiments, the first TTI and the second TTI are spaced or separated by a reservation period (which is indicated by the SCI).

[0832] Preferably, in certain embodiments, for the sidelink resources on the second TTI reserved by the SCI in the first TTI, the first UE cannot change the first TX beam for sidelink transmission on the second TTI.

[0833] Preferably, in certain embodiments, for sidelink resources on the second TTI reserved by the SCI in the first TTI, the first UE prioritizes or determines the destinations based on one or more destinations by monitoring the SCI on the second TTI via an RX beam associated with a TX beam.

[0834] Preferably, in certain embodiments, when the first UE determines a destination for sidelink transmission on a second TTI (regardless of the RX UE monitoring the SCI via a paired RX beam associated with one TX beam) and the determined destination is using a second RX beam associated with a second TX beam of the first UE that is different from the first TX beam, the first UE discards the sidelink resources on the second TTI (associated with the selected sidelink grant), and / or the first UE triggers sidelink resource (re)selection (for sidelink transmission on the second TTI) and / or the first UE transmits a signal to change the beam monitoring mode of the RX UE.

[0835] Preferably, in certain embodiments, the first UE may determine whether to perform sidelink transmission via the second TX beam on the second TTI (according to the selected sidelink grant) based on the periodicity threshold.

[0836] Preferably, in certain embodiments, when the first UE determines a destination for sidelink transmission on a second TTI and the determined destination is using a second RX beam associated with a second TX beam of the first UE that is different from the first TX beam, the first UE performs a reassessment of the sidelink resources.

[0837] Preferably, in some embodiments, the first UE may determine whether to perform sidelink transmission on the second TTI (according to the selected sidelink grant) based on whether the CBR and / or CR value is greater than or not greater than a threshold.

[0838] Return to reference Figure 3 and 4 , in one or more embodiments from the perspective of a first UE (associated with a first destination) performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) transmit an SCI to a second UE (associated with a second destination) in a first TTI via a first TX beam, wherein the SCI indicates reserved resources in a second TTI. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0839] refer to Fig.16 , through this and other concepts, systems and methods of the present invention, a method 1080 for a first UE to perform a sidelink transmission in a sidelink resource pool includes: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE (step 1082); and transmitting information indicating a TTI set to a network node, wherein the TTI set corresponds to (a set of opportunities in which) the second UE monitors or receives an SCI in the sidelink resource pool via a second beam associated with the first UE (step 1084).

[0840] In various embodiments, the first UE has available sidelink data associated with the second UE, and / or the first UE transmits a first BSR including further information of the sidelink data to the network node. In various embodiments, the further information may be a buffer size associated with the sidelink data.

[0841] In various embodiments, the UE transmits information together with a first BSR at one time instance, wherein the first BSR corresponds to a regular BSR, or the UE transmits information and the first BSR at different time instances, or the UE transmits a second BSR including information, wherein the second BSR is different from the regular BSR, or the UE transmits a third BSR including information, wherein the third BSR corresponds to a regular BSR and / or a periodic BSR and / or a padding BSR.

[0842] In various embodiments, the first UE triggers transmission of information in response to one or more of the following: receiving an indication from the second UE that a second beam is applied or used or changed or updated relative to a previous beam, and / or an indication that a beam used for listening to or receiving SCI on a side link resource pool is changed (from a third beam to a second beam), or a TTI set is changed or updated or applied or used; and / or determining that a first beam used for side link transmission to the second UE is changed or updated or applied or used; and / or a third destination associated with a third UE is added as a destination of the first UE; and / or having side link data to be transmitted associated with the second UE.

[0843] In various embodiments, the UE transmits information on periodic resources or semi-persistently scheduled resources.

[0844] In various embodiments, the method further includes transmitting a second BSR including an amount of data associated with one or more destinations or a second BSR including an amount of data associated with a subset of one or more destinations, wherein the first UE transmits a second BSR including information associated with one or more TTI sets for the one or more destinations or a second BSR including information associated with one or more TTI sets for a subset of the one or more destinations.

[0845] In various embodiments, after establishing a link with a second UE, or after an initial beam pair procedure, or after a beam failure recovery procedure, the first UE: determines a first beam for sidelink transmission to the second UE, or receives a message from the second UE indicating a listening mode associated with the second beam, or determines a TTI set based on the received message.

[0846] In various embodiments, the information further includes information of the first beam, and / or the first UE provides information of a TTI set associated with the first beam to the network node.

[0847] In various embodiments, after the first UE transmits information, the first UE expects to receive sidelink grant scheduling resources associated with at least one TTI monitored by the destination via the first beam, or the first UE expects to receive sidelink grant scheduling resources on at least one TTI in a set of TTIs associated with the first beam.

[0848] In various embodiments, the method further includes receiving one or more messages from one or more destinations, wherein each of the one or more messages indicates a listening mode associated with a transmitted beam, and information that one of the one or more destinations listens to a TTI transmitted by the side link via a received beam associated with a transmitted beam of the first UE. The receiving beams of different destinations in the one or more destinations are associated with the same or different transmitting beams of the first UE.

[0849] In various embodiments, the first UE has available sidelink data associated with a subset of one or more destinations, and / or the first UE receives a sidelink grant from a network node to schedule one or more sidelink resources in one or more TTIs, and / or the first UE selects or determines a destination from the subset of one or more destinations, wherein the selection or determination is based on one or more received messages regarding the destination listening to a received beam associated with a transmitted beam in a TTI among the one or more TTIs.

[0850] In various embodiments, a TTI among the one or more TTIs corresponds to an earliest TTI or any TTI among the one or more TTIs.

[0851] In various embodiments, if the first UE selects or determines that no destination is monitored via a received beam associated with a transmitted beam in a TTI, or if the first UE is unable to select a destination because no destination is selected or determined to be monitored via a received beam associated with a transmitted beam in a TTI, the first UE discards or ignores the sidelink grant, or does not perform a sidelink transmission on one or more sidelink resources scheduled by the sidelink grant.

[0852] In various embodiments, if the first UE determines that the second destination is not listening via a received beam associated with one of the transmitted beams in a TTI, the first UE does not or is not allowed to select the second destination.

[0853] In various embodiments, the destination is further selected or determined based on the priority of the available sidelink data.

[0854] In various embodiments, the sidelink grant does not provide information associated with which beam is used for sidelink transmission on one or more sidelink resources, and / or the first UE determines the transmitted beam to be used for sidelink transmission on one or more sidelink resources based on a selected or determined destination, and / or when the selected or determined destination is associated with a first transmitted beam, the first UE performs sidelink transmission on one or more sidelink resources via the first transmitted beam.

[0855] In various embodiments, when a sidelink grant provides information associated with a specific beam for sidelink transmission on one or more sidelink resources, the destination is further selected or determined based on the paired transmitted beams being (or corresponding to) the specific beam, and / or when a sidelink grant provides information associated with a specific beam for sidelink transmission on one or more sidelink resources, the destination is selected or determined to be limited to the paired transmitted beams being (or corresponding to) the specific beam, and / or if the first UE determines that a transmitted beam associated with the sidelink transmission is for a third destination and a transmitted beam is not (or does not correspond to) the specific beam, the first UE does not select or is not allowed to select the third destination.

[0856] Return to reference Figure 3 and 4 In one or more embodiments from the perspective of a first UE performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes program code 312 stored in a memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) perform one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second UE; and (ii) transmit information indicating a set of TTIs to a network node, wherein the set of TTIs corresponds to (a set of opportunities in which) the second UE listens to or receives an SCI in the sidelink resource pool via a second beam associated with the first UE. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0857] refer to Fig.17, through this and other concepts, systems and methods of the present invention, a method 1090 for a first UE to perform sidelink transmissions in a sidelink resource pool includes: performing one or more unicast sidelink transmissions with one or more destinations, wherein the first UE determines to apply a transmitted beam for sidelink transmissions to each of the one or more destinations (step 1092); receiving one or more messages from the one or more destinations, wherein each of the one or more messages indicates a listening mode associated with a transmitted beam, and information that one of the one or more destinations monitors a TTI of the sidelink transmission via a received beam associated with a transmitted beam (step 1094); having available sidelink data associated with a subset of the one or more destinations (step 1096); receiving a sidelink grant for scheduling one or more sidelink resources in one or more TTIs from a network node (step 1098); and selecting or determining a destination from the subset of one or more destinations, wherein the first UE selects or determines the destination based at least on the one or more messages received by the destination monitoring via a received beam associated with a transmitted beam in a TTI among the one or more TTIs (step 1100).

[0858] In various embodiments, a TTI among the one or more TTIs corresponds to an earliest TTI or any TTI among the one or more TTIs.

[0859] In various embodiments, if the first UE selects or determines that the second destination is not listening via a received beam associated with one of the transmitted beams in a TTI, the first UE does not select or is not allowed to select the second destination.

[0860] In various embodiments, the destination is further selected or determined based on the priority of the available sidelink data.

[0861] In various embodiments, the sidelink grant does not provide information associated with which beam is used for sidelink transmission on one or more sidelink resources, and / or the first UE determines the transmitted beam to be used for sidelink transmission on one or more sidelink resources based on a selected or determined destination, and / or when the selected or determined destination is associated with a first transmitted beam, the first UE performs sidelink transmission on one or more sidelink resources via the first transmitted beam.

[0862] In various embodiments, when the sidelink grant provides information associated with a specific beam for sidelink transmission on one or more sidelink resources, the destination is further selected or determined based on the paired transmitted beams being or corresponding to the specific beam, and / or when the sidelink grant provides information associated with a specific beam for sidelink transmission on one or more sidelink resources, the destination is selected or determined to be limited to the paired transmitted beams being or corresponding to the specific beam, and / or if the first UE determines that one transmitted beam associated with the sidelink transmission is for a third destination and one transmitted beam is not or does not correspond to the specific beam, the first UE does not select or is not allowed to select the third destination.

[0863] In various embodiments, if the first UE selects or determines that no destination is monitored via a received beam associated with a transmitted beam in a TTI, or if the first UE is unable to select a destination because no destination is selected or determined to be monitored via a received beam associated with a transmitted beam in a TTI, the first UE discards or ignores the sidelink grant, or does not perform a sidelink transmission on one or more sidelink resources scheduled by the sidelink grant.

[0864] In various embodiments, a first UE transmits information associated with a TTI set to a network node, wherein the information associated with the TTI set corresponds to a second UE (which is associated with one of the one or more destinations) monitoring or receiving an SCI in a side link resource pool via a second beam associated with the first UE.

[0865] In various embodiments, the first UE triggers transmission of information in response to any one or combination of the following: receiving an indication from the second UE that the second beam is applied or used or changed or updated relative to the previous beam, and / or the beam used for listening to or receiving SCI on the side link resource pool is changed (from the third beam to the second beam), or the TTI set is changed or updated or applied or used; and / or the first UE determines that the first beam used for side link transmission to the second UE is changed or updated or applied or used; and / or a third destination associated with the third UE is added as a destination of the first UE; and / or there is side link data to be transmitted associated with the second UE.

[0866] In various embodiments, the first UE transmits information on periodic resources or semi-persistently scheduled resources.

[0867] In various embodiments, the first UE transmits information together with a first BSR at one time instance, wherein the first BSR corresponds to a regular BSR, or the first UE transmits information and the first BSR at different time instances, or the first UE transmits a second BSR including the information, wherein the second BSR is different from the regular BSR.

[0868] In various embodiments, the first UE transmits a second BSR including an amount of data associated with one or more destinations, the first UE transmitting the second BSR including information associated with one or more TTI sets for the one or more destinations.

[0869] In various embodiments, after a first UE establishes a link with a second UE, or after an initial beam pair procedure, or after a beam failure recovery procedure: the first UE determines a first beam for sidelink transmission to the second UE, or the first UE receives a message from the second UE indicating a listening (time) mode associated with the second beam, or the first UE determines a TTI set based on the (received) message.

[0870] In various embodiments, the information associated with the TTI set further includes information of the first beam, and / or the first UE provides information about associating the TTI set with the first beam to the network node.

[0871] In various embodiments, after the first UE transmits information, the first UE expects to receive sidelink grant scheduling resources associated with at least one TTI monitored by the destination via the first beam, or the first UE expects to receive sidelink grant scheduling resources on at least one TTI associated with the first beam in the TTI set.

[0872] Return to reference Figure 3 and 4In one or more embodiments from the perspective of a first UE performing a sidelink transmission in a sidelink resource pool, the apparatus 300 includes program code 312 stored in a memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) perform one or more unicast sidelink transmissions with one or more destinations, wherein the first UE determines to apply a transmitted beam for the sidelink transmission to each of the one or more destinations; (ii) receive one or more messages from the one or more destinations, wherein each of the one or more messages indicates a listening mode associated with a transmitted beam, and information that one of the one or more destinations listens to the TTI of the sidelink transmission via a received beam associated with a transmitted beam; (iii) have available sidelink data associated with a subset of the one or more destinations; (iv) receive a sidelink grant scheduling one or more sidelink resources in one or more TTIs from a network node; and (v) select or determine a destination from the subset of the one or more destinations, wherein the first UE selects or determines the destination based at least on the received one or more messages that the destination listens to via a received beam associated with one of the transmitted beams in a TTI among the one or more TTIs. Furthermore, CPU 308 may execute program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0873] Any combination of the concepts or teachings above or here can be combined or formed into new embodiments in whole or in part. The disclosed details and embodiments can be used to solve at least (but not limited to) the problems mentioned above and here.

[0874] 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.

[0875] Various aspects of the present disclosure have been described above. It should be clear 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 of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, by using other structures, functionality, or structures and functionality other than one or more aspects of the aspects set forth herein or different from one or more aspects of the aspects set forth herein, this device can be implemented or this method can be practiced. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequency. In some aspects, parallel channels can be established based on pulse position or offset. 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 frequency, pulse position or offset, and time hopping sequences.

[0876] Those skilled in the art will understand 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.

[0877] Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the various 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 decoding 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, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the 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.

[0878] 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, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0879] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in an exemplary order, but are not meant to be limited to the specific order or hierarchy presented.

[0880] The steps of the method or algorithm described in conjunction with the various aspects disclosed herein can 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. An example storage medium may be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to as a "processor" in this article) so that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. An example storage medium may be integrated with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user device. In an alternative, the processor and the 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, and the computer-readable medium includes a code related to one or more aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0881] 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 for a first user equipment to perform sidelink transmission in a sidelink resource pool, characterized in that: include: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second user equipment; as well as Information indicating a set of transmission time intervals is transmitted to a network node, wherein the set of transmission time intervals corresponds to the second user equipment listening to or receiving sidelink control information in the sidelink resource pool via a second beam associated with the first user equipment.

2. The method according to claim 1, characterized in that The first user equipment has available sidelink data associated with the second user equipment and / or the first user equipment transmits a first buffer status report including further information of the sidelink data to the network node.

3. The method according to claim 2, characterized in that: the user equipment transmitting the information together with the first buffer status report at a time instance, wherein the first buffer status report corresponds to a regular buffer status report, or The user equipment transmits the information and the first buffer status report at different time instances, or the user equipment transmitting a second buffer status report comprising the information, wherein the second buffer status report is different from a regular buffer status report, or The user equipment transmits a third buffer status report comprising the information, wherein the third buffer status report corresponds to a regular buffer status report and / or a periodic buffer status report and / or a filling buffer status report.

4. The method according to claim 1, characterized in that: The first user equipment triggers the transmission of the information in response to one or more of the following: receiving from the second user equipment an indication that the second beam is applied or used or changed or updated relative to a previous beam, or that a beam used for monitoring or receiving side link control information on the side link resource pool is changed, or that the transmission time interval set is changed or updated or applied or used, and / or determining that a first beam for sidelink transmission to the second user equipment is changed or updated or applied or used, and / or a third destination associated with a third user equipment is added as a destination of the first user equipment, and / or There is to-be-transmitted sidelink data associated with the second user equipment to be transmitted.

5. The method according to claim 1, characterized in that The user equipment transmits the information on a periodic resource or a semi-persistently scheduled resource.

6. The method according to claim 1, characterized in that Further comprising transmitting a second buffer status report including an amount of data associated with the one or more destinations, wherein the first user equipment transmits the second buffer status report including information associated with one or more transmission time interval sets for the one or more destinations.

7. The method according to claim 1, characterized in that After establishing a link with the second user equipment, or after an initial beam pairing procedure, or after a beam failure recovery procedure: determining a first beam for sidelink transmission to the second user equipment, or receiving a message from the second user equipment indicating a listening mode associated with the second beam, or The set of transmission time intervals is determined based on the received message.

8. The method according to claim 1, characterized in that The information further includes information of the first beam, and / or the first user equipment provides information of the transmission time interval set associated with the first beam to the network node.

9. The method according to claim 1, characterized in that: After the first user equipment transmits the information, the first user equipment expects to receive sidelink grant scheduling resources associated with at least one transmission time interval monitored by the destination via the first beam, or the first user equipment expects to receive sidelink grant scheduling resources on at least one transmission time interval in the transmission time interval set associated with the first beam.

10. The method according to claim 1, characterized in that Further comprising receiving one or more messages from the one or more destinations, wherein each of the one or more messages indicates a listening mode associated with a transmitted beam, and information of a transmission time interval transmitted by one of the one or more destinations via a received beam listening side link associated with the one transmitted beam of the first user equipment.

11. The method according to claim 10, characterized in that: the first user equipment having available sidelink data associated with a subset of the one or more destinations, and / or The first user equipment receives a sidelink grant from the network node scheduling one or more sidelink resources in one or more transmission time intervals, and / or The first user equipment selects or determines a destination from the subset of the one or more destinations, wherein the selecting or the determining is based on one or more received messages.

12. The method according to claim 11, characterized in that The transmission time interval among the one or more transmission time intervals corresponds to an earliest transmission time interval or any transmission time interval among the one or more transmission time intervals.

13. A method for a first user equipment to perform sidelink transmission in a sidelink resource pool, characterized in that: include: performing one or more unicast sidelink transmissions with one or more destinations, wherein the first user equipment determines to apply one transmitted beam for sidelink transmissions to each of the one or more destinations; receiving one or more messages from the one or more destinations, wherein each of the one or more messages indicates a listening mode associated with the one transmitted beam and information of a transmit time interval at which one of the one or more destinations transmits via a received beam listening sidelink associated with the one transmitted beam; having available sidelink data associated with a subset of the one or more destinations; receiving a sidelink grant from a network node scheduling one or more sidelink resources in one or more transmit time intervals; as well as A destination is selected or determined from the subset of the one or more destinations, wherein the first user device selects or determines the destination based at least on one or more messages received by the destination via received beam monitoring associated with the one transmitted beam in a transmission time interval among the one or more transmission time intervals.

14. The method according to claim 13, characterized in that The transmission time interval among the one or more transmission time intervals corresponds to an earliest transmission time interval or any transmission time interval among the one or more transmission time intervals.

15. The method according to claim 13, characterized in that If the first user equipment selects or determines that a second destination is not listening via the received beam associated with the one transmitted beam in the transmit time interval, the first user equipment does not select or is not allowed to select the second destination.

16. The method according to claim 13, characterized in that The destination is further selected or determined based on a priority of the available sidelink data.

17. The method according to claim 13, characterized in that: The sidelink grant does not provide information associated with which beam to use for sidelink transmission on the one or more sidelink resources, and / or The first user equipment determines a transmitted beam for sidelink transmission on the one or more sidelink resources based on the selected or determined destination, and / or When the selected or determined destination is associated with a first transmitted beam, the first user equipment performs sidelink transmission on the one or more sidelink resources via the first transmitted beam.

18. The method according to claim 13, characterized in that: When the sidelink grant provides information associated with a particular beam for sidelink transmission on the one or more sidelink resources, the destination is further selected or determined based on the paired transmitted beam being or corresponding to the particular beam, and / or When the sidelink grant provides information associated with the particular beam for sidelink transmission on the one or more sidelink resources, the destination is selected or determined to be limited to the paired transmitted beams that are or correspond to the particular beam, and / or If the first user equipment determines that the one transmitted beam associated with the sidelink transmission is for a third destination and the one transmitted beam is not or does not correspond to the specific beam, the first user equipment does not select or is not allowed to select the third destination.

19. The method according to claim 13, characterized in that If the first user device selects or determines that there is no destination to monitor via the received beam associated with the one transmitted beam in the transmission time interval, or if the first user device is unable to select a destination because no destination is selected or determined to be monitored via the received beam associated with the one transmitted beam in the transmission time interval, the first user device discards or ignores the sidelink grant, or does not perform a sidelink transmission on the one or more sidelink resources scheduled by the sidelink grant.

20. A first user equipment performing sidelink transmission in a sidelink resource pool, characterized in that: include: Memory; as well as a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: performing one or more unicast sidelink transmissions with one or more destinations including a second destination associated with a second user equipment; and Information indicating a set of transmission time intervals is transmitted to a network node, wherein the set of transmission time intervals corresponds to the second user equipment listening to or receiving sidelink control information in the sidelink resource pool via a second beam associated with the first user equipment.

Images