Method and apparatus for processing discontinuous reception and partial sensing in a wireless communication system

Abstract

The present invention discloses a method and apparatus for processing discontinuous reception and partial sensing in a wireless communication system, and a method and apparatus for sidelink communication to reduce potential latency caused by additional sensing and improve resource utilization efficiency. A first device can perform sidelink communication to at least a second device or to the second device in a sidelink resource pool, and trigger resource selection for sidelink data at a timing. The first device can perform sensing within a first continuous sensing duration before the sidelink on duration activity time of the second device, determine or select a first sidelink resource from a sidelink resource set, derive or determine the sidelink resource set based on at least the sensing results during the first continuous sensing duration, and perform a first sidelink transmission on the first sidelink resource for transmitting sidelink data to the second device.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication networks, and more particularly, to methods and apparatus for handling discontinuous reception and partial sensing for sidelink communications. Background Art

[0002] With the rapidly growing demand for transferring large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that use Internet Protocol (IP) packet communications. This IP packet communication can provide IP-based voice, multimedia, multicast, and on-demand communication services to users of mobile communication devices.

[0003] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Consequently, 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

[0004] Methods and apparatus are provided for handling discontinuous reception and partial sensing for sidelink communications to reduce potential latency due to additional sensing and improve resource utilization efficiency.

[0005] In one embodiment, a method for a first device to perform sidelink communication with at least a second device in a sidelink resource pool includes the following steps: the first device triggers resource selection for sidelink data at a timing sequence; the first device performs sensing for a first continuous sensing duration before a sidelink on duration active time of a second device; the first device determines / selects a first sidelink resource from a set of sidelink resources, wherein the sidelink resource set is derived or determined based on at least a sensing result during the first continuous sensing duration; and the first device performs a first sidelink transmission on the first sidelink resource for transmitting sidelink data to the second device. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0010] Figure 5 It is R1-2007615 Figure 4 , which shows that the non-periodic reservation (indicated in the SCI) cannot be listened to.

[0011] Figure 6 It is R1-2007615 Figure 5 Reproduction of , which shows the extended partial sensing window for aperiodic traffic.

[0012] Figure 7 It is R1-2007688 Figure 4 A reproduction of , which shows an additional sensing window: the short-term partial sensing window.

[0013] Figure 8 It is R1-2008189 Figure 1 A reproduction showing partial sensing for intra-cycle and inter-cycle reservations.

[0014] Figure 9 It is R1-2009072 Figure 1 and 2 The reproduction of Figure 9 Part A of R1-2009072 Figure 1 , used to show partial sensing following LTE behavior, and Figure 9 Part B of R1-2009072 Figure 2 , used to illustrate partial sensing for NR (considering the aperiodic nature of the traffic).

[0015] Figure 10 It is R1-2009272 Figure 2 A reproduction showing the execution of a random selection and subsequent re-evaluation.

[0016] Figure 11 It is R1-2009272 Figure 3 A reproduction of FIG1 , which shows that sensing is performed after the resource selection trigger.

[0017] Figure 12 A UE having a candidate resource set including a plurality of candidate resources according to an embodiment of the present invention is shown.

[0018] Figure 13A possible manner for a UE to obtain sensing results in a sidelink inactive time by performing partial sensing in a sidelink active time according to an embodiment of the present invention is shown.

[0019] Figures 14A to 14B It is shown that the UE according to an embodiment of the present invention triggers resource sensing (and selection) for sidelink data, for example in time slot n, and (starts) performing additional sensing within an additional sensing duration, for example a time interval.

[0020] Figure 15A It shows a case where the first UE may trigger resource sensing and selection in time slot 220 according to an embodiment of the present invention.

[0021] Figure 15B It shows a case where the first UE according to an embodiment of the present invention may trigger resource sensing and selection in time slot 210, while the first UE does not perform additional sensing in time slots [210, 219].

[0022] Figure 15C It shows a case where the first UE may start to perform additional sensing when the first UE triggers to perform resource sensing and selection according to an embodiment of the present invention.

[0023] Figure 15D The case where the continuous time slot set according to the embodiment of the present invention is a specific value of continuous time slots is shown.

[0024] Figure 16 is a flowchart of a method in which a first device performs sidelink communication to at least a second device according to an embodiment of the present invention.

[0025] Figure 17 is a flowchart of a method in which a first device performs sidelink communication to at least a second device in a sidelink resource pool according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] The present invention described herein may be applied to or implemented in the exemplary wireless communication systems and devices described below. Furthermore, the present invention is primarily described in the context of the 3GPP architecture reference model. However, it should be understood that, with the aid of the disclosed information, one skilled in the art can readily adapt and implement aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

[0027] 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) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0028] Specifically, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as those provided by an association named "3rd Generation Partnership Project" (referred to herein as 3GPP), including: [1] 3GPP TS 36.213 V16.4.0 (2020-12), "3GPP TSG RAN; E-UTRA physical layer procedures (Release 16)"; [2] 3GPP TS 38.214 V16.4.0 (2020-12), "3GPP TSG RAN; NR physical layer procedures for data (Release 16)"; [3] 3GPP TS 38.213 V16.4.0 (2020-12), "3GPP TSG RAN; NR physical layer procedures for control (Release 16)"; [4] 3GPP TS 38.212 V16.4.0 (2020-12), "3GPP TSG RAN; NR multiplexing and channel coding (Release 16)”; [5] 3GPP TS 38.321 V16.3.0 (2020-12), “3GPP TSG RAN; NR Media Access Control (MAC) Protocol Specification (Release 16)”; [6] RP-202846, “WID Revision: NR Sidelink Enhancements”; [7] Draft Report of 3GPP TSG RAN WG1#103-ev0.2.0 (Online Meeting, October 26 to November 13, 2020); [8] R2-2100001, “3GPP TSG [9] R1-2007615, “Sidelink resource allocation for reducing power consumption”, Huawei HiSilicon;

[10] R1-2007688, “Resource allocation for sidelink energy saving”, vivo;

[11] R1-2008189, “On resource allocation for power saving”, Samsung;

[12] R1-2009072, “Resource allocation mechanism for energy saving”, Ericsson; and

[13] R1-2009272, “Power saving for sidelink”, Qualcomm. The standards and documents listed above are hereby expressly and fully incorporated into this document in their entirety.

[0029] Figure 1 1 shows a multiple access wireless communication system according to an embodiment of the present invention. An access network 100 (AN) includes multiple antenna groups, one group includes 104 and 106, another group includes 108 and 110, and an additional group includes 112 and 114. Figure 1In the figure, only two antennas are shown for each antenna group; however, each antenna group may utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 may utilize different frequencies for communication. For example, forward link 120 may utilize a different frequency than that used by reverse link 118.

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

[0031] In communications via forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Additionally, an access network that uses beamforming to transmit to access terminals randomly dispersed throughout its coverage area may cause less interference to access terminals in neighboring cells than an access network that transmits to all of its access terminals through a single antenna.

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

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

[0034] In one embodiment, each data stream is transmitted through 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.

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

[0036] 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). TX MIMO processor 220 then provides NT modulation symbol streams to NT 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.

[0037] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. NT modulated signals from transmitters 222a through 222t are then transmitted from NT antennas 224a through 224t, respectively.

[0038] At receiver system 250, the transmitted modulated signals are received by NR antennas 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.

[0039] An RX data processor 260 then receives and processes the NR received symbol streams from NR receivers 254 based on a particular receiver processing technique to provide NT "detected" symbol streams. 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 RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210.

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

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

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

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

[0044] Return to 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 the communication device 300, 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 signals input by the user through the input device 302 (for example, a keyboard or 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, pass the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306.

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

[0046] For LTE, LTE-A, or NR systems, Layer 2 portion 404 may include the Radio Link Control (RLC) layer and the Medium Access Control (MAC) layer. Layer 3 portion 402 may include the Radio Resource Control (RRC) layer.

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

[0048] Any sentence, paragraph, (sub) bullet, point, action or claim described in each of the following inventions can be independently and individually implemented to form a specific method. Dependencies in the following inventions, such as "based on", "more specifically", etc., are only one possible embodiment that will not limit a specific method.

[0049] TS 36.213 [1] specifies physical sidelink shared channel related procedures in LTE. In order to acquire sidelink resources, it specifies (periodic based) partial sensing for sidelink transmission mode 4.

[0050] ******************Quote [1]Start************************

[0051] 14.1.1.6 UE procedure for determining the subset of resources to be reported to higher layers in PSSCH resource selection in sidelink transmission mode 4 and in sensing measurements in sidelink transmission mode 3

[0052] In sidelink transmission mode 4, when requested by higher layers for a carrier in subframe n, the UE shall determine the resource set to be reported to higher layers for PSSCH transmission according to the steps described in this clause. Parameter L subCH (the number of subchannels to be used for PSSCH transmission in a subframe), P rsvp_TX (resource reservation interval) and prio TX (The priority to be transmitted by the UE in the associated SCI format 1) is provided by higher layers (described in [8]). reselis determined in accordance with Section 14.1.1.4B.

[0053] In sidelink transmission mode 3, when requested by higher layers for a carrier in subframe n, the UE shall determine the set of resources to be reported to higher layers in sensing measurements according to the steps described in this clause. Parameter L subCH 、P rsvp_TX and prio TX are provided by higher layers (described in

[11] ). C resel By C resel =10*SL_RESOURCE_RESELECTION_COUNTER, where SL_RESOURCE_RESELECTION_COUNTER is provided by higher layers

[11] .

[0054] […]

[0055] If partially sensed by a higher layer configuration, the following steps are used:

[0056] 1) Candidate single subframe resource R to be used for PSSCH transmission x,y Defined as L subCH A set of consecutive subchannels, where subchannel x+j is in the subframe where j = 0, ..., L subCH -1. The UE shall determine a subframe set consisting of at least Y subframes within the time interval [n+T1, n+T2] according to its implementation, where the selection of T1 and T2 depends on T1≤4 and T 2min (prio TX )≤T2≤100, provided that T 2min (prio TX ) by higher layers for prio TX Provided, otherwise 20≤T2≤100. The UE selection of T2 shall meet the latency requirement and Y shall be greater than or equal to the higher layer parameter minNumCandidateSF. The UE shall assume that the L contained in the corresponding PSSCH resource pool (described in 14.1.5) within the determined set of subframes subCH Any set of consecutive subchannels corresponds to a candidate single subframe resource. The total number of candidate single subframe resources is M total express.

[0057] 2) If the subframe If the subframe set is included in step 1, the UE will monitor any subframe if the kth bit of the higher layer parameter gapCandidateSensing is set to 1. The UE will perform the actions described in the following steps based on the decoded PSCCH and measured S-RSSI in these subframes.

[0058] 3) Parameter Th a,b Set to the value indicated by the i-th SL-ThresPSSCH-RSRP field in the SL-ThresPSSCH-RSRP-List, where i=(a-1)*8+b.

[0059] 4) Set S A Initialize to the union of all candidate single subframe resources. B Initialized to an empty set.

[0060] 5) If all of the following conditions are met, the UE shall select A Exclude any candidate single subframe resource R x,y :

[0061] -UE in subframe The SCI format 1 is received in the received SCI format, and according to Section 14.2.1, the "Resource Reservation" field and the "Priority" field in the received SCI format 1 indicate the value P respectively. rsvp_RX and prio RX .

[0062] -PSSCH-RSRP measurement based on received SCI format 1 is higher than

[0063] - In subframe The received SCI format, or assuming that the subframe The same SCI format 1 received in the 14.1.1.4C determines the set of resource blocks and the number of resource blocks for q = 1, 2, ..., Q and j = 0, 1, ..., C resel -1 and Overlapping subframes. Here, if P rsvp_RX <1 and y'-m≤P step ×P rsvp_RX +P step ,but in It is the last subframe of Y subframes, and in other cases, Q=1.

[0064] 6) If the set S A The number of remaining candidate single subframe resources is less than 0.2·M total , then repeat step 4, where Th a,b Increase by 3dB.

[0065] 7) For set S A The remaining candidate single subframe resources R x,y, metric E x,y is defined as the linear average of the S-RSSIs measured in subchannel x+k in the monitored subframes in step 2, where k=0,...,L subCH -1, which can be expressed as Where j is a non-negative integer.

[0066] 8) The UE will have A The minimum measure E x,y Candidate single subframe resource R x,y Move to set S B Repeat this step until the set S B The number of candidate single-subframe resources in becomes greater than or equal to 0.2·M total until.

[0067] 9) When the UE is configured by upper layers to transmit using a resource pool on multiple carriers, if the UE does not support candidate single-subframe resource R in a carrier under the assumption that the selected resource is used for transmission in other carriers due to a limit on the number of simultaneously transmitting carriers, a limit on the supported carrier combinations, or an interruption in RF retuning time x,y The UE will receive the transmission from S B The candidate single subframe resources are excluded

[10] .

[0068] The UE shall report the set S to higher layers B .

[0069] ******************End of quote [1]************************

[0070] TS 38.214[2] specifies the physical sidelink shared channel (PSCH) related procedures in NR. In order to obtain sidelink resources, it specifies sidelink resource allocation mode 1 and sidelink resource allocation mode 2.

[0071] ******************Quote [2]Start************************

[0072] 8 Physical side link shared channel related procedures

[0073] A UE may be configured by higher layers to have one or more sidelink resource pools. A sidelink resource pool may be used to transmit PSSCH, as described in Section 8.1, or to receive PSSCH, as described in Section 8.3, and may be associated with sidelink resource allocation mode 1 or sidelink resource allocation mode 2.

[0074] In the frequency domain, the sidelink resource pool consists of sl-NumSubchannel consecutive subchannels. A subchannel consists of sl-SubchannelSize consecutive PRBs, where sl-NumSubchannel and sl-SubchannelSize are higher-layer parameters.

[0075] The set of time slots that may belong to the sidelink resource pool is represented by: in

[0076] -

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

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

[0079] -N S_SSB timeslot, in which an S-SS / PSBCH block (S-SSB) is configured,

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

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

[0082] 1) Exclude N from all time slot sets S_SSB Time slot and N nonSL The remaining time slots are arranged in increasing order of time slot index express.

[0083] 2) If Time slot Belongs to the reserved time slot, where m = 0, 1, ..., N reserved -1 and Among them L bitmap Indicates the length of the bitmap configured by higher layers.

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

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

[0086] - The length L of the bitmap bitmap When configured by higher layers, using the bitmap associated with the resource pool

[0087] - If b k′ =1, then the time slot belongs to the set, where k′=k mod L bitmap .

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

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

[0090] -The resource block pool is composed of N PRB It consists of PRBs.

[0091] - For m = 0, 1, ..., numSubchannel-1, subchannel m is composed of n subCHsize The set of consecutive resource blocks, where for j = 0, 1, ..., n subCHsize -1, the number of physical resource blocks n PRB =n subCHRBstart +m·n subCHsize +j, where n subCHRBstart and n subCHsize The UE is not expected to use the last N in the resource pool as indicated by the higher layer parameters sl-StartRB-Subchannel and sl-SubchannelSize respectively. PRB mod n subCHsize PRBs.

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

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

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

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

[0096] -A transport block is transmitted in at most two layers;

[0097] - Determine the number of layers (υ) according to the "Number of DMRS Ports" field in the SCI;

[0098] - The set of consecutive symbols within a slot used to transmit the PSSCH is determined according to Section 8.1.2.1;

[0099] - The set of consecutive resource blocks used to transmit the PSSCH is determined according to Section 8.1.2.2;

[0100] Transform precoding is not supported for PSSCH transmission.

[0101] PSSCH transmission only supports wideband precoding.

[0102] The DM-RS antenna ports in Section 8.4.1.1.1 of [4, TS 38.211] are determined according to the ordering of the DM-RS ports given by Table 8.3.1.1-1 in Section 8.3.1.1 of [5, TS 38.212]

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

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

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

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

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

[0108] - The UE shall set the value of the "HARQ Feedback Enable / Disable Indicator" field as instructed by higher layers.

[0109] - The UE shall set the value of the "Broadcast Type Indicator" field as instructed by higher layers.

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

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

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

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

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

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

[0116] - The UE shall set the value of the "HARQ Feedback Enable / Disable Indicator" field as instructed by higher layers.

[0117] - The UE shall set the value of the "Zone ID" field as instructed by higher layers.

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

[0119] 8.1.1 Transmission Scheme

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

[0121] PSSCH transmission is performed through a maximum of two antenna ports, where antenna ports 1000-1001 are defined in Section 8.2.4 of [4, TS38.211].

[0122] 8.1.2 Resource Allocation

[0123] In sidelink resource allocation mode 1:

[0124] - 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 through SL grants according to section 10.3 of [6, TS 38.213] in the valid activation DCI.

[0125] 8.1.2.1 Resource Allocation in the Time Domain

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

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

[0128] The UE shall transmit the PSSCH in consecutive symbols within a slot, subject to the following constraints:

[0129] - The UE shall not transmit PSSCH in symbols not configured for the sidelink.Symbols for the sidelink are configured according to higher layer parameters startSLsymbols and lengthSLsymbols, where startSLsymbols is the symbol index of the first symbol of lengthSLsymbols consecutive symbols configured for the sidelink.

[0130] - Within a time slot, PSSCH resource allocation starts at symbol startSLsymbols+1.

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

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

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

[0134] …

[0135] 8.1.2.2 Resource Allocation in the Frequency Domain

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

[0137] The sub-channel assignment for sidelink transmissions is determined using the "Frequency Resource Assignment" field in the associated SCI.

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

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

[0140] […]

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

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

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

[0144] -L1 priority, prio TX ;

[0145] - Remaining packet delay budget;

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

[0147] - Optionally, a resource reservation interval P rsvp_TX , in milliseconds.

[0148] - If, as part of a reassessment or pre-camping procedure, higher layers request the UE to determine a subset of resources from which the higher layers shall select resources for PSSCH / PSCCH transmission, the higher layers provide a set of resources that are subject to reassessment (r0, r1, r2, ...) and a set of resources that are subject to pre-camping (r′0, r′1, r′2, ...).

[0149] - implemented by the UE in time slot r″ i - Before or after T3 determines the resource subset as requested by the higher layer, where r″ i is the time slot with the smallest slot index among (r0, r1, r2, ...) and (r′0, r′1, r′2, ...), and T3 is equal to in The time slots defined in Table 8.1.4-2, where μ SL It is the SCS configuration of SL BWP.

[0150] The following higher-level parameters influence this procedure:

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

[0152] -sl-ThresPSSCH-RSRP-List: This higher layer parameter provides the i , p j ) RSRP threshold, where p i is the value of the priority field in the received SCI format 1-A, and p j The priority for selecting resources for the UE to transmit; for a given invocation of this procedure, p j =prio TX .

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

[0154] -sl-ResourceReservePeriodList

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

[0156] -sl-TxPercentageList: for a given prio TX The internal parameter X is defined as sl-TxPercentageList(prio TX )

[0157] -sl-PreemptionEnable: If sl-PreemptionEnable is provided, and if it is not equal to "enabled", the internal parameter prio pre Set the parameter sl-PreemptionEnable provided by the higher layer

[0158] According to Section 8.1.7, the resource reservation interval P rsvp_TX (If provided) Convert from milliseconds to logical slots, yielding P' rsvp_TX .

[0159] annotation:

[0160] Represents the set of time slots that can belong to the sidelink resource pool and is defined in Section 8.

[0161] Represents the set of time slots belonging to the sidelink resource pool and is defined in Section 8.

[0162] Use the following steps:

[0163] 1) Candidate single-slot resource R for 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 the L in the corresponding resource pool contained in the time interval [n+T1, n+T2] subCH Any set of consecutive subchannels corresponds to a candidate single-slot resource, where

[0164] -T1 selection depends on UE implementation, in The time slots defined in Table 8.1.4-2, where μ SL SCS configuration for SL BWP;

[0165] -If T 2min is shorter than the remaining packet delay budget (in the time slot), then T2 depends on T 2min ≤ T2 ≤ the remaining packet delay budget (in the time slot); otherwise T2 is set to the remaining packet delay budget (in the time slot).

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

[0167] 2) Sensing window is composed of time slots where T0 is defined above and The time slots defined in Table 8.1.4-1, where μ SL The SCS configuration for the SL BWP. The UE shall monitor the time slots belonging to the sidelink resource pool within the sensing window, except for the time slots in which its own transmission occurs. The UE shall perform the actions in the following steps based on the decoded PSCCH and measured RSRP in these time slots.

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

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

[0170] 5) UE should select from the set S A Eliminate any candidate single-slot resource R x，y , provided that it satisfies all of the following conditions:

[0171] - The UE has not yet monitored the time slot in step 2

[0172] - For any periodicity value allowed by the higher layer parameter sl-ResourceReservePeriodList and in time slots The hypothetical SCI format 1-A received in , where the "resource reservation period" field is set to the periodic value and indicates all sub-channels of the resource pool in this time slot, will satisfy condition c in step 6.

[0173] 6) UE should select from the set S A Eliminate any candidate single-slot resource R x，y , provided that it satisfies all of the following conditions:

[0174] a)UE in time slot The SCI format 1-A is received in the received SCI format 1-A, and according to Section 16.4 of [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 ;

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

[0176] 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 UE determines the resource block set according to Section 8.1.5, and for q = 1, 2, ..., Q and j = 0, 1, ..., C resel -1 and Overlapping time slots. Here, P′ rsvp_RX To convert to P in logical time slots according to clause 8.1.7 rsvp_RX , if P rsvp_RX <T scal And n′-m≤P′ rsvp_RX ,but where if time slot n belongs to the set but Otherwise time slot Belong to the set The first time slot after time slot n; otherwise Q = 1. T scal Set to convert the selection window size T2 into milliseconds.

[0177] 7) If the set S A The number of candidate single-slot resources remaining in is less than X·M total , then for each priority value Th(p i , p j ), so that Th(p i , p j ) is increased by 3dB, and the procedure continues with step 4.

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

[0179] If a resource r from the set (r0, r1, r2, ...) i Not a set S A If the UE is a member of i .

[0180] If due to the received SCI format 1-A having an associated priority prio RX The RSRP measurement of the resource r′ from the set (r′0, r′1, r′2, …) is excluded in step 6 above. i Not S A If the UE is a member of r and one of the following conditions is met, the UE shall report the resource r′ to the higher layer. i pre-occupancy.

[0181] -sl-PreemptionEnable is provided and equal to "enabled", and prio TX >prio RX

[0182] -sl-PreemptionEnable is provided and is not equal to "enabled", and prio RX <prio pre And prio TX >prio RX

[0183] Table 8.1.4-1: Dependence on subcarrier spacing

[0184]

[0185] Table 8.1.4-2: Dependence on subcarrier spacing

[0186]

[0187]

[0188] 8.1.5 UE Procedure for Determining Timeslots and Resource Blocks for PSSCH Transmissions Associated with SCI Format 1-A

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

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

[0191] If N=1

[0192] TRIV=0

[0193] else if N=2

[0194] TRIV=t1

[0195] else

[0196] if(t2-t1-1)≤15

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

[0198] else

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

[0200] end if

[0201] end if

[0202] Wherein the first resource is in a time slot in which SCI format 1-A is received, and t i represents the time offset of the i-th resource 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。

[0203] Determine the initiator channel of the first resource according to Section 8.1.2.2 The number of subchannels L allocated consecutively 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 the resources in the time slot in which the SCI format 1-A is received) is determined according to the "frequency resource assignment" equal to the frequency RIV (FRIV), where.

[0204] If sl-MaxNumPerReserve is 2, then

[0205]

[0206] If sl-MaxNumPerReserve is 3, then

[0207]

[0208] where

[0209] - represents the promoter channel index of the second resource

[0210] - represents the promoter channel index of the third resource

[0211] - is the number of sub-channels in the resource pool provided according to the higher layer parameter sl-NumSubchannel

[0212] If TRIV indicates that N < sl-MaxNumPerReserve, the promoter channel index corresponding to the last sl-MaxNumPerReserve minus N resources is not used

[0213] The number of time slots in a time and frequency resource set for the transmission opportunity of PSSCH is given by C resel where if configured, C resel = 10 * SL_RESOURCE_RESELECTION_COUNTER[10, TS 38.321], otherwise C resel is set to 1

[0214] If the sub-channel set in the time slot is determined to be the time and frequency resources for PSSCH transmission corresponding to the selected sidelink grant (described in [10, TS38.321]), the same sub-channel set in the time slot is also determined to be used for PSSCH transmission corresponding to the same sidelink grant, where j = 1, 2,..., C resel -1, according to Section 8.1.7, P rsvp_TX (if provided) is converted from milliseconds to logical time slots, resulting in P' rsvp_TX , and is determined by Section 8. Here, P rsvp_TX is the resource reservation interval indicated by the higher layer

[0215] […]

[0216] 8.3 UE Procedures for Receiving the Physical Sidelink Shared Channel

[0217] For sidelink resource allocation mode 1, after detecting SCI format 1-A on the PSCCH, the UE can decode the PSSCH according to the detected SCI formats 2-A and 2-B 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.

[0218] For sidelink resource allocation mode 2, after detecting SCI format 1-A on the PSCCH, the UE can decode the PSSCH according to the detected SCI formats 2-A and 2-B 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.

[0219] 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 and 2-B nor the PSSCH associated with SCI format 1-A.

[0220] […]

[0221] 8.6 UE PSSCH preparation procedure time

[0222] For sidelink dynamic grant and for SL configured grant type 2 activation, if the slot offset K as determined by the scheduling DCI for dynamic grant or the activation DCI for SL configured grant type 2 SL The first sidelink symbol (including DM-RS and repeated symbols) in the sidelink allocation of the PSSCH and associated PSCCH for a defined transport block is no earlier than symbol L, where L is defined as the next sidelink symbol whose CP starts after the end of reception of the last symbol of the PDCCH carrying the DCI scheduling the sidelink transmission of a dynamic grant or activating the SL configured grant type 2. proc =(N2+d 2，1 )(2048+144)·κ2 -μ ·T C , the UE shall transmit PSSCH and associated PSCCH.

[0223] - N2 is μ based on Table 8.6-1, where μ corresponds to one of (μDL, μSL) that results in the maximum Tproc, where μDL corresponds to the subcarrier spacing of the downlink, over which the PDCCH carrying the scheduling dynamic grant or the activation SL configured grant type 2 DCI is transmitted, and μSL corresponds to the subcarrier spacing of the sidelink channel, over which the PSSCH and the associated PSCCH are transmitted, and κ is defined in Section 4.1 of [4, TS 38.211].

[0224] -d2,1=1.

[0225] Otherwise, the UE may ignore the scheduling DCI for dynamic grant or the activation DCI for SL configured grant type 2.

[0226] In both normal and extended cyclic prefix cases, T is used. proc The value of .

[0227] Table 8.6-1: PSSCH preparation time

[0228] μ PSSCH preparation time N2 [symbol] 0 10 1 12 2 23 3 36

[0229] For sidelink resource allocation mode 1, the UE does not expect the first sidelink symbol in the sidelink allocation of the PSSCH and associated PSCCH for a retransmitted transport block (containing DM-RS and repeated symbols as defined by the "Time Resource Assignment" field of the corresponding DCI for dynamic grant or SL configured grant type 2 or sl-TimeResourceCG-Type1 for configured grant type 1) to be earlier than symbol L, where L is defined as the next sidelink symbol whose CP starts T after the end of the last symbol of the PSFCH opportunity of the most recent PSSCH transmission corresponding to the same transport block. prep +δ, where T is defined in Section 16.5 of [6, TS38.213] prep And δ=5·10 -4 Otherwise, the UE may skip the retransmission of the PSSCH and the corresponding transmission of the PSCCH.

[0230] ******************End of quote [2]****************************

[0231] In TS 38.213 [3], it specifies the sidelink control and feedback channel related procedures in NR.

[0232] ******************Quote [3]Start ******************************

[0233] 16 UE procedures for sidelink

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

[0235] The UE is expected to use the same base parameters in the SL BWP and the active UL BWP in the same carrier of the same cell. If the active UL BWP base parameters are different from the SL BWP base parameters, the SL BWP is deactivated.

[0236] […]

[0237] 16.4 UE Procedure for Transmitting PSCCH

[0238] For PSCCH transmission with SCI format 1-A, several symbols from a resource pool started 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 started from the lowest PRB of the lowest subchannel of the associated PSSCH may be provided to the UE via sl-FreqResourcePSCCH.

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

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

[0241] - Set the value of the frequency resource assignment field and the time resource assignment field as described in [6, TS 38.214] to indicate the resource set selected by the higher layer as described in [11, TS 38.321] {R y}, which has N minimum time slot index y i , where 0≤i≤N-1, such that y0 <y1<…<y N-1 ≤y0+31, where:

[0242] -N=min(N selected , N max_reserve ), where N selected For a time slot index y j The set {R y}, 0≤j≤N selected -1, making And N max_reserve Provided by sl-MaxNumPerReserve

[0243] -From the resource set {R y Each resource of} corresponds to L subCH A set of consecutive subchannels and time slots The time slots in which L subCH is the number of subchannels available for PSSCH / PSCCH transmission in a time slot

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

[0245] -y0 is the index of the slot in which the PSCCH having SCI format 1-A is transmitted.

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

[0247] - Set the values of the Frequency Resource Assignment field and the Time Resource Assignment field for SCI format 1-A transmitted in the mth resource of a PSCCH / PSSCH transmission provided by a dynamic grant or by an SL configured grant as follows, 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 SL configured grant type 2:

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

[0249] For decoding of SCI format 1-A, the UE may assume that the number of bits provided by sl-NumReservedBits may have any value.

[0250] ******************End of quote [3]************************

[0251] In TS 38.212[4], it specifies the sidelink control information in NR

[0252] ******************Quote [4]Start***************************

[0253] 8.3 Sidelink Control Information on PSCCH

[0254] The SCI carried on the PSCCH is level 1 SCI, which transmits sidelink scheduling information.

[0255] 8.3.1 Level 1 SCI Format

[0256] The fields defined in each of the following Level 1 SCI formats are mapped to information bits a0 to a A-1 ,as follows:

[0257] Each field is mapped in the order it appears in the description, with the first field mapped to the lowest order information bit, a0, and each successive field mapped to a higher order information bit. The most significant bit of each field is mapped to the lowest order information bit of that field, e.g., the most significant bit of the first field is mapped to a0.

[0258] 8.3.1.1 SCI Format 1-A

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

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

[0261] - Priority - 3 bits as specified in section 5.4.3.3 of [12, TS 23.287] and section 5.22.1.3.1 of [8, TS 38.321].

[0262] -Frequency Resource Assignment- bit, then the value of the higher layer parameter sl-MaxNumPerReserve is configured to 2; otherwise bit, in which case the value of the higher layer parameter sl-MaxNumPerReserve is configured to 3, as defined in section 8.1.5 of [6, TS 38.214].

[0263] - 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 section 8.1.5 of [6, TS 38.214].

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

[0265] -DMRS Mode- bits, as defined in section 8.4.1.1.2 of [4, TS 38.211], where N pattern The number of DMRS patterns configured by the higher-layer parameter sl-PSSCH-DMRS-TimePatternList.

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

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

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

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

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

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

[0272] - Reserved - the number of bits as determined by the higher layer parameter sl-NumReservedBits, where the value is set to zero.

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

[0274]

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

[0276]

[0277] Table 8.3.1.1-3: Number of DMRS ports

[0278] The value of the DMRS Port Number field Antenna port 0 1000 1 1000 and 1001

[0279] 8.3.2 CRC Append

[0280] CRC appending is performed according to section 7.3.2, except that scrambling is not performed.

[0281] 8.3.3 Channel Decoding

[0282] Channel decoding is performed according to clause 7.3.3.

[0283] 8.3.4 Rate Matching

[0284] Rate matching is performed according to Section 7.3.4.

[0285] 8.4 Sidelink Control Information on PSSCH

[0286] The SCI carried on the PSSCH is level 2 SCI, which transmits sidelink scheduling information.

[0287] 8.4.1 Level 2 SCI Format

[0288] The fields defined in each of the following Level 2 SCI formats are mapped to information bits a0 to a A-1 ,as follows:

[0289] Each field is mapped in the order it appears in the description, with the first field mapped to the lowest order information bit, a0, and each successive field mapped to a higher order information bit. The most significant bit of each field is mapped to the lowest order information bit of that field, e.g., the most significant bit of the first field is mapped to a0.

[0290] 8.4.1.1 SCI Format 2-A

[0291] 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 HARQ-ACK information.

[0292] The following information is transmitted using SCI Format 2-A:

[0293] - HARQ process number - 4 bits, as defined in section 16.4 of [5, TS 38.213].

[0294] - New Data Indicator - 1 bit, as defined in section 16.4 of [5, TS 38.213].

[0295] - Redundancy version - 2 bits, as defined in section 16.4 of [6, TS 38.214].

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

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

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

[0299] - Broadcast Type Indicator - 2 bits, as defined in Table 8.4.1.1-1.

[0300] - CSI request - 1 bit, as defined in section 8.2.1 of [6, TS 38.214].

[0301] Table 8.4.1.1-1: Broadcast type indicator

[0302]

[0303] 8.4.1.2 SCI Format 2-B

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

[0305] The following information is transmitted using SCI Format 2-B:

[0306] - HARQ process number - 4 bits, as defined in section 16.4 of [5, TS 38.213].

[0307] - New Data Indicator - 1 bit, as defined in section 16.4 of [5, TS 38.213].

[0308] - Redundancy version - 2 bits, as defined in section 16.4 of [6, TS 38.214].

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

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

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

[0312] - Region ID - 12 bits, as defined in section 5.8.11 of [9, TS 38.331].

[0313] - Communication range requirement - 4 bits, determined by the higher layer parameter sl-ZoneConfigMCR-Index.

[0314] 8.4.2 CRC appending

[0315] CRC appending is performed according to section 7.3.2, except that scrambling is not performed.

[0316] 8.4.3 Channel Decoding

[0317] Channel decoding is performed according to clause 7.3.3.

[0318] 8.4.4 Rate Matching

[0319] For level 2 SCI transmission on PSSCH with SL-SCH, the number of decoded modulation symbols generated for the level 2 SCI transmission before being repeated for layer 2 (if present) is denoted as Q′ SCI2 , which is determined as follows:

[0320]

[0321] ...8.4.5 Multiplexing of Decoded Level 2 SCI Bits onto PSSCH

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

[0323] *******************End of Quote [4]**********************

[0324] In TS 38.321 [5], it specifies DRX related procedures in the MAC layer in NR Uu.

[0325] *******************Quote [5]Start **************************

[0326] 5.7 Discontinuous Reception (DRX)

[0327] The MAC entity may be configured by RRC with DRX functionality that controls the PDCCH of the UE to monitor the activity of the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and AI-RNTI. When using DRX operation, the MAC entity shall also monitor the PDCCH in accordance with the requirements present in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured, the MAC entity may monitor the PDCCH discontinuously for all activated serving cells using the DRX operation specified in this clause; otherwise the MAC entity shall monitor the PDCCH as specified in TS 38.213 [6].

[0328] NOTE 1: If sidelink resource allocation mode 1 is configured by RRC, DRX functionality is not configured.

[0329] RRC controls DRX operation by configuring the following parameters:

[0330] -drx-onDurationTimer: duration of the DRX cycle start;

[0331] -drx-SlotOffset: Delay before starting drx-onDurationTimer;

[0332] -drx-InactivityTimer: duration after the PDCCH opportunity where the PDCCH indicates a new UL or DL transmission by the MAC entity;

[0333] -drx-RetransmissionTimerDL (per DL HARQ process, except the broadcast process): maximum duration until a DL retransmission is received;

[0334] -drx-RetransmissionTimerUL (per UL HARQ process): maximum duration until a grant for UL retransmission is received;

[0335] -drx-LongCycleStartOffset: the long DRX cycle and the drx-StartOffset of the subframe that defines the start of the long and short DRX cycles;

[0336] -drx-ShortCycle (optional): short DRX cycle;

[0337] -drx-ShortCycleTimer (optional): duration of the short DRX cycle that the UE should follow;

[0338] -drx-HARQ-RTT-TimerDL (per DL HARQ process, except the broadcast process): minimum duration before the MAC entity expects a DL assignment of a HARQ retransmission;

[0339] -drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before the MAC entity expects a UL HARQ retransmission grant;

[0340] -ps-Wakeup (optional): starts the configuration of the associated drx-onDurationTimer when listening but no DCP is detected;

[0341] ps-TransmitOtherPeriodicCSI (optional): configuration to report periodic CSI other than L1-RSRP on PUCCH during the duration indicated by drx-onDurationTimer if DCP is configured but the associated drx-onDurationTimer is not started;

[0342] -ps-TransmitPeriodicL1-RSRP (optional): Configuration to transmit periodic CSI for L1-RSRP on PUCCH during the duration indicated by drx-onDurationTimer if DCP is configured but the associated drx-onDurationTimer is not started.

[0343] The serving cells of the MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all serving cells belong to the one DRX group. When two DRX groups are configured, each serving cell is uniquely assigned to either of the two groups. The DRX parameters configured separately for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters common to the DRX groups are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL.

[0344] When a DRX cycle is configured, the active time for the serving cells in the DRX group includes the following times:

[0345] - the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or

[0346] -drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell in the DRX group; or

[0347] -ra-ContentionResolutionTimer (as described in Section 5.1.5) or msgB-ResponseWindow (as described in Section 5.1.4a) is running; or

[0348] - a scheduling request is sent on the PUCCH and is pending (as described in Section 5.4.4); or

[0349] - No newly transmitted PDCCH indicating the C-RNTI addressed to the MAC entity is received after successful reception of a random access response for a random access preamble that was not selected by the MAC entity among the contention-based random access preambles (as described in Sections 5.1.4 and 5.1.4a).

[0350] When DRX is configured, the MAC entity shall:

[0351] 1> If a MAC PDU is received in a configured downlink assignment:

[0352] 2> Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends;

[0353] 2>Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0354] 1> If a MAC PDU is transmitted in a configured uplink grant and no LBT failure indication is received from lower layers:

[0355] 2> Start the drx-HARQ-RTT-TimerUL of the corresponding HARQ process in the first symbol after the first transmission (in the bundle) of the corresponding PUSCH transmission ends;

[0356] 2> Stop the drx-RetransmissionTimerUL of the corresponding HARQ process at the first transmission (within the bundle) of the corresponding PUSCH transmission.

[0357] 1> If drx-HARQ-RTT-TimerDL expires:

[0358] 2> If the data corresponding to the HARQ process is not successfully decoded:

[0359] 3> Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0360] 1> If drx-HARQ-RTT-TimerUL expires:

[0361] 2> Start the drx-RetransmissionTimerUL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerUL expires.

[0362] 1> If a DRX command MAC CE or a long DRX command MAC CE is received:

[0363] 2> Stop the drx-onDurationTimer for each DRX group;

[0364] 2> Stop the drx-InactivityTimer for each DRX group.

[0365] 1> If the drx-InactivityTimer for the DRX group expires:

[0366] 2> If a short DRX cycle is configured:

[0367] 3> Start or restart the drx-ShortCycleTimer for this DRX group in the first symbol after the expiration of the drx-InactivityTimer;

[0368] 3> Use short DRX cycle for this DRX group.

[0369] 2> Otherwise:

[0370] 3> Use long DRX cycle for this DRX group.

[0371] 1> If DRX command MAC CE is received:

[0372] 2> If a short DRX cycle is configured:

[0373] 3> Start or restart the drx-ShortCycleTimer for each DRX group in the first symbol after the DRX command MAC CE is received;

[0374] 3> Use a short DRX cycle for each DRX group.

[0375] 2> Otherwise:

[0376] 3> Use a long DRX cycle for each DRX group.

[0377] 1> If the drx-ShortCycleTimer for the DRX group expires:

[0378] 2> Use long DRX cycle for this DRX group.

[0379] 1> If a long DRX command MAC CE is received:

[0380] 2> Stop the drx-ShortCycleTimer for each DRX group;

[0381] 2> Use a long DRX cycle for each DRX group.

[0382] 1> If a short DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle):

[0383] 2> Start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.

[0384] 1> If a long DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-LongCycle)=drx-StartOffset:

[0385] 2> If DCP monitoring is configured for the active DL BWP as specified in TS 38.213 [6], section 10.3:

[0386] 3> if a DCP indication is received from lower layers indicating the start of the drx-onDurationTimer associated with the current DRX cycle, as specified in TS 38.213 [6]; or

[0387] 3> if all DCP opportunities in the time domain associated with the current DRX cycle occur in active time as specified in TS 38.213 [6], consider the grant / assignment / DRX Command MAC CE / Long DRX Command MAC CE received and the Scheduling Request sent 4 ms before the start of the last DCP opportunity, or during a measurement gap, or while the MAC entity monitors PDCCH transmissions on the search space indicated by the recoverySearchSpaceId of the SpCell identified by the C-RNTI while the ra-ResponseWindow is running (as specified in section 5.1.4); or

[0388] 3> If ps-Wakeup is configured with a value of true and no DCP indication associated with the current DRX cycle is received from lower layers:

[0389] 4> Start drx-onDurationTimer after drx-SlotOffset from the beginning of the subframe.

[0390] 2> Otherwise:

[0391] 3> Start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.

[0392] NOTE 2: In case of misaligned SFN across carriers in a cell group, the SFN of the SpCell is used to calculate the DRX duration.

[0393] 1> If the DRX group is in active time:

[0394] 2> monitor the PDCCH on the serving cell in this DRX group as specified in TS 38.213 [6];

[0395] 2> If PDCCH indicates DL transmission:

[0396] 3> Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends;

[0397] NOTE 3: When HARQ feedback is deferred by PDSCH-to-HARQ_feedback timing indicating a non-numeric k1 value, as specified in TS 38.213 [6], the corresponding transmit opportunity to send DL HARQ feedback is indicated in a later PDCCH requesting HARQ-ACK feedback.

[0398] 3> Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0399] 3> If the PDSCH-to-HARQ_feedback timing indicates a non-numeric k1 value, as specified in TS 38.213 [6]:

[0400] 4> Start drx-RetransmissionTimerDL in the first symbol after PDSCH transmission for the corresponding HARQ process.

[0401] 2> If PDCCH indicates UL transmission:

[0402] 3> Start the drx-HARQ-RTT-TimerUL of the corresponding HARQ process in the first symbol after the first transmission (in the cluster) of the corresponding PUSCH transmission ends;

[0403] 3> Stop the drx-RetransmissionTimerUL of the corresponding HARQ process.

[0404] 2> If PDCCH indicates a new transmission (DL or UL) on a serving cell in this DRX group:

[0405] 3> Start or restart the drx-InactivityTimer for this DRX group in the first symbol after the end of PDCCH reception.

[0406] 2> If the HARQ process receives downlink feedback information and indicates confirmation:

[0407] 3> Stop the drx-RetransmissionTimerUL of the corresponding HARQ process.

[0408] 1> if DCP listening is configured for the active DL BWP as specified in TS 38.213 [6], section 10.3; and

[0409] 1> If the current symbol n occurs within the duration of drx-onDurationTimer; and

[0410] 1> If the drx-onDurationTimer associated with the current DRX cycle is not started as specified in this clause:

[0411] 2> If, while evaluating all DRX Active Time conditions specified in this clause, taking into account the Grant / Assignment / DRX Command MAC CE / Long DRX Command MAC CE received and the Scheduling Request sent 4 ms before symbol n, the MAC entity shall not be in Active Time:

[0412] 3> Periodic SRS and semi-static SRS defined in TS 38.214[7] are not transmitted;

[0413] 3> Do not report the semi-static CSI configured on PUSCH;

[0414] 3>If ps-TransmitPeriodicL1-RSRP is not configured with a value of true:

[0415] 4> Periodic CSI as L1-RSRP on PUCCH is not reported.

[0416] 3> If ps-TransmitOtherPeriodicCSI is not configured with a value of true:

[0417] 4>Do not report periodic CSI other than L1-RSRP on PUCCH.

[0418] 1> Otherwise:

[0419] 2> In the current symbol n, the DRX group shall not be in active time if, when evaluating all DRX active time conditions specified in this clause, the grant / assignment and DRX command MAC CE / long DRX command MAC CE scheduled on the serving cell in this DRX group received 4 ms before symbol n and the scheduling request sent:

[0420] 3> Periodic SRS and semi-static SRS defined in TS 38.214 [7] are not transmitted in this DRX group;

[0421] 3> Do not report the CSI on the PUCCH and the semi-static CSI configured on the PUSCH in this DRX group.

[0422] 2> If CSI mask (csi-Mask) is set by upper layers:

[0423] 3> in the current symbol n, if, when evaluating all DRX active time conditions specified in this clause, the grant / assignment and DRX command MAC CE / long DRX command MAC CE scheduled on the serving cell in this DRX group received 4 ms before symbol n, the drx-onDurationTimer for the DRX group shall not be running; and

[0424] 4> CSI on PUCCH is not reported in this DRX group.

[0425] NOTE 4: If a UE multiplexes CSI configured on PUCCH with other overlapping UCI according to the procedure specified in section 9.2.5 of TS 38.213 [6], and this CSI multiplexed with other UCI is to be reported on PUCCH resources outside the DRX active time of the DRX group in which this PUCCH is configured, then whether to report this CSI multiplexed with other UCI is up to the UE implementation.

[0426] Regardless of whether the MAC entity monitors PDCCH on the serving cells in the DRX group, the MAC entity transmits HARQ feedback, aperiodic CSI on PUSCH, and aperiodic SRS as defined in TS 38.214 [7] on the serving cells in the DRX group when this is expected.

[0427] If the PDCCH opportunity is incomplete (eg, the active time starts or ends in the middle of a PDCCH opportunity), the MAC entity does not need to monitor the PDCCH.

[0428] ******************End of quote [5]************************

[0429] In RP-202846 [6], it specifies WID on NR sidelink enhancement.

[0430] ******************Quote [6]Start ******************************

[0431] 3 Explanation

[0432] Since LTE, 3GPP has been developing standards for sidelinks as a tool for direct UE-to-UE communications required in various use cases. The first standard for NR sidelinks will be completed in Rel-16 under the work item "5G V2X with NR sidelink." Solutions incorporating NR sidelinks are primarily targeted for vehicle-to-everything (V2X) applications, but they may also be used for public safety applications if the service requirements are met.

[0433] At the same time, the need for NR sidelink enhancements has been identified. For V2X and public safety, due to time constraints, service requirements and operational scenarios could not be fully supported in Rel-16, and SA is currently working on several enhancements for Rel-17, such as the 3GPP Architecture Enhancements for Supporting Advanced V2X Services - Phase 2 (FS_eV2XARC_Ph2) and the System Enhancements for Proximity-Based Services in 5GS (FS_5G_ProSe). Additionally, within the SA Working Group, several work / study items are being considered for other business use cases related to the NR sidelink, such as Network Controlled Interactive Service (NCIS), Railway Gap Analysis (MONASTERYEND), Relays for Energy eFficiency and Extensive Coverage (REFEC), and Audio-Visual Service Production (AVPROD). To provide wider NR sidelink coverage for these use cases and enable the provision of radio solutions based on progress within the SA Working Group, it is necessary to specify NR sidelink enhancements within the TSG RAN.

[0434] TSG RAN initiated discussions in RAN#84 to identify detailed motivations and work areas for NR sidelink enhancements in Rel-17. Based on the latest overview in RP-192745, strong interest was observed in several motivations including the following:

[0435] Energy saving enables battery-constrained UEs to perform sidelink operations in a power-efficient manner. The Rel-16 NR sidelink is designed based on the assumption that the UE is "always on" when operating the sidelink, for example, only focusing on UEs installed in vehicles with sufficient battery capacity. The energy saving solutions in Rel-17 are needed for vulnerable road users (VRUs) in V2X use cases, as well as for UEs in public safety and commercial use cases where power consumption in the UE needs to be minimized.

[0436] Enhanced reliability and reduced latency allow support for URLLC-type sidelink use cases in a wider range of operating scenarios. Communication conditions such as the radio channel state and offered load impact the system-level reliability and latency performance of the sidelink, and in some cases, such as when the channel is relatively busy, the Rel-16 NR sidelink is expected to be limited in achieving high reliability and low latency. To continue to deliver use cases requiring low latency and high reliability under such communication conditions, solutions that can enhance reliability and reduce latency are needed.

[0437] While several areas of work were identified during the discussion, some key principles for the 3GPP evolution of the NR sidelink were also discussed. When addressing different use cases in the NR sidelink evolution, the WG should strive to achieve maximum commonality between commercial V2X and critical communications uses of the sidelink to avoid duplication of solutions and maximize economies of scale. Additionally, enhancements introduced in Rel-17 should build on the functionality specified in Rel-16, rather than reinventing the basic NR sidelink functionality in Rel-17.

[0438] 4 goals

[0439] 4.1 Objectives of SI or Core WI or Test WI

[0440] The goal of this work item is to specify radio solutions that can enhance the NR sidelink for V2X, public safety, and commercial use cases.

[0441] 1. Sidelink evaluation method update: Define evaluation assumptions and performance metrics for energy saving by reusing TR 36.843 and / or TR 38.840 (to be completed by RAN#89) [RAN1]

[0442] - Note: TR 37.885 is reused for other evaluation assumptions and performance metrics. For highway and urban grid scenarios, vehicle drop model B and antenna option 2 should be a more realistic benchmark.

[0443] 2. Resource allocation enhancement:

[0444] -Specify resource allocation to reduce UE power consumption [RAN1, RAN2]

[0445] ■ The benchmark is to introduce the principles of Rel-14 LTE sidelink random resource selection and partial sensing into Rel-16 NR sidelink resource allocation Mode 2.

[0446] ■ Note: Using Rel-14 as a reference does not preclude the introduction of new solutions to reduce power consumption if the reference does not work properly.

[0447] ■ This work should take into account the impact of sidelink DRX (if present).

[0448] - Considering the PRR and PIR defined in TR37.885 (RAN#91), study the feasibility and benefits of enhancements to improve reliability and reduce latency under Mode 2, and specify the identified solutions if deemed feasible and beneficial [RAN1, RAN2]

[0449] ■The coordination between UEs is as follows.

[0450] A resource set is determined at UE-A. In Mode 2, this set is sent to UE-B, and UE-B takes its own transmission into account when selecting resources.

[0451] ■Note: The solution should be able to operate in coverage, partial coverage, and out of coverage and be able to resolve continuous packet loss in all coverage scenarios.

[0452] ■Note: RAN2 work will be started after RAN#89.

[0453] 3. Sidelink DRX for broadcast, multicast, and unicast [RAN2]

[0454] ● Define on and off durations in the sidelink and specify corresponding UE procedures

[0455] ●Specify a mechanism to align the sidelink DRX wake-up times among UEs communicating with each other

[0456] ●Specify a mechanism to align the sidelink DRX wake-up time with the Uu DRX wake-up time of the UEs in coverage

[0457] ******************End of quote [6]************************

[0458] In the RAN1#103-e meeting [7], RAN1 has some agreements on NR V2X.

[0459] ******************Quote [7]Start ******************************

[0460] protocol:

[0461] ●Supports partial sensing-based RA as an energy-saving RA solution

[0462] ○ Details need further study

[0463] ●Support random resource selection as an energy-saving RA solution

[0464] Any changes or enhancements are subject to further research.

[0465] ○The conditions for applying random resource selection need further study

[0466] protocol:

[0467] ● In R17, the SL Mode 2 Tx resource pool can be (pre-)configured to implement only full sensing, only partial sensing, only random resource selection, or any combination thereof

[0468] ○ Details are for further study, including use cases, potential limitations, and whether / how any enhancements or conditions are needed to allow full sensing and energy-efficient RA solutions to coexist in the same resource pool.

[0469] protocol:

[0470] ● Further research on congestion control based on CBR and CR to achieve energy-saving RA scheme

[0471] ○ Identify necessary changes from R16 CBR / CR (if any), including transmission resource selection and transmission parameters that can be adapted and adapted for energy-efficient RA schemes

[0472] ○ Note: For the purpose of CBR measurement, this is not intended to require all UEs to perform sensing

[0473] ******************End of quote [7]************************

[0474] In the RAN2#112-e meeting [8], RAN2 has some agreements on NR V2X.

[0475] ******************Quote [8]Start ******************************

[0476] Agreement on SL DRX:

[0477] 1: Sidelink DRX needs to support sidelink communications in both inside and outside network coverage.

[0478] 2: RAN2 will prioritize normal use cases without considering relay UE use cases in Rel-17.

[0479] 3: Supports SL DRX for all broadcast types.

[0480] 4: If the UE is in SL active time, the UE shall monitor PSCCH. PSSCH is for further study. Sensing impact is for further study.

[0481] 5: RAN2 will not introduce SL paging and SL PO for SL DRX.

[0482] 6: As a baseline, for sidelink DRX for SL unicast, it is proposed to inherit and use similar timers used in Uu DRX. SL broadcast / multicast is for further study. Detailed timers are for further study.

[0483] 7: Working assumption: If SL DRX is used, then SL DRX should consider PSCCH monitoring also for sensing (in addition to data reception).

[0484] 8: Support for long DRX cycles for SL unicast should be assumed as a baseline. The need for short DRX cycles is for further study.

[0485] 9: In Rel-17, SL WUS cancellation priority is sorted based on RAN2 perspective.

[0486] ******************End of quote [8]************************

[0487] In R1-2007615 [9], an extended partial sensing window for aperiodic traffic is proposed.

[0488] ******************Quote [9]Start***************************

[0489] 2.2.2 Non-cyclical business

[0490] LTE-V partial sensing only handles P-UE for periodic broadcast traffic[2], while NR sidelink also needs to consider non-periodic traffic in commercial use cases. Given that LTE-V partial sensing is only performed at a subset of subframes to evaluate the periodic reservations of other UEs to determine candidate resources for PSCCH / PSSCH transmission, the UE cannot monitor any non-periodic traffic that occurs before the PSCCH / PSSCH transmission, such as Figure 4 ( Figure 5 In this example, some sensing UEs may select candidate resources reserved by aperiodic PSSCH retransmissions.

[0491] Figure 5 It is R1-2007615 Figure 4 , which shows that the non-periodic reservation (indicated in the SCI) cannot be listened to.

[0492] Observation 3: When introduced to the NR sidelink, the LTE-V partial sensing mechanism cannot evaluate NR’s aperiodic traffic, and therefore the NR partial sensing resource allocation performance will be degraded compared to LTE-V in terms of resource selection conflicts.

[0493] In the Rel-16 sidelink, up to 32 time slots can be reserved in advance via SCI for retransmission of non-periodic traffic, and a reassessment procedure (triggered at time slot m-T3) is introduced before the SCI transmission in time slot m to overcome potential resource conflicts caused by non-periodic traffic. One proposal is to select a time slot among the selected candidate resource set within the selection window. The first candidate resource in the extended sensing window is introduced before Figure 5 ( Figure 6 The TX UE may combine the sensing results based on the partial sensing time slots monitored for periodic reservation and the time slots monitored within the extended partial sensing window to determine whether to select the S A Exclude time slots The first candidate resource in .

[0494] Figure 6 It is R1-2007615 Figure 5 Reproduction of , which shows the extended partial sensing window for aperiodic traffic.

[0495] Proposal 4: Aperiodic traffic reservation can be considered to enhance NR partial sensing based on LTE-V mechanism by introducing a short sensing window before the first selected candidate resource.

[0496] Re-evaluation and pre-emption checks were introduced in Rel-16 NR-V to allow the UE to reselect resources to avoid potential transmission conflicts, which will improve the reliability of Mode 2 operation. However, given power consumption constraints, it is not necessary to perform re-evaluation and pre-emption checks before every transmission. As explained above, in addition to periodic reservations for partial sensing in LTE-V, the NR sidelink also supports aperiodic reservations and pre-emption. Re-evaluation and pre-emption checks help reduce the probability of resource conflicts, and some conditions that trigger those actions can be considered, so that the reliability of Mode 2 operation can be guaranteed while also reducing power consumption to achieve energy-saving UEs.

[0497] Proposal 5: Support re-evaluation and pre-emption checking to achieve energy-saving UE operation.

[0498] ******************End of quote [9]************************

[0499] In R1-2007688

[10] , it is proposed to use an additional sensing window for aperiodic traffic.

[0500] ********************Quote

[10] Start ******************************

[0501] 3.1. Enhancements to some sensing mechanisms

[0502] However, in NR V2X, some aspects that are different from LTE SL should be considered, such as support for aperiodic reservation, variable resource reservation period, etc. In the following, some challenges when applying partial sensing in NR SL are identified.

[0503] -Non-cyclical business

[0504] In LTE V2X, the partial sensing mechanism is designed with periodic services in mind. However, in NR V2X, aperiodic resource reservation is introduced to support aperiodic services. Therefore, according to the LTE partial sensing mechanism, the sensing UE may not be able to detect the aperiodic resource allocation from the neighboring UE just before the selection window in advance. A simple way to alleviate this problem is to add an additional sensing window before the UE's selection window. An example is shown in Figure 4 ( Figure 7 ) When resource selection is triggered for a UE, the UE sets a short-term sensing window and determines the selection window after this short-term sensing window. Preliminary simulation results of this approach can be found in Section 3.2, which show that this simple approach can maintain PRR performance while also reducing power consumption.

[0505] Figure 7 It is R1-2007688 Figure 4 A reproduction of , which shows an additional sensing window: the short-term partial sensing window.

[0506] Therefore, the following suggestions are made:

[0507] Proposal 5: To reduce the possibility of collisions caused by aperiodic resource allocation, a short-term partial sensing window should be introduced before the resource selection window for the NR partial sensing mechanism.

[0508] ********************End of quote

[10] ************************

[0509] In R1-2008189

[11] , an extended partial sensing window for aperiodic traffic is proposed.

[0510] ********************Quote

[11] Start ******************************

[0511] 2.2 Partial Sensing

[0512] In Rel-14 LTE V2X, partial sensing is an effective way to balance the power consumption and collision avoidance of pedestrian UEs. The principle of partial sensing is that the UE determines a subframe set consisting of at least Y subframes in the resource selection window as a candidate resource set, and then for each subframe in the candidate resource set UE in the previous subframe subset , other side link UEs can sense in the subframe The UE then performs RSRP-based resource exclusion and RSSI-based ranking within the candidate resource set based on the sensing results.

[0513] By monitoring the resource selection window corresponding to the periodic subframes to achieve a limited sensing window length, the LTE pedestrian UE can detect potential conflicts and estimate the quality of each resource within the resource selection window. The principle can be similarly reused in the Rel-17 NR sidelink. The NR sidelink UE can generate a candidate resource set and then for each time slot in the candidate resource set, The NR sidelink UE further determines that other sidelink UEs can The UE performs sensing on each set and then eliminates candidate resources based on the SCI decoded in the sensed time slot set.

[0514] The feasibility of full or partial sensing procedures for LTE V2X is based on the premise that most traffic in the LTE sidelink is periodic and the impact of event-triggered traffic is assessed to be acceptable. The UE can predict when packets will arrive from higher layers for transmission, and after receiving a transmission from the other sidelink UE, it can also predict the next transmission in the subsequent period. Therefore, a simple backtracking solution with periodicity configured by higher layers is sufficient to protect PRR performance in Mode 2.

[0515] However, the NR sidelink considers the important case of aperiodic transmission, and the sensing mechanism is for both periodic and aperiodic traffic types. Therefore, the performance of partial sensing like LTE needs further evaluation and may not meet the reliability requirements of some NR services.

[0516] Proposal 2: Reuse the principle of partial sensing in LTE sidelink and consider the feasibility of partial sensing corresponding to both aperiodic and periodic traffic.

[0517] Figure 8 It is R1-2008189 Figure 1 A reproduction showing partial sensing for intra-cycle and inter-cycle reservations.

[0518] In NR sidelink systems, potential future transmissions by another UE may be reflected by the received resource reservation indicated in the SCI. Figure 1 ( Figure 8 ), a single SCI format can reserve up to 2 additional sidelink resources within a 32ms time window. Therefore, each time slot within the candidate resource Corresponding to the time slot The above is a sensing time slot set of resources reserved for non-periodic services, and the sensing time slot set can be determined by the range reserved by SCI, such as time slot The previous maximum was 31 time slots.

[0519] Rel-16 sidelink also supports cross-cycle resource reservation. The cycle {0, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000} can be transmitted in the SCI to reserve resources in the subsequent cycle. Similar to the LTE P2V use case, for each time slot within the candidate resource sensed by the NR part The UE shall monitor the corresponding sensing time slot.

[0520] In addition, the introduction of reassessment check and preemption check procedures in NR partial sensing may be considered to avoid conflicts on SL and improve PRR.

[0521] Sidelink energy savings benefit from collision avoidance methods, as HARQ retransmissions minimize interference. Therefore, a UE can attempt to obtain as much resource reservation information as possible from neighboring UEs by using all of the above methods. However, these methods correspond to different sensing windows and will increase power consumption during the partial sensing procedure. Therefore, the trade-off between performance gain and power consumption should be carefully analyzed to implement partial sensing enhancements in the NR sidelink.

[0522] Proposal 3: Further study the following methods for NR sidelink partial sensing:

[0523] - Partial sensing for resource reservation within a cycle

[0524] - Partial sensing for inter-cycle resource reservation

[0525] -Reassessment and preemption

[0526] ********************End of quote

[11] ************************

[0527] In R1-2009072

[12] , an extended partial sensing window for aperiodic traffic is proposed.

[0528] ********************Quote

[12] Start ******************************

[0529] 2.1 Explanation of some sensing definitions

[0530] It's important to note up front that when using partial sensing, the savings primarily come from not using the RX chain: the UE can shut down the RX circuitry and not decode any of the sidelink channels. In previous RAN1 contributions, some companies have expressed the view that the energy savings of partial sensing mechanisms come from saving sensing computation. In our view, once the UE decodes the control information, the energy cost of performing sensing operations is negligible. In other words, if the RX chain is active, the energy savings gained by not performing sensing operations are nominal.

[0531] Proposal 1 RAN1 assumes that energy savings in partial sensing come from the possibility of switching off the RX chain during time periods when the UE is not sensing.

[0532] Furthermore, in LTE, the partial sensing mechanism assumes that pedestrian UEs will only act as transmitters. RAN1 does not specify a mechanism for aligning TX and RX behavior for partial sensing, other than pool configuration. Alignment is addressed by the implicit assumption that RX UEs will perform full sensing and continuously listen to the channel.

[0533] Observation 3: The LTE partial sensing mechanism is based on the assumption that the receiver UE is always listening / receiving and does not specify Tx / Rx alignment.

[0534] However, in NR, the assumption that the RX UE continuously senses and listens to the channel may not be valid in all situations. Therefore, it is important to assume that the RX UE may not always be active, i.e., the RX UE may not continuously listen to the channel.

[0535] Proposal 2: In NR, it is assumed that the RX UE may not monitor the channel continuously.

[0536] Therefore, it is important to explain the differences and relationship between the partial sensing mechanism specified in RAN1 and the SL DRX configuration specified in RAN2. In our view, these two mechanisms should be defined in a complementary manner, meaning they need to be aligned to optimize power savings for SL UEs. Based on this alignment between partial sensing and SL DRX configuration, in our view, the resource allocation mechanism for partial sensing defined in RAN1 does not provide for standalone Tx / Rx alignment. In other words, Tx / Rx alignment is achieved through the use of a DRX alignment procedure, which is also a goal of the DRX procedure to be specified.

[0537] Proposal 3 does not specify a separate Tx / Rx alignment procedure for partial sensing in RAN1.

[0538] As a consequence of the above proposal, when SL DRX is (pre-)configured, the (partial) sensing performed by the UE may only be available during the active time defined by the SL DRX configuration. Similarly, the resource selection window, i.e. the mechanism in which the UE selects the resources for the next transmission, should also be limited to the active time period defined by the SL DRX configuration.

[0539] Proposal 4 The (partial) sensing operations and resource selection performed by the UE take into account the active time defined by the SL DRX (if (pre)configured) configuration.

[0540] More details on the relationship between SL DRX and partial sensing mechanisms are contained in our accompanying contribution [3].

[0541] 2.2 Description of the solution

[0542] One of the main differences between NR SL and LTE SL is that NR SL is designed with both periodic and aperiodic traffic types in mind, whereas LTE SL focuses only on traffic of a periodic nature. In our view, aperiodic traffic, which is a common traffic type for advanced V2X use cases and many public safety use cases, requires some procedural differences compared to the LTE partial sensing mechanisms. For example, assuming the periodic nature of the traffic (multiples of 100ms), in LTE the RRC parameter gapCandidateSensing[4] is (pre-)configured and then used to determine the subframe index.

[0543] Observation 4 specifies that some of the sensing mechanisms used in LTE Rel-14 are optimized only for periodic traffic types.

[0544] 2.2.1 Definition of Partial Sensing Window

[0545] As described above, the partial sensing procedure in NR SL should be specified while also taking into account non-periodic traffic. This means that it is not optimal to (pre-)configure sensing opportunities within a sensing window assuming certain periodicity, as is done in LTE SL. In addition, in NR SL, the number of possible periodicities is much larger and shorter than in LTE (e.g., 1:99, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000 milliseconds). Therefore, it is not possible to define a partial sensing procedure similar to LTE SL that takes into account all possible periodicities of NR.

[0546] Observation 5 Some sensing procedures in LTE SL are not suitable for the traffic types / modes considered for NR SL.

[0547] Before describing the details of the partial sensing procedure, it is important to first explain the definition of the partial sensing window in NR SL compared to the normal sensing window defined in Release 16 and LTE partial sensing procedures. According to the Release 16 sensing procedure, the length of the sensing window can be (pre-)configured with a value of 100ms or 1100ms. In our opinion, when partial sensing is (pre-)configured for a resource pool, the UE can perform reduced sensing, i.e. sensing with limited sensing occasions. However, compared to LTE, which determines the sensing occasions based on the periodic nature of the service, i.e. periodically repeating with a step size of 100ms, NR should focus on determining the sensing occasions based on the aperiodic nature of the service. This means that it is necessary to define a number of consecutive sensing occasions (described below) that can be smaller than the normal sensing window in length. Figure 2 ( Figure 9 ) is also called a partial sensing window), and the UE triggers a sensing procedure for non-periodic services after the packet arrives.

[0548] Proposal 5 Partial Sensing Procedure supports UE to start sensing after packet arrival.

[0549] Proposal 6: Several consecutive sensing opportunities are defined as a partial sensing window that is smaller than a normal sensing window.

[0550] Figure 9 It is R1-2009072 Figure 1 and 2 The reproduction of Figure 9 Part A of R1-2009072 Figure 1 , used to show partial sensing following LTE behavior, and Figure 9 Part B is R1-2009072 Figure 2 , used to illustrate partial sensing for NR (considering the aperiodic nature of the traffic).

[0551] To illustrate the (pre)configuration of a "partial sensing window", the duration of the partial sensing window can be defined as [n, n+T4), where the value of T4 is selected by the UE within a certain range and the minimum value of T4 can be (pre)configured to be a zero logical time slot (i.e., no sensing is performed). Furthermore, in our opinion, the exact value of T4 can be adapted to optimize the performance of partial sensing as described in Section 2.1.2. below. However, the maximum possible value of T4 is limited by the PDB of the packet. In other words, the value of T4 is always smaller than the value of T2. Furthermore, as Figure 1 ( Figure 9 The periodic sensing opportunities shown in ) can be used in NR SL to Figure 2 ( Figure 9 ) for non-periodic services.

[0552] Observation 6: The periodic sensing occasion similar to the LTE procedure can be applied to the partial sensing procedure for aperiodic traffic as described in Proposals 5 and 6.

[0553] ********************End of quote

[12] ************************

[0554] In R1-2009272

[13] , an extended partial sensing window for aperiodic traffic is proposed.

[0555] ********************Quote

[13] Start ******************************

[0556] 2.2 Sensing after resource selection trigger

[0557] In this section, we propose two methods that trade off some power consumption and perform sensing after receiving a resource selection trigger to improve performance without performing full sensing. The first method uses re-evaluation after random resource selection, and the second method performs sensing and then selects a resource after receiving a resource selection trigger.

[0558] Re-evaluation enables the UE to change the selected but not yet transmitted resource based on the sensing information. This allows the UE to select different resources and avoid conflicts, thereby improving performance. In the first proposed scheme, the UE that performs random selection additionally starts sensing and performs re-evaluation after selecting the resource. The sensing information for re-evaluation will then start at the resource selection trigger, and the UE will continue to perform sensing and re-evaluation until the last re-transmission of the TB. This process is described in Figure 2 ( Figure 10 )middle.

[0559] Figure 10 It is R1-2009272 Figure 2 A reproduction showing the execution of a random selection and subsequent re-evaluation.

[0560] In the second approach, the UE performs sensing after receiving a resource selection trigger. Then, resource selection is performed after a sensing window. This enables the UE to perform sensing only when necessary to benefit from the performance improvement introduced by sensing while still saving energy. Figure 3 ( Figure 11 ) describes this process, which is compatible with both periodic and aperiodic services, especially for delay tolerant transmission.

[0561] Figure 11 It is R1-2009272 Figure 3 A reproduction of FIG1 , which shows that sensing is performed after the resource selection trigger.

[0562] Observation 3: Performing sensing after resource selection triggering enables the UE to sense only when needed and reduces power consumption.

[0563] ********************End of quote

[13] ************************

[0564] Some or all of the following terms and assumptions may be used herein.

[0565] BS: A network central unit or network node in a NR that controls one or more Transportable Resource Planners (TRPs) associated with one or more cells. Communication between the BS and the TRPs is via fronthaul. The BS can be referred to as a central unit (CU), eNB, gNB, or NodeB.

[0566] ● TRP: Transmission and reception points provide network coverage and communicate directly with UEs. TRPs may be referred to as distributed units (DUs) or network nodes.

[0567] ● Cell: A cell consists of one or more associated TRPs, i.e., the coverage of a cell consists of the coverage of all associated TRPs. A cell is controlled by one BS. Cells can be referred to as TRP groups (TRPGs).

[0568] Slot: The scheduling unit in NR. The slot duration is 14 OFDM symbols.

[0569] On the network side:

[0570] ●Downlink timing synchronization of TRPs in the same cell.

[0571] ●The RRC layer on the network side is in the BS.

[0572] On the UE side:

[0573] There are at least two UE (RRC) states: connected state (or active state) and non-connected state (or inactive state or idle state). The non-active state may be an additional state or belong to the connected state or the non-connected state.

[0574] Problem and solution:

[0575] In LTE / LTE-A sidelink (see e.g. TS 36.213 V16.4.0), a sensing-based resource selection procedure is supported in sidelink transmission mode 4. Figure 12In the example shown in , a user equipment (UE) has a candidate resource set comprising a plurality of candidate resources. The available candidate resource set is limited by a time interval [n+T1, n+T2] which may be referred to as a resource selection window. When (periodic-based) partial sensing is configured, the UE determines, by its implementation scheme, a subframe set consisting of at least Y subframes within the time interval [n+T1, n+T2], wherein the available candidate resource set is in the subframe set. If full sensing is performed, e.g., partial sensing is not configured, the available candidate resource set is in the (complete) time interval [n+T1, n+T2]. Preferably, a candidate resource may mean a candidate single subframe resource. A candidate resource may comprise one or more resource units. A resource unit may be a subchannel. Preferably, a resource unit may comprise a plurality of (physical) resource blocks in a transmission time interval (TTI). A TTI may be a subframe in LTE.

[0576] Based on the sensing results within the sensing duration, the UE may generate an effective / identified resource set, wherein the effective / identified resource set is a subset of the candidate resource set. The generation of the effective / identified resource set may be performed by excluding some candidate resources from the candidate resource set - e.g. Figure 12 The generation of the set of valid / identified resources may be performed by selecting some valid / identified candidate resources - e.g. Figure 12 And then, the UE selects one or some valid / identified resources from the valid / identified resource set to perform sidelink transmission from the UE. The resource selection for sidelink transmission may be randomly selected from the valid / identified resource set, e.g. Figure 12 Follow the steps 3-2 shown in the .

[0577] As in TS 36.213 V16.4.0, the first elimination step is that if the UE does not monitor / sense TTI z, then the UE cannot predict whether the candidate resources "z+Pany" in TTI are occupied, where Pany means any possible periodicity for transmission. Figure 12Shown as step 2-1. For the case of Pany>=100ms, the UE excludes candidate resources in TTI "z+Pany", and excludes candidate resources where the UE may have possible transmission in TTI "z+Pany". For the case of Pany<100ms, the UE excludes candidate resources in TTI "z+q·Pany", and excludes candidate resources where the UE may have possible transmission in TTI "z+q·Pany", where q is 1, 2, ..., 100 / Pany. The parameter q means that the UE excludes multiple candidate resources with a period Pany within the time interval [z, z+100]. The possible transmission may mean transmission on the selected resource. The possible transmission may mean periodic transmission of transmission on the selected resource. In addition, Pany means any possible periodicity configured by a higher layer.

[0578] The second elimination step is that if the UE receives / detects control signaling in TTI m, the UE may eliminate candidate resources according to the received control signaling. Figure 12 2-2. More specifically, if the UE receives / detects control signaling for scheduling a transmission in TTIm, and a measurement result of the scheduled transmission and / or the control signal exceeds a threshold, the UE may exclude candidate resources based on the received control signaling. The measurement result may be a reference signal received power (RSRP). More specifically, the measurement result may be a physical sidelink shared channel (PSSCH)-RSRP. The control signaling may indicate the resource of the scheduled transmission and / or the periodicity PRX of the scheduled transmission. The candidate resource excluded based on the received control signaling is the resource of the next scheduled transmission based on the resource of the scheduled transmission and the periodicity of the scheduled transmission (e.g., for a case where PRX>=100ms). In addition, the candidate resource excluded based on the received control signaling is the resource of the next multiple scheduled transmissions based on the resource of the scheduled transmission and the periodicity of the scheduled transmission (e.g., for a case where PRX<100ms). The next multiple scheduled transmissions may have a periodicity PRX within the time interval [m, m+100]. If the control signaling indicates that there is no next scheduled transmission or the control signaling indicates that the resources for the scheduled transmission are not maintained for the next time or the control signaling indicates that the scheduled transmission is the last transmission from the UE transmitting the control signaling or the control signaling indicates that the periodicity of the scheduled transmission is indicated as zero, the UE may not exclude candidate resources based on the received control signaling.

[0579] After the first elimination step and the second elimination step, the UE may select some valid / identified candidate resources from the remaining candidate resources, e.g. Figure 12As shown in step 3 of . The UE may measure resources in the sensing duration, where the measured resources are associated with the remaining candidate resources after steps 2-1 and 2-2. More specifically, for the remaining candidate resources, the timing at which the associated measured resources in the sensing duration are located is a multiple of the time period in the remaining candidate resources. For example, if the time period is 100 TTIs, then for the remaining candidate resources in TTin, the associated measured resources in the sensing duration are in TTI "nj·100", where j is a positive integer. In addition, the associated measured resources in the sensing duration have the same frequency resources as the remaining candidate resources. More specifically, the measurement is an S-Received Signal Strength Indicator (S-RSSI) measurement.

[0580] Based on the measurement, the UE may derive a metric for each remaining candidate resource. The metric for the remaining candidate resource may be a linear average of the S-RSSIs measured over the sensing duration according to the associated measured resources. And then, the UE may select a valid / identified candidate resource based on the metric for each remaining candidate resource. Preferably, one action is to select the remaining candidate resource with the smallest metric as the valid / identified candidate resource and move it to the valid / identified resource set. Repeat the actions until the UE selects a certain number of remaining candidate resources as valid candidate resources and moves the number of remaining candidate resources to the valid / identified resource set. For example, the number is greater than or equal to 20% of the total candidate resources. The number is greater than or equal to 20% of the cardinality of the candidate resource set.

[0581] Based on the current (partial) sensing procedure, the UE may determine an effective / identified resource set. The effective / identified resource set may be reported to higher layers for use in sidelink transmissions from the UE. The UE may select one or more effective / identified resources from the effective / identified resource set to perform a sidelink transmission from the UE. The sidelink transmission from the UE may be a PSSCH transmission. Preferably, the sidelink transmission from the UE may be a device-to-device transmission.

[0582] For NR sidelink transmission, there are two sidelink resource allocation modes defined for NR-V2X sidelink communication (see, for example, TS 38.214 V16.4.0):

[0583] Mode 1 is that the base station / network node can schedule sidelink resources to be used by the UE for sidelink transmission. The concept is similar to sidelink transmission mode 3 in LTE / LTE-A (see, for example, TS 36.213 V16.4.0);

[0584] ●Mode 2 is that the UE determines the sidelink transmission resources within the sidelink resources configured by the base station / network node or the pre-configured sidelink resources (for example, the base station / network node does not schedule) and the concept is similar to the sidelink transmission mode 4 in LTE / LTE-A (see, for example, TS 36.213V16.4.0).

[0585] For network scheduling modes, such as NR sidelink resource allocation mode 1, the network node may transmit a sidelink (SL) grant over the Uu interface for scheduling resources for PSCCH and / or PSSCH. The V2X UE may perform PSCCH and PSSCH transmissions over the PC5 interface in response to the received sidelink grant. The Uu interface refers to the radio interface used for communication between the network and the UE. The PC5 interface refers to the radio interface used for (direct) communication between the UE / device.

[0586] For UE (autonomous) selection modes, such as NR sidelink resource allocation mode 2, since transmission resources are not scheduled via the network, the UE may need to perform sensing before selecting resources for transmission (e.g., sensing-based transmission) to avoid resource conflicts and interference from or to other UEs. Currently, full sensing is supported in the NR sidelink. Partial sensing is not supported / designed for the NR sidelink. In addition, Figure 12 Step 3-1 shown in does not apply to the sensing procedure in the NR sidelink (see, for example, TS 38.214 V16.4.0). Based on the results of the sensing procedure, the UE may determine a valid / identified resource set. The valid / identified resource set may be reported to higher layers (of the UE). The UE may (randomly) select one or more valid / identified resources from the valid / identified resource set to perform a sidelink transmission from the UE. The sidelink transmission from the UE may be a PSCCH and / or PSSCH transmission.

[0587] Energy conservation is an enhancement within the NR Rel-17 V2X work items and objectives, enabling battery-constrained UEs to perform sidelink operations in a power-efficient manner. To reduce power consumption, partial sensing may be incorporated into Rel-17 NR sidelink resource allocation mode 2. Thus, rather than performing full sensing, which consumes more power, the UE can perform partial sensing to select sidelink resources. Note that partial sensing and resource selection are performed from the UE's transmitter perspective.

[0588] On the other hand, the NR Rel-17 V2X work item may specify / design sidelink discontinuous reception (DRX) for the UE to reduce power consumption, as the UE will not need to stay awake all the time. This means that the UE will not need to monitor / decode the physical sidelink control channel (PSCCH) and / or PSSCH in all sidelink timeslots. Preferably, the UE may monitor / decode the PSCCH and / or PSSCH during the sidelink active time. The UE may not monitor / decode the PSCCH and / or PSSCH during the sidelink inactive time. The DRX procedure in the NR Uu may be considered applicable to the NR sidelink with some modifications. Preferably, if a DRX cycle for the sidelink and / or a DRX on-duration timer for the sidelink are introduced, the UE's sidelink active time may include the time when the DRX on-duration timer for the sidelink is running. Preferably, if a DRX inactivity timer for the sidelink is introduced, the UE's sidelink active time may include the time when the DRX inactivity timer for the sidelink is running. Preferably, if a DRX retransmission timer for the sidelink is introduced, the UE's sidelink active time may include the time when the DRX retransmission timer for the sidelink is running. Preferably, the UE's sidelink active time may include the time when any one of the DRX on-duration timer for the sidelink, the DRX inactivity timer for the sidelink, or the DRX retransmission timer for the sidelink is running. It should be noted that sidelink DRX is performed from the perspective of the UE's receiver.

[0589] Although sidelink DRX can reduce UE power consumption, it may mean that the UE will not monitor / decode the PSCCH during the sidelink inactivity time. Therefore, the UE will not receive the PSCCH or sidelink control information (SCI) from other UEs during the sidelink inactivity time; therefore, the UE cannot obtain sensing results during the sidelink inactivity time.

[0590] One possible approach is to perform partial sensing during the side link active time, such as Figure 13 . When the UE triggers resource sensing (and selection) for sidelink data, for example, in time slot n, the candidate resources in the associated resource selection window may be determined / limited within the sidelink active time. It should be noted that the associated resource selection window, for example, in the time interval [n+T1, n+T2], may be upper-limited based on the remaining packet delay budget (PDB).

[0591] Furthermore, candidate resource elimination and / or generation of valid / identified resources in the associated resource selection window may be performed based on sensing results in one or more previous sidelink activity times, e.g. Figure 13. For example, a UE may receive an SCI from another UE during a previous sidelink activity time, wherein the received SCI reserves one or more sidelink resources located in an associated resource selection window. More specifically, the received SCI may schedule / indicate a sidelink transmission for delivering / transmitting a transport block (TB) from another UE, and the received SCI may reserve one or more sidelink resources for another TB different from the one TB. Preferably, the received SCI may schedule / indicate a sidelink transmission for delivering / transmitting a TB via a "frequency resource assignment" field and a "time resource assignment field". Preferably, the received SCI may reserve one or more sidelink resources for another TB via a "resource reservation period" field and / or a "frequency resource assignment" field and a "time resource assignment field". In this case, the UE may exclude candidate resources that overlap (partially or completely) with one or more sidelink resources reserved by the SCI received during the previous sidelink activity time. The UE may not generate valid / identified resources that overlap (partially or completely) with one or more sidelink resources reserved by the SCI received in the previous sidelink activity time. Finally, the UE may select one or more sidelink resources from the valid / identified resources and then perform sidelink transmission on the selected one or more sidelink resources.

[0592] Figure 13 The example shown in can process sensing results associated with resource reservation information for periodic sidelink data (e.g., one TB and another TB from another UE). However, the UE may not be able to obtain resource reservation information for aperiodic sidelink data (transmitted from other UEs). In the current NR sidelink design, one SCI in time slot m can schedule / indicate sidelink resources up to time slot m+31 for the same TB. Therefore, there are some proposals to perform additional sensing to obtain this resource reservation information for aperiodic sidelink data (see, for example, [9] to

[13] ). Therefore, the exclusion of candidate resources and / or the generation of valid / identified resources can be performed based on partial / periodic sensing results and additional sensing results.

[0593] like Figure 14A and 14B As shown in the example of , when a UE triggers resource sensing (and selection) for sidelink data, for example, in time slot n, the UE may perform additional sensing within an additional sensing duration, for example, a time interval [n, n+T4] or (n, n+T4), for obtaining resource reservation information from other UEs. More specifically, T4 may be 31. The associated resource selection window may start after the additional sensing duration, for example, at Figure 14A In the time interval [n+T4+T1, n+T4+T2] shown in Figure 14BThe candidate resource elimination and / or generation of valid / identified resources in the associated resource selection window may be performed based on the sensing results in the previous one or more sidelink activity times and the sensing results in the additional sensing duration.

[0594] For example, a UE may receive an SCI from another UE during an additional sensing duration, wherein the received SCI may schedule / indicate a sidelink transmission from the other UE in an associated resource selection window. More specifically, the received SCI may schedule / indicate sidelink resources for the scheduled / indicated sidelink transmission from the other UE. Preferably, the received SCI may schedule / indicate sidelink resources via a "frequency resource assignment" field, a "time resource assignment field," and / or a "resource reservation period" field. In this case, the UE may exclude candidate resources that overlap (partially or completely) with the sidelink resources scheduled / indicated / reserved by the SCI received during the additional sensing duration. The UE may not generate valid / identified resources that overlap (partially or completely) with the sidelink resources scheduled / indicated / reserved by the SCI received during the additional sensing duration. Finally, the UE may select one or more sidelink resources from the valid / identified resources and then perform sidelink transmission on the selected one or more sidelink resources.

[0595] However, additional sensing design may induce some problems.

[0596] One problem is that when the UE triggers resource sensing and selection for sidelink data, the additional sensing duration may induce a delay for delivering / transmitting the sidelink data, such as an additional 31 time slots. This problem is because the UE may select the sidelink resource after the additional sensing duration.

[0597] Furthermore, the additional sensing duration may induce a restriction such that sidelink resources in the first 32 time slots of each sidelink active time are not available for selection or use by the UE to perform sidelink transmissions, since the UE may select sidelink resources after performing the additional sensing duration. Such a restriction will result in additional latency and inefficient resource utilization.

[0598] To address the aforementioned challenges and problems, various embodiments, methods, systems, apparatuses, and mechanisms are provided below.

[0599] The first UE may operate sidelink DRX. The first UE may receive / monitor SCI during the sidelink active time. The sidelink active time may be determined / derived based on the sidelink DRX configuration / parameters. The sidelink active time may occur periodically (e.g., every DRX cycle). The concept of this method (b) is that the first UE may perform additional sensing within a set of (consecutive) time slots prior to the start boundary / timing of a sidelink active time to obtain resource reservation information from one or more other UEs. Preferably, in some embodiments, the number of (consecutive) time slot sets may be equal to a specific value.

[0600] Preferably, in some embodiments, the (continuous) time slot set may be / mean a specific value of (continuous) time slots before the start boundary / timing of a sidelink active time. Preferably or alternatively, in some embodiments, the number of (continuous) time slot sets may be less than the specific value. Preferably, in some embodiments, the (continuous) time slot set may be the (latter) portion of a specific value of (continuous) time slots before the start boundary / timing of a sidelink active time.

[0601] For example, assuming that additional sensing requires 31 time slots (e.g., a specific value is 31), if the UE's sidelink active time is in time slot [251, 320] (assuming that the previous sidelink active time is in time slot [51, 120]), the UE may perform additional sensing in the additional sensing duration [220, 250] or [220, 251). Preferably, in some embodiments, the first UE may trigger resource sensing and selection in time slot 220, such as Figure 15A Preferably or alternatively, in some embodiments, the first UE may trigger resource sensing and selection in time slot 210, while the first UE does not perform additional sensing in time slots [210, 219], as shown in FIG. Figure 15B As shown in .

[0602] Preferably, in some embodiments, the specific value may be 31. Preferably or alternatively, in some embodiments, the specific value may be 32.

[0603] Preferably or alternatively, in some embodiments, the specific value may be (31+T1) or a ceiling function of (31+T1).

[0604] Preferably, in some embodiments, the specific value may be a (pre)configured value. Preferably, in some embodiments, the specific value may be a specified value.

[0605] Preferably, in certain embodiments, the first UE may perform sidelink DRX and / or additional sensing in the sidelink resource pool. Preferably, in certain embodiments, the specific value may be determined based on the CBR of the sidelink resource pool. For example, if the CBR of the sidelink resource pool is lower than a CBR threshold, the specific value may be determined as a smaller value. If the CBR of the sidelink resource pool is greater than the CBR threshold, the specific value may be determined as a larger value. Alternatively, if the CBR of the sidelink resource pool is lower than the CBR threshold, the specific value may be determined as a larger value. If the CBR of the sidelink resource pool is greater than the CBR threshold, the specific value may be determined as a smaller value.

[0606] Preferably, in certain embodiments, the first UE may (trigger) perform resource sensing (and selection) for determining a first side link resource, and then the first UE performs a first (control and / or data) side link transmission on the first side link resource for delivering / transmitting side link data.

[0607] Preferably, in certain embodiments, the specific value may be determined based on the data priority of the sidelink data. For example, if the data priority of the sidelink data is lower than a priority threshold, the specific value may be determined as a smaller value. If the data priority of the sidelink data is higher than the priority threshold, the specific value may be determined as a larger value. Alternatively, if the data priority of the sidelink data is lower than the priority threshold, the specific value may be determined as a larger value. If the data priority of the sidelink data is higher than the priority threshold, the specific value may be determined as a smaller value.

[0608] Preferably, in certain embodiments, the specific value may be determined based on the latency requirement or (remaining) PDB of the sidelink data. For example, if the latency requirement or (remaining) PDB of the sidelink data is shorter than a time threshold, the specific value may be determined as a smaller value. If the latency requirement or (remaining) PDB of the sidelink data is greater than a time threshold, the specific value may be determined as a larger value. Alternatively, if the latency requirement or (remaining) PDB of the sidelink data is shorter than a time threshold, the specific value may be determined as a larger value. If the latency requirement or (remaining) PDB of the sidelink data is greater than a time threshold, the specific value may be determined as a smaller value.

[0609] In one embodiment, the first UE may (trigger) perform resource sensing (and selection) before the start boundary / timing of a sidelink active time. Preferably, in certain embodiments, the first UE may (trigger) perform resource sensing (and selection) during a sidelink inactive time. Preferably, in certain embodiments, the first sidelink resource is during a sidelink active time. It may not be allowed that the sidelink resource during the sidelink inactive time is the first sidelink resource. The first UE avoids / prevents selecting the sidelink resource during the sidelink inactive time as the first sidelink resource.

[0610] Preferably, in some embodiments, if the first UE performs resource sensing (and selection) (triggered) before a start boundary / timing of a sidelink activity time, the first UE may perform additional sensing within a set of (continuous) time slots before the start boundary / timing of the sidelink activity time. If the first UE does not perform resource sensing (and selection) (triggered) within a sidelink inactive time before a start boundary / timing of the sidelink activity time, the first UE may not perform additional sensing within a set of (continuous) time slots before the start boundary / timing of the sidelink activity time.

[0611] Preferably, in some embodiments, if the first UE (triggers) to perform resource sensing (and selection) in a timing before a specific value of (continuous) time slots before the start boundary / timing of a side link active time, the first UE starts to perform additional sensing in a specific value of (continuous) time slots. This may mean that the (continuous) time slot set is a specific value of (continuous) time slots. Preferably, in some embodiments, the first UE may perform additional sensing within the additional sensing duration, wherein the additional sensing duration includes / contains / consists of a specific value of (continuous) time slots. Preferably, in some embodiments, the first UE does not perform additional sensing before the specific value of (continuous) time slots (after the timing at which the first UE (triggers) to perform resource sensing (and selection)). This situation is shown in Figure 15B In other words, the first UE does not perform additional sensing in the time gap between the timing of (triggering) performing resource sensing (and selection) and the first time slot of a specific value of (consecutive) time slots before the start boundary / timing of one sidelink active time.

[0612] Preferably, in some embodiments, if the first UE (trigger) performs resource sensing (and selection) in a timing within a specific value of (continuous) time slots before the start boundary / timing of a side link active time, then when the first UE (trigger) performs resource sensing (and selection), the first UE may start to perform additional sensing, such as Figure 15CAs shown in . Preferably, in some embodiments, the (continuous) time slot set may be the (latter) part of a specific value of (continuous) time slots. Preferably, in some embodiments, the first UE may perform additional sensing within the additional sensing duration. The additional sensing duration may at least include / contain a (continuous) time slot set before the start boundary / timing of a side link active time. Preferably, in some embodiments, the additional sensing duration may include / contain another (continuous) time slot set starting from the start boundary / timing of a side link active time. Preferably, in some embodiments, the total value of the number of (continuous) time slot sets and the number of another (continuous) time slot set is equal to a specific value. Preferably, in some embodiments, the first UE does not perform additional sensing in a timing within the side link inactive time, wherein the timing is before the first UE (trigger) performs resource sensing (and selection).

[0613] In one embodiment, regardless of whether the first UE performs (triggers) resource sensing (and selection) at a timing within the sidelink inactive time, the first UE may perform additional sensing in a specific number of (continuous) time slots before (each) starting boundary / timing of each sidelink active time. Preferably, in certain embodiments, the first UE may perform additional sensing within an additional sensing duration, wherein the additional sensing duration includes / contains / consists of a specific number of (continuous) time slots before the starting boundary / timing of each sidelink active time.

[0614] More specifically, if the first UE performs resource sensing (and selection) (triggered) within the sidelink inactive time before the start boundary / timing of a sidelink active time, the first UE may perform additional sensing within a specific value of (continuous) time slots before the start boundary / timing of the sidelink active time. If the first UE does not perform resource sensing (and selection) (triggered) within the sidelink inactive time before the start boundary / timing of the sidelink active time, the first UE may perform additional sensing within a specific value of (continuous) time slots before the start boundary / timing of the sidelink active time. This may mean that the (continuous) time slot set is a specific value of (continuous) time slots. This situation is shown in Figure 15D The first UE has performed additional sensing within a specific number of (continuous) time slots before the start boundary / timing of a sidelink activity time. Even when the first UE performs (triggered) resource sensing (and selection) at the start timing of a sidelink activity time, the first UE may not need to perform additional sensing after the first UE (triggered) resource sensing (and selection). Therefore, the sidelink resources in the early time slots of a sidelink activity time are available for selection or use by the first UE to perform a first (control and / or data) sidelink transmission.

[0615] Preferably, in certain embodiments, for additional sensing during sidelink inactivity time, the first UE may receive / listen (only) level 1 SCI. The first UE may receive / listen (only) SCI format 1. The first UE may receive / listen (only) PSCCH. Preferably, in certain embodiments, the first UE may not receive / listen level 2 SCI. The first UE may not receive / listen SCI format 2-A / 2-B. The first UE may not receive / decode PSSCH.

[0616] Alternatively, for additional sensing in the sidelink inactive time, the first UE may receive / listen to level 1 SCI and / or level 2 SCI.The first UE may receive / listen to SCI format 1 and / or SCI format 2-A / 2-B.

[0617] Preferably, in certain embodiments, for additional sensing during the sidelink active time, the first UE may receive / monitor level 1 SCI and / or level 2 SCI. The first UE may receive / monitor SCI format 1 and / or SCI format 2-A / 2-B. The first UE may receive / monitor the PSCCH of SCI format 1. The first UE may receive / decode the PSSCH for receiving SCI format 2-A / 2-B.

[0618] refer to Figure 16 According to this and other concepts and methods of the present invention, a method 1000 of a first device performing sidelink communication to at least a second device includes the following steps: wherein, at step 1002, the first device performs a sidelink DRX procedure. At step 1004, the first device receives / listens for SCI in a sidelink active time, wherein the sidelink active time is determined / derived based on a sidelink DRX configuration / parameter. At step 1006, the first device performs additional sensing within a set of (contiguous) time slots before a start boundary / timing of a sidelink active time. At step 1008, the first device determines / selects a first sidelink resource based at least on a sensing result of the additional sensing. At step 1010, the first device performs a first (control and / or data) sidelink transmission on the first sidelink resource for transmitting the sidelink data to the second device.

[0619] In some embodiments, the (continuous) time slot set is the (latter) part of a specific value of (continuous) time slots before the start boundary / timing of one side link active time.

[0620] In some embodiments, the (continuous) time slot set is a specific value of (continuous) time slots before the start boundary / timing of one side link active time.

[0621] In some embodiments, the method further includes: when the first device triggers resource sensing and selection during the side link inactive time before the start boundary / timing of a side link active time, the first device performs additional sensing within a (continuous) time slot set before the start boundary / timing of a side link active time.

[0622] In some embodiments, the method further includes: when the first device does not trigger resource sensing and selection within the side link inactive time before the start boundary / timing of a side link active time, the first device does not perform additional sensing within the (continuous) time slot set before the start boundary / timing of a side link active time.

[0623] In some embodiments, if the first device triggers resource sensing and selection in a timing before a specific value of (continuous) time slots before the start boundary / timing of a side link active time (in the side link inactive time), the first device starts to perform additional sensing in the specific value of (continuous) time slots, and / or the first device does not perform additional sensing before the specific value of (continuous) time slots, and / or the (continuous) time slot set is a specific value of (continuous) time slots.

[0624] In some embodiments, if the first device triggers resource sensing and selection within a specific value of (continuous) time slots before the start boundary / timing of a side link active time, the first device starts to perform additional sensing when the first device triggers resource sensing and selection, and / or the (continuous) time slot set is the (latter) part of the specific value of (continuous) time slots, and / or the first device performs additional sensing within the additional sensing duration, wherein the additional sensing duration at least includes / contains the (continuous) time slot set and another (continuous) time slot set starting from the start boundary / timing of a side link active time, and / or wherein the total value of the number of (continuous) time slot sets and the number of another (continuous) time slot sets is equal to a specific value.

[0625] In some embodiments, the method further includes: regardless of whether the first device triggers resource sensing and selection within the side link inactive time before the start boundary / timing of a side link active time, the first device performs additional sensing within a (continuous) time slot set before the start boundary / timing of a side link active time, and / or wherein the (continuous) time slot set is a specific value of (continuous) time slots before the start boundary / timing of a side link active time.

[0626] In some embodiments, the first device performs additional sensing within an additional sensing duration, wherein the additional sensing duration includes / contains / consists of a specific value of (continuous) time slots before a start boundary / timing of each side link activity time.

[0627] In some embodiments, the specific value is 31 or 32.

[0628] In some embodiments, the specific value is (31+T1) or a ceiling function of (31+T1).

[0629] In some embodiments, the specific value is (pre-)configured or specified.

[0630] In certain embodiments, the first device performs additional sensing in the sidelink resource pool and / or determines a specific value based on the CBR of the sidelink resource pool.

[0631] In certain embodiments, the specific value is determined based on the data priority of the sidelink data.

[0632] In some embodiments, the specific value is determined based on the latency requirement or the (remaining) PDB of the sidelink data.

[0633] In certain embodiments, for additional sensing in the sidelink inactive time, the first device receives / listens for (only) level 1 SCI.

[0634] In certain embodiments, for additional sensing in the sidelink inactive time, the first device receives / listens to the level 1 SCI and / or the level 2 SCI.

[0635] Return Reference Figure 3 and 4 In one or more embodiments, the device 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to: (i) perform sidelink communication to at least a second device at the first device, with the first device performing a sidelink DRX procedure, (ii) receive / listen for SCI at the first device during a sidelink active time, wherein the sidelink active time is determined / derived based on the sidelink DRX configuration / parameters, (iii) perform additional sensing at the first device within a set of (consecutive) time slots before a start boundary / timing of a sidelink active time, (iv) determine / select a first sidelink resource at the first device based at least on a sensing result of the additional sensing, and (v) perform a first (control and / or data) sidelink transmission on the first sidelink resource at the first device for transmitting the sidelink data to the second device. 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 elsewhere herein.

[0636] refer to Figure 17According to this and other concepts and methods of the present invention, a method 1020 for a first device to perform sidelink communication to at least a second device in a sidelink resource pool includes the following steps: wherein, at step 1022, the first device triggers resource selection for sidelink data at a timing. At step 1024, the first device performs sensing for a first continuous sensing duration prior to a sidelink on duration active time of the second device. At step 1026, the first device determines / selects a first sidelink resource from a set of sidelink resources, wherein, at step 1028, the set of sidelink resources is derived or determined based on at least the sensing results during the first continuous sensing duration. At step 1030, the first device performs a first sidelink transmission on the first sidelink resource for transmitting sidelink data to the second device.

[0637] In some embodiments, the side link on duration activity time of the second device is the most recent side link on duration activity time of the second device after the timing, and / or the first continuous sensing duration is derived or determined based on (the starting boundary / timing of) the side link on duration activity time of the second device.

[0638] In some embodiments, the specific value is 31, 32, (pre) configured or specified, and / or the specific value is determined based on the data priority of the side link data, and / or the specific value is determined based on the delay requirement or (remaining) packet delay budget of the side link data, and / or the specific value is determined based on the channel busy ratio of the side link resource pool.

[0639] In some embodiments, the timing is before (just before) a specific value of (continuous) TTIs before (the start boundary / timing of) the side link on duration active time of the second device, and / or the first device performs sensing in a specific value of (continuous) TTIs in response to a resource selection trigger, and / or the first continuous sensing duration is or includes a specific value of (continuous) TTIs, and / or in response to a trigger to perform resource selection, the first device does not perform sensing before the first continuous sensing duration (and after the timing).

[0640] In some embodiments, the timing is within a specific value of (continuous) TTIs before (just before) the side link on duration active time of the second device (the starting boundary / timing), and / or the first device starts performing sensing in response to a resource selection trigger, and / or the first continuous sensing duration includes the latter part of the specific value of (continuous) TTIs after the timing.

[0641] In certain embodiments, the first device performs sensing within a second continuous sensing duration, the second continuous sensing duration starting from (the starting boundary / timing of) the side link on duration activity time of the second device, and / or the side link resource set is derived or determined based on the sensing results in the first continuous sensing duration and the sensing results in the second continuous sensing duration, and / or the sum of the number of TTIs of the first continuous sensing duration and the number of TTIs of the second continuous sensing duration is equal to a specific value.

[0642] In some embodiments, regardless of whether the first device triggers resource selection, the first device performs sensing within a first continuous sensing duration before the side link on duration active time of the second device, and / or the first continuous sensing duration is or includes (just before) a specific value of (continuous) TTIs before (the starting boundary / timing of) the side link on duration active time of the second device.

[0643] In some embodiments, the timing is outside the side link on duration active time of the second device, and / or the first continuous sensing duration is outside the side link on duration active time of the second device, and / or the first continuous sensing duration ends in the starting boundary / timing of the side link on duration active time of the second device, and / or the first continuous sensing duration is just before the side link on duration active time of the second device.

[0644] In some embodiments, the first device assumes or determines the sidelink on duration active time of the second device based on the sidelink DRX on duration timer configuration of the second device, and / or the sidelink on duration active time includes the time when the associated sidelink DRX on duration timer is running.

[0645] In certain embodiments, the timing is outside the side link on duration active time of the first device, and / or (the portion of) the first continuous sensing duration is outside the side link on duration active time of the first device.

[0646] In certain embodiments, the timing is a sidelink TTI (in sidelink TTI) in the sidelink resource pool. The first continuous sensing duration consists of the sidelink TTI in the sidelink resource pool, and / or the second continuous sensing duration consists of the sidelink TTI in the sidelink resource pool, and / or a specific value of (continuous) TTIs consists of the sidelink TTI in the sidelink resource pool. The first continuous sensing duration includes the sidelink TTI in the sidelink resource pool, and / or the second continuous sensing duration includes the sidelink TTI in the sidelink resource pool, and / or the specific value of (continuous) TTIs includes the sidelink TTI in the sidelink resource pool.

[0647] In certain embodiments, sensing within the first continuous sensing duration does not imply periodicity-based partial sensing, and / or sensing within the first continuous sensing duration does not imply reserved period-based sensing.

[0648] Return Reference Figure 3 and 4 In one or more embodiments, the device 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to: (i) perform sidelink communication to at least a second device in a sidelink resource pool at a first device, with the first device triggering resource selection for sidelink data at a timing, (ii) perform sensing at the first device for a first continuous sensing duration before a sidelink on duration active time of the second device, (iii) determine / select a first sidelink resource from a sidelink resource set at the first device, (iv) derive / determine a sidelink resource set at the first device based on at least the sensing results in the first continuous sensing duration, and (v) perform a first sidelink transmission on the first sidelink resource at the first device for transmitting sidelink data to the second device. 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 elsewhere herein.

[0649] Any combination of the above concepts or teachings may be combined or formed into one or more new embodiments.The disclosed details and embodiments provided below can be used to at least (but not limited to) solve the problems mentioned above and herein.

[0650] Preferably, in some embodiments, the start boundary / timing of a side link activity time may be the start time slot boundary / start time slot timing of a side link activity time.

[0651] Preferably, in some embodiments, the start boundary / timing of a sidelink active time may be a start symbol boundary / start symbol timing of a sidelink active time. Preferably, in some embodiments, the symbol is the first symbol available for sidelink transmission in a time slot.

[0652] Preferably, in certain embodiments, when the first UE requires sidelink resources for communicating / transmitting sidelink data / when the first UE requires sidelink resources for communicating / transmitting sidelink data, the first UE may (trigger) to perform resource sensing (and selection). Preferably, in certain embodiments, the first sidelink (control and / or data) transmission is a new / initial sidelink transmission of the sidelink data. Preferably, in certain embodiments, the first sidelink (control and / or data) transmission is a sidelink retransmission of the sidelink data.

[0653] Preferably, in some embodiments, the sidelink data may refer to a TB. Preferably, in some embodiments, the transport block may refer to / be a MAC PDU.

[0654] Preferably, in certain embodiments, the non-periodic sidelink data may refer to a transport block, wherein the "Resource Reservation Period" field in the SCI scheduling the transport block indicates a zero value for the reservation period.

[0655] Preferably, in certain embodiments, the periodic sidelink data may refer to a transport block, wherein the "Resource Reservation Period" field in the SCI scheduling the transport block indicates a non-zero value for the reservation period.

[0656] Preferably, in some embodiments, the time unit of the additional sensing duration may be a time slot.

[0657] Preferably, in some embodiments, the time unit of the (continuous) time interval may be a time slot.

[0658] Preferably, in some embodiments, the time slot may refer to a side link time slot.

[0659] Preferably, in certain embodiments, the first UE may perform resource sensing (and selection) in the sidelink resource pool. Preferably, in certain embodiments, the first UE may perform additional sensing in the sidelink resource pool. Preferably, in certain embodiments, the first UE may perform sidelink DRX in the sidelink resource pool. Preferably, in certain embodiments, a time slot may refer to / include a sidelink time slot associated with a sidelink resource pool. Preferably, in certain embodiments, a time slot may not refer to / include a sidelink time slot associated with another sidelink resource pool.

[0660] Preferably, in certain embodiments, consecutive time slots in the sidelink resource pool may not be consecutive in physical time slots. This means that from the perspective of physical time slots, consecutive time slots in the sidelink resource pool may not be consecutive. Preferably, in certain embodiments, consecutive time slots in the sidelink resource pool may not be consecutive in sidelink time slots in a carrier / cell. This means that from the perspective of sidelink time slots in a carrier / cell, consecutive time slots in the sidelink resource pool may not be consecutive. Preferably, in certain embodiments, one or more sidelink resource pools may exist in a carrier / cell.

[0661] Preferably, in some embodiments, additional sensing may mean / include short sensing before performing resource selection or before a resource selection window. Preferably, in some embodiments, additional sensing may mean / include short sensing before candidate resources for resource sensing and selection.

[0662] Preferably, in some embodiments, additional sensing may mean / include sensing for a duration preceding a candidate resource for resource sensing and selection.

[0663] Preferably, in some embodiments, additional sensing may mean / include continuous sensing. Preferably, in some embodiments, additional sensing in the additional sensing duration may mean / include continuous sensing for at least the (continuous) additional sensing duration. Preferably, in some embodiments, additional sensing does not mean periodic partial sensing. Preferably, in some embodiments, additional sensing does not mean reserved period-based sensing.

[0664] Preferably, in some embodiments, partial sensing may mean / include periodic sensing and / or additional sensing based on periodicity. Preferably, in some embodiments, partial sensing may mean / include periodic sensing and / or continuous sensing based on periodicity. Preferably, in some embodiments, partial sensing based on periodicity may mean / include sensing based on a (reserved) cycle set. Preferably, in some embodiments, partial sensing based on periodicity may mean / include sensing of time slots / resources associated with candidate resources for resource sensing and selection, wherein the association is based on a (reserved) cycle set. Preferably, in some embodiments, the (reserved) cycle set is (pre)configured. Preferably, in some embodiments, the (reserved) cycle set is (pre)configured for the first UE.

[0665] Preferably, in certain embodiments, the (reserved) period set is (pre)configured for the sidelink resource pool. Preferably, in certain embodiments, the (reserved) period set is specified. Preferably, in certain embodiments, the (reserved) period set may include / include all or part of the supported reservation periods in the sidelink resource pool. Preferably, in certain embodiments, the (reserved) period set may include / include reservation periods having a period value greater than a specific value. Preferably, in certain embodiments, the (reserved) period set may include / include reservation periods having a period value greater than a specific value. This means that the (reserved) period set used for periodic partial sensing may include / include some reservation periods not covered by the additional sensing (duration). This is because resource reservation information for sidelink data having a reservation period value less than a specific value can be obtained via additional sensing. Preferably, in certain embodiments, the (reserved) period value may be in milliseconds. Preferably, in certain embodiments, the (reserved) period value may be (converted / changed) to) time slots for comparison with the specific value.

[0666] Preferably, in some embodiments, the (reserved) period set may be determined / derived based on the sidelink DRX configuration. Preferably, in some embodiments, the (reserved) period set may be determined / derived based on the sidelink DRX cycle and / or the on-duration timer.

[0667] Preferably, in some embodiments, the first UE obtains resource reservation information from one or more other UEs via SCI received from the one or more other UEs. Preferably, in some embodiments, the SCI from the one or more other UEs contains resource reservation information of another UE.

[0668] Preferably, in some embodiments, the sidelink data is for the second UE.Preferably, in some embodiments, the first UE performs a first (control and / or data) sidelink transmission on the first sidelink resource for delivering / transmitting the sidelink data to the second UE.

[0669] Preferably, in certain embodiments, the first UE may have / maintain / establish a sidelink link / connection with the second UE over the PC5 interface. Preferably, in certain embodiments, sidelink DRX is performed / operated for sidelink communication between the first UE and the second UE. Preferably, in certain embodiments, the sidelink DRX configuration is configured for the sidelink link / connection between the first UE and the second UE. Preferably, in certain embodiments, the sidelink DRX configuration is configured for the first UE. Preferably, or alternatively, in certain embodiments, the sidelink DRX configuration is configured for the second UE.

[0670] Preferably, in some embodiments, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the sidelink link / connection between the first UE and the second UE. Preferably, in some embodiments, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the second UE. Preferably, or alternatively, in some embodiments, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the first UE.

[0671] Preferably, in some embodiments, the sidelink active time associated with partial sensing is associated / derived / determined based on a sidelink DRX configuration for a sidelink link / connection between the first UE and the second UE. Preferably, in some embodiments, the sidelink active time associated with partial sensing is associated / derived / determined based on a sidelink DRX configuration for the second UE. Preferably, or alternatively, in some embodiments, the sidelink active time associated with partial sensing is associated / derived / determined based on a sidelink DRX configuration for the first UE.

[0672] In one embodiment, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the sidelink link / connection between the first UE and the second UE. The sidelink active time associated with the partial sensing is associated / derived / determined based on the sidelink DRX configuration for the sidelink link / connection between the first UE and the second UE.

[0673] In one embodiment, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the second UE. The sidelink active time associated with the partial sensing is associated / derived / determined based on the sidelink DRX configuration for the first UE.

[0674] In one embodiment, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the second UE. The sidelink active time associated with the partial sensing is associated / derived / determined based on the sidelink DRX configuration for the second UE.

[0675] In one embodiment, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the first UE. The sidelink active time associated with the partial sensing is associated / derived / determined based on the sidelink DRX configuration for the first UE.

[0676] Preferably, in certain embodiments, the first UE may have / maintain / establish a sidelink link / connection with a sidelink group over a PC5 interface, wherein the sidelink group includes at least the first UE and a second UE. Preferably, in certain embodiments, sidelink DRX is performed / operated for sidelink communications of the sidelink group. Preferably, in certain embodiments, the sidelink DRX configuration is configured for the sidelink group. Preferably, in certain embodiments, the sidelink DRX configuration is configured for the first UE.

[0677] Preferably, in some embodiments, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the sidelink group. Preferably, or alternatively, in some embodiments, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the first UE.

[0678] Preferably, in some embodiments, the sidelink active time associated with partial sensing is associated / derived / determined based on the sidelink DRX configuration for the sidelink group. Preferably, or alternatively, in some embodiments, the sidelink active time associated with partial sensing is associated / derived / determined based on the sidelink DRX configuration for the first UE.

[0679] In one embodiment, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the sidelink group. Preferably, in certain embodiments, the sidelink active time associated with the partial sensing is associated / derived / determined based on the sidelink DRX configuration for the sidelink group.

[0680] In one embodiment, the sidelink active time associated with the additional sensing is associated / derived / determined based on the sidelink DRX configuration for the sidelink group. Preferably, in certain embodiments, the sidelink active time associated with the partial sensing is associated / derived / determined based on the sidelink DRX configuration for the first UE.

[0681] Preferably, in certain embodiments, the first UE may determine / derive the resource selection window based on the sidelink active time of the second UE - for example, the resource selection window is within the sidelink active time of the second UE (limited to the sidelink active time). Preferably, in certain embodiments, the first UE may determine / derive the resource selection window based on the sidelink DRX configuration for the second UE. Preferably or alternatively, in certain embodiments, the first UE may determine / derive the resource selection window based on the sidelink DRX configuration for the first UE. Preferably or alternatively, in certain embodiments, the first UE may determine / derive the resource selection window based on the sidelink DRX configuration for the sidelink link / connection between the first UE and the second UE. Preferably or alternatively, in certain embodiments, the first UE may determine / derive the resource selection window based on the sidelink DRX configuration for the sidelink group.

[0682] Preferably, in some embodiments, the first UE may have / maintain / establish multiple sidelink links / connections on the PC5 interface. For different sidelink links / connections, the first UE may perform sidelink transmission to / receive from different paired UEs.

[0683] Preferably, in some embodiments, the first UE may have / maintain / establish a first sidelink link / connection and a second sidelink link / connection. The paired UE of the first sidelink link / connection may be different from the paired UE of the second sidelink link / connection. Preferably, in some embodiments, one or more sidelink logical channels associated with (the paired UE of) the first sidelink link / connection and one or more sidelink logical channels associated with (the paired UE of) the second sidelink link / connection are separate / unrelated.

[0684] Preferably, in some embodiments, the data packet is associated with at least a sidelink logical channel. Preferably, in some embodiments, the sidelink data is from at least a sidelink logical channel.

[0685] Preferably, in some embodiments, the sidelink data transmission may be / means PSSCH transmission.

[0686] Preferably, in some embodiments, the sidelink control transmission may be / means PSCCH transmission.

[0687] Preferably, in certain embodiments, at least the SCI may be conveyed in the PSCCH. Preferably, in certain embodiments, the sidelink control information may include level 1 SCI. Preferably, in certain embodiments, the level 1 SCI may be transmitted via the PSCCH. Preferably, in certain embodiments, the sidelink control information may include level 2 SCI. Preferably, in certain embodiments, the level 2 SCI may be transmitted multiplexed with the PSSCH. Preferably, in certain embodiments, SCI format 1 is the level 1 SCI. Preferably, in certain embodiments, SCI format 2-A is the level 2 SCI. Preferably, in certain embodiments, SCI format 2-B is the level 2 SCI.

[0688] Preferably, in some embodiments, a sidelink time slot may refer to a time slot used for the sidelink. Preferably, in some embodiments, a sidelink time slot may be expressed as a TTI. Preferably, in some embodiments, a TTI may be a subframe (used for the sidelink). Preferably, in some embodiments, a TTI includes multiple symbols, such as 12 or 14 symbols. Preferably, in some embodiments, a TTI may be a time slot that (completely / partially) includes sidelink symbols. Preferably, in some embodiments, a TTI may refer to a transmission time interval used for sidelink (data) transmission. Preferably, in some embodiments, a sidelink time slot or a time slot used for the sidelink may include all OFDM symbols available for sidelink transmission. Preferably, in some embodiments, a sidelink time slot or a time slot used for the sidelink may include a consecutive number of symbols available for sidelink transmission. Preferably, in some embodiments, a sidelink time slot or a time slot used for the sidelink means that the time slot is included in the sidelink resource pool.

[0689] Preferably, in certain embodiments, the symbol may mean a symbol indicated / configured to be used for a side link.

[0690] Preferably, in certain embodiments, a subchannel is a unit used for sidelink resource allocation / scheduling (for PSSCH). Preferably, in certain embodiments, a subchannel may include multiple consecutive physical resource blocks (PRBs) in the frequency domain. Preferably, in certain embodiments, the number of PRBs used for each subchannel may be (pre-)configured for the sidelink resource pool. Preferably, in certain embodiments, the sidelink resource pool (pre-)configuration may indicate / configure the number of PRBs used for each subchannel. Preferably, in certain embodiments, the number of PRBs used for each subchannel may be any one of 4, 5, 6, 8, 9, 10, 12, 15, 16, 18, 20, 25, 30, 48, 50, 72, 75, 96, or 100. Preferably, in certain embodiments, a subchannel may be represented as a unit for sidelink resource allocation / scheduling. Preferably, in certain embodiments, a subchannel may refer to a PRB. Preferably, in certain embodiments, a subchannel may refer to a set of consecutive PRBs in the frequency domain. Preferably, in some embodiments, a subchannel may mean a set of continuous resource elements in the frequency domain.

[0691] Preferably, in some embodiments, UE may be / mean / include / replace a device.

[0692] Preferably, in certain embodiments, the sidelink transmission / reception may be UE-to-UE transmission / reception. Preferably, in certain embodiments, the sidelink transmission / reception may be device-to-device transmission / reception. Preferably, in certain embodiments, the sidelink transmission / reception may be V2X transmission / reception. Preferably, in certain embodiments, the sidelink transmission / reception may be pedestrian-to-everything (P2X) transmission / reception. Preferably, in certain embodiments, the sidelink transmission / reception may be over a PC5 interface.

[0693] Preferably, in certain embodiments, the PC5 interface may be a wireless interface for device-to-device communication. Preferably, in certain embodiments, the PC5 interface may be a wireless interface for device-to-device communication. Preferably, in certain embodiments, the PC5 interface may be a wireless interface for communication between UEs. Preferably, in certain embodiments, the PC5 interface may be a wireless interface for V2X or P2X communication. Preferably, in certain embodiments, the Uu interface may be a wireless interface for communication between a network node and a device. Preferably, in certain embodiments, the Uu interface may be a wireless interface for communication between a network node and a UE.

[0694] Preferably, in some embodiments, the first UE may be a first device. Preferably, in some embodiments, the first device may be a vehicle UE. Preferably, in some embodiments, the first device may be a V2X UE.

[0695] Preferably, in some embodiments, the second UE may be a second device. Preferably, in some embodiments, the second device may be a vehicle UE. Preferably, in some embodiments, the second device may be a V2X UE.

[0696] Preferably, in some embodiments, the first UE and the second device are different devices.

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

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

[0699] Various aspects of the present disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any specific structure, functionality, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will appreciate that the aspects disclosed herein can be implemented independently of any other aspects, and that two or more of these aspects can be combined in various ways. For example, a device or method can be implemented using any number of the aspects described herein. Additionally, the device or method can be implemented using other structures, functionality, or structures and functionality in addition to or different from one or more of the aspects described herein. As examples 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 a time hopping sequence. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and a time hopping sequence.

[0700] 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 voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0701] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in connection with the various aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two, which can be designed using source decoding or some other technique), and various forms of programs or design code with instructions (which, for convenience, may be referred to herein as "software" or "software modules"), 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 skilled in the art may implement the described functionality in varying ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0702] In addition, the various illustrative logical blocks, modules, and circuits described in connection 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, external to 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 conjunction with a DSP core, or any other such configuration.

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

[0704] The steps of the methods or algorithms described in conjunction with the various aspects disclosed herein can be implemented directly with hardware, with software modules executed by a processor, or with a combination of the two. Software modules (e.g., containing executable instructions and associated data) and other data can reside in a data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. An example storage medium can be connected to a machine such as a computer / processor (for convenience, the machine can be referred to as a "processor" herein) 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 can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and storage medium can reside in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium that includes code related to one or more aspects of the various aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0705] Although the present invention has been described in conjunction with various aspects and examples, it will be understood that the invention is capable of further modification. This application is intended to cover any changes, uses or adaptations of the invention that generally follow the principles of the invention and include such deviations from the present disclosure as come within the scope of known and customary practice in the art to which the invention pertains.

[0706] CROSS-REFERENCE TO RELATED APPLICATIONS

[0707] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 137,103, filed January 13, 2021, which is incorporated herein by reference in its entirety.

Claims

1. A method for a first device to perform sidelink communication to at least a second device in a sidelink resource pool, characterized in that: include: triggering, at a timing, to perform resource selection for sidelink data; Determining or selecting a first sidelink resource from a set of sidelink candidate resources, wherein: deriving or determining the sidelink candidate resource set based on at least a sensing result in a first continuous sensing duration, The first continuous sensing duration comprises a configured or preconfigured number of consecutive transmission time intervals before a first sidelink candidate resource, wherein the first sidelink candidate resource is within a sidelink discontinuous reception active time of the second apparatus, and At least a portion of the first continuous sensing duration is within a sidelink discontinuous reception inactivity time of the first apparatus; as well as A first sidelink transmission is performed on the first sidelink resource for transmitting the sidelink data to the second device.

2. The method according to claim 1, wherein: The side link discontinuous reception activity time of the second device is the most recent side link on duration activity time of the second device after the timing, and / or The first continuous sensing duration is derived or determined based on a start boundary or timing of the side link on-duration active time of the second device, and / or The first continuous sensing duration is derived or determined based on a start boundary or timing of the first side link candidate resource, and / or The first sidelink candidate resource is at a starting boundary or timing of the sidelink discontinuous reception activity time of the second device, and / or The first device assumes or determines the sidelink discontinuous reception activity time of the second device based on at least a second sidelink DRX on-duration timer configuration of the second device, and / or The sidelink on-duration active time of the second device includes a time when the second sidelink DRX on-duration timer is running.

3. The method according to claim 1, wherein: The value of the configured or preconfigured number is 31, 32, configured or preconfigured or specified, and / or The configured or preconfigured number is determined based on the data priority of the side link data, and / or The configured or preconfigured number is determined based on the delay requirement or remaining packet delay budget of the sidelink data, and / or The configured or preconfigured quantity is determined based on a channel busy ratio of the side link resource pool.

4. The method according to claim 3, wherein: The timing is before the configured or preconfigured number of consecutive transmission time intervals immediately before the start boundary or timing of the sidelink DRX active time of the second device, and / or The first apparatus performs the sensing in the configured or preconfigured number of consecutive transmission time intervals in response to the trigger for performing resource selection, and / or In response to the triggering to perform resource selection, the first device does not perform the sensing before the first continuous sensing duration and after the timing.

5. The method according to claim 3, wherein: The timing is within the configured or preconfigured number of consecutive transmission time intervals immediately before the start boundary or timing of the sidelink DRX activity time of the second device, and / or The first device starts performing the sensing in response to the triggering of performing resource selection, and / or The first continuous sensing duration includes a latter portion of the configured or preconfigured number of consecutive transmission time intervals after the timing.

6. The method according to claim 5, characterized in that: The first device performs sensing during a second continuous sensing duration, wherein the second continuous sensing duration starts from the starting boundary or timing of the sidelink discontinuous reception active time of the second device, and / or The sidelink candidate resource set is derived or determined based on a sensing result in the first continuous sensing duration and a sensing result in the second continuous sensing duration, and / or A sum of the number of transmission time intervals of the first continuous sensing duration and the number of transmission time intervals of the second continuous sensing duration is equal to the configured or preconfigured number.

7. The method according to claim 3, wherein: Regardless of whether the first device triggers the resource selection, the first device performs sensing within the first continuous sensing duration before the sidelink discontinuous reception active time of the second device, and / or The first continuous sensing duration is or includes the configured or preconfigured number of consecutive transmission time intervals immediately before a start boundary or timing of the sidelink discontinuous reception active time of the second device.

8. The method according to claim 1, wherein: The timing is outside the sidelink discontinuous reception activity time of the second device, and / or The first continuous sensing duration is outside the sidelink discontinuous reception active time of the second device, and / or The first continuous sensing duration ends at a start boundary or timing of the sidelink discontinuous reception active time of the second device.

9. The method according to claim 1, wherein: The timing is outside the sidelink discontinuous reception activity time of the first device, and / or At least part of the first continuous sensing duration is outside the sidelink discontinuous reception activity time of the first device, and / or The first device determines the sidelink discontinuous reception active time of the first device based on at least a first sidelink DRX on-duration timer configuration of the first device, and / or the sidelink on-duration active time of the first device includes a time when the first sidelink DRX on-duration timer is running.

10. The method according to claim 6, wherein: The timing is in a sidelink transmission time interval in the sidelink resource pool, and / or The first continuous sensing duration includes a side link transmission time interval in the side link resource pool, and / or The second continuous sensing duration includes a side link transmission time interval in the side link resource pool, and / or The configured or preconfigured number of consecutive transmission time intervals includes the side link transmission time intervals in the side link resource pool, and / or The configured or preconfigured number of consecutive transmission time intervals consists of side link transmission time intervals in the side link resource pool.

11. The method according to claim 1, wherein: The sensing during the first continuous sensing duration does not imply partial sensing on a periodic basis, and / or The sensing within the first continuous sensing duration does not mean sensing based on a reservation period.

12. A first device configured to perform sidelink communication to at least a second device 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: triggering, at a timing, to perform resource selection for sidelink data; Determining or selecting a first sidelink resource from a set of sidelink candidate resources, wherein: deriving or determining the sidelink candidate resource set based on at least a sensing result in a first continuous sensing duration, The first continuous sensing duration comprises a configured or preconfigured number of consecutive transmission time intervals before a first sidelink candidate resource, wherein the first sidelink candidate resource is within a sidelink discontinuous reception active time of the second apparatus, and At least a portion of the first continuous sensing duration is within a sidelink discontinuous reception inactivity time of the first apparatus; as well as A first sidelink transmission is performed on the first sidelink resource for transmitting the sidelink data to the second device.

13. The first device according to claim 12, characterized in that: The side link discontinuous reception activity time of the second device is the most recent side link on duration activity time of the second device after the timing, and / or The first continuous sensing duration is derived or determined based on a start boundary or timing of the side link on-duration active time of the second device, and / or The first continuous sensing duration is derived or determined based on a start boundary or timing of the first side link candidate resource, and / or The first sidelink candidate resource is at a starting boundary or timing of the sidelink discontinuous reception activity time of the second device, and / or The first device assumes or determines the sidelink discontinuous reception activity time of the second device based on at least a second sidelink DRX on-duration timer configuration of the second device, and / or The sidelink on-duration active time of the second device includes a time when a second sidelink DRX on-duration timer is running.

14. The first device according to claim 12, characterized in that: The value of the configured or preconfigured number is 31, 32, configured or preconfigured or specified, and / or The configured or preconfigured number is determined based on the data priority of the side link data, and / or The configured or preconfigured number is determined based on the delay requirement or remaining packet delay budget of the sidelink data, and / or The configured or preconfigured quantity is determined based on a channel busy ratio of the side link resource pool.

15. The first device according to claim 14, characterized in that: The timing is before the configured or preconfigured number of consecutive transmission time intervals immediately before the start boundary or timing of the sidelink DRX active time of the second device, and / or The first apparatus performs the sensing in the configured or preconfigured number of consecutive transmission time intervals in response to the trigger for performing resource selection, and / or In response to the triggering to perform resource selection, the first device does not perform the sensing before the first continuous sensing duration and after the timing.

16. The first device according to claim 14, characterized in that: The timing is within the configured or preconfigured number of consecutive transmission time intervals immediately before the start boundary or timing of the sidelink DRX activity time of the second device, and / or The first device starts performing the sensing in response to the triggering of performing resource selection, and / or The first continuous sensing duration includes a latter portion of the configured or preconfigured number of consecutive transmission time intervals after the timing.

17. The first device according to claim 16, characterized in that: The first device performs sensing during a second continuous sensing duration, wherein the second continuous sensing duration starts from the starting boundary or timing of the sidelink discontinuous reception active time of the second device, and / or The sidelink candidate resource set is derived or determined based on the sensing results in the first continuous sensing duration and the sensing results in the second continuous sensing duration, and / or the sum of the number of transmission time intervals of the first continuous sensing duration and the number of transmission time intervals of the second continuous sensing duration is equal to the configured or preconfigured number.

18. The first device according to claim 12, characterized in that: The timing is outside the sidelink discontinuous reception activity time of the first device, and / or At least part of the first continuous sensing duration is outside the sidelink discontinuous reception activity time of the first device, and / or The first apparatus determines the sidelink discontinuous reception activity time of the first apparatus based on at least a first sidelink DRX on-duration timer configuration of the first apparatus, and / or The sidelink on-duration active time of the first device includes a time when the first sidelink DRX on-duration timer is running.

19. The first device according to claim 17, characterized in that: The timing is in a sidelink transmission time interval in the sidelink resource pool, and / or The first continuous sensing duration includes a side link transmission time interval in the side link resource pool, and / or The second continuous sensing duration includes a side link transmission time interval in the side link resource pool, and / or The configured or preconfigured number of consecutive transmission time intervals includes the side link transmission time intervals in the side link resource pool, and / or The configured or preconfigured number of consecutive transmission time intervals consists of side link transmission time intervals in the side link resource pool.

20. The first device according to claim 12, characterized in that: The sensing during the first continuous sensing duration does not imply partial sensing on a periodic basis, and / or The sensing within the first continuous sensing duration does not mean sensing based on a reservation period.

Images